On Tue, Jan 03, 2006 at 11:36:16PM -0500, Christopher Faylor wrote:
>On Wed, Jan 04, 2006 at 04:17:44AM +0000, Eric Blake wrote:
>>> Neither Corinna nor I have a real machine running Windows 98 any more
>>> so we can't easily test to see if echoing a CTRL-G to a console window
>>> running bash (or any other cygwin shell) actually does anything. Can
>>> anyone confirm if this actually plays a beep?
>>
>>My experience with Win98 is that both before and after the patch,
>>snapshots 20051229 and 20060103 12:55:23, the command
>>"printf '\a%1000s\a' 1" produced two tweets on the motherboard
>>speaker (which is rather faint to hear since I keep my box underneath
>>the desk), rather than playing a .wav file on my speakers which
>>are located on my desk. Yes, my 266MHz box is slow enough that
>>printing one thousand characters had enough noticeable I/O delay
>>that I could distinguish between the two beeps. I would much
>>rather hear a .wav file, though (or not hear, as the case may be,
>>when I mute my desktop speakers - there is no way to mute the
>>motherboard speaker).
>
>The patch shouldn't have had an effect on a working installation so I'm
>glad that there is not change in the recent snapshot.
>
>Apparently, Windows 9x defaults to the system speaker no matter what.
>How very surprising that this would be inconsistent. What. are. the. odds?
>
>>Maybe Win9x needs to use MessageBeep(0) to play a .wav.
>
>In theory, MessageBeep(-1) will try to play a sound, and if that fails,
^
via a sound card
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
