Re: Defending OpenBSD Performance

2009-09-18 Thread Buzzer
On Fri, Sep 18, 2009 at 06:48:06PM -0400, bofh wrote: > actually beat me out for stupidity of the day. He probably believes > Microsoft and runs XP on a 486 too. You are probably junked now. -- /Buzzer

Re: Defending OpenBSD Performance

2009-09-18 Thread Buzzer
t; in 2009? after all, this subthread started with you > saying OpenBSD might not be suitable as a desktop system, because of your > issue with timidity "performance". I affirm that it is timidity on FreeBSD 4.11 display more performance than timidity or fluidsynth both on OpenBSD 4.5. -- /Buzzer

Re: Defending OpenBSD Performance

2009-09-24 Thread Buzzer
secure OS in the world, which one they allow me to use for free. This is the best donation, which I can give to. -- /Buzzer

Shutdown problem.

2009-09-26 Thread Buzzer
vt100 emulation) wsdisplay0: screen 2 added (80x25bf, vt100 emulation) -- /Buzzer

Re: Shutdown problem.

2009-09-26 Thread Buzzer
watch TV. When I > > returned, nothing has changed - the same message on my display, power > > off did not happen. > > Hi did you try: shutdown -hp now? I will try. It will take some time to see if problem can be reproduced. > I tested that on my old pc running 4.3 and work

Re: Shutdown problem.

2009-09-26 Thread Buzzer
oot prompt, quickly type boot -c > Then type: disable apm apmd_flags in rc.conf.local file will not disable it? > If this fixes problem, you can use config to make change permanent Sometimes I need to put system into deep sleep mode... -- /Buzzer () KAMPANIQ ascii ribbon - PROTIW PISEM W html FORMATE /\ www.asciiribbon.org - PROTIW PROPRIETARNYH WLOVENIJ

Re: Shutdown problem.

2009-09-26 Thread Buzzer
^^ wsdisplay0: screen 1 added (80x25bf, vt100 emulation) wsdisplay0: screen 2 added (80x25bf, vt100 emulation) wsdisplay0: screen 3 added (80x25bf, vt100 emulation) wsdisplay0: screen 4 added (80x25bf, vt100 emulation) wsdisplay0: screen 5 added (80x25bf, vt100 emulation) wsdisplay0: screen 6 added (

/dev/audio: Device busy

2009-10-01 Thread Buzzer
P, CTL0045, , Audio" port 0x220/16,0x330/2,0 x388/4 irq 5 drq 1,5: dsp v4.16 audio0 at sb1 -- /Buzzer () KAMPANIQ ascii ribbon - PROTIW PISEM W html FORMATE /\ www.asciiribbon.org - PROTIW PROPRIETARNYH WLOVENIJ

Re: /dev/audio: Device busy

2009-10-01 Thread Buzzer
e you think that I did not read man aucat? -- /Buzzer () KAMPANIQ ascii ribbon - PROTIW PISEM W html FORMATE /\ www.asciiribbon.org - PROTIW PROPRIETARNYH WLOVENIJ

Re: /dev/audio: Device busy

2009-10-02 Thread Buzzer
to make > some assumptions of our own... I'm waiting for step by step advices. It would be good idea to make suitable issue in the FAQ. -- /Buzzer () KAMPANIQ ascii ribbon - PROTIW PISEM W html FORMATE /\ www.asciiribbon.org - PROTIW PROPRIETARNYH WLOVENIJ

Re: /dev/audio: Device busy

2009-10-02 Thread Buzzer
-s deafault file.wav'. > > > > aucat -s default send.wav > > aucat: can't open /dev/audio: Device busy > > aucat: send.wav: could not play -- /Buzzer () KAMPANIQ ascii ribbon - PROTIW PISEM W html FORMATE /\ www.asciiribbon.org - PROTIW PROPRIETARNYH WLOVENIJ

Re: /dev/audio: Device busy

2009-10-02 Thread Buzzer
ently using the audio device, kill that Nobody, except 'aucat -l', use /dev/audio. So, there is nothing to kill, except $(ps -axc | grep aucat | awk {'print($1)'}). And when I kill 'aucat -l', then 'aucat' will be able to play file. > application. Aft

Re: /dev/audio: Device busy

2009-10-02 Thread Buzzer
n ttyC0 following message appers: 'sbdsp_trigger_input: width=8 bad chan 5'. > > It would be good idea to make > > suitable issue in the FAQ. > > yeah, aucat server should probably be mentioned in faq13 somewhere. I mean multiplex play. -- /Buzzer () KAMPANIQ ascii ribbon - PROTIW PISEM W html FORMATE /\ www.asciiribbon.org - PROTIW PROPRIETARNYH WLOVENIJ

Re: /dev/audio: Device busy

2009-10-02 Thread Buzzer
fferent > hardware). Do you suggest to change play.precision to 8? My hardware works perfectly on FreeBSD 4.11. > you may want to use '-m play' when sarting aucat server. Device busy. -- /Buzzer () KAMPANIQ ascii ribbon - PROTIW PISEM W html FORMATE /\

Re: /dev/audio: Device busy

2009-10-02 Thread Buzzer
ice to run aucat with '-l' arg. Above you saw the result. > > On ttyC0 following message appers: 'sbdsp_trigger_input: width=8 bad > > chan 5'. > > > > > > It would be good idea to make > > > > suitable issue in the FAQ. > > >

Re: /dev/audio: Device busy

2009-10-02 Thread Buzzer
ther -i nor -o are > given, aucat falls back to legacy mode; legacy mode wants to open the > device directly rather than going through the "aucat -l" server. Use the > '-i' flag. Got sound. -- /Buzzer () KAMPANIQ ascii ribbon - PROTIW PISEM W html FORMATE

Re: OpenBSD -current Xterm cyrillic problem

2009-10-03 Thread Buzzer
rm*faceName: Andale Mono Hope this help. 2) Read the thread 'Cyrillic fonts in X Window'. -- /Buzzer () KAMPANIQ ascii ribbon - PROTIW PISEM W html FORMATE /\ www.asciiribbon.org - PROTIW PROPRIETARNYH WLOVENIJ

Re: /dev/audio: Device busy

2009-10-03 Thread Buzzer
reeBSD 4.11? > > > you may want to use '-m play' when sarting aucat server. > > > > Device busy. > > Input/output error. FAQ. -- /Buzzer () KAMPANIQ ascii ribbon - PROTIW PISEM W html FORMATE /\ www.asciiribbon.org - PROTIW PROPRIETARNYH WLOVENIJ

Re: /dev/audio: Device busy

2009-10-03 Thread Buzzer
advised several times to read aucat(1). If aucat are able to play without '-i', then '-i' is a rudiment (on my opinion). I miss. > > > > > > It would be good idea to make suitable issue in the FAQ. > > > > > > > > > > yeah, aucat server should proba

Re: /dev/audio: Device busy

2009-10-04 Thread Buzzer
to thank me for my bug reports and proposes, of course, if you are aim to make OS better and understandable for new users. Otherwise, you will get 'Device busy II'. By the way, 'Xterm cyrillic problem II' you've got. I do not want to hear anything else. Thread closed. -- /Buzzer () KAMPANIQ ascii ribbon - PROTIW PISEM W html FORMATE /\ www.asciiribbon.org - PROTIW PROPRIETARNYH WLOVENIJ