X-Spam-Check-By: sourceware.org Date: Tue, 3 Jan 2006 23:43:31 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Does "^G" work on Windows 9x/Me? Message-ID: <20060104044331.GA24111@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com References: <010420060417 DOT 19001 DOT 43BB4C68000220B300004A3922007510900A050E040D0C079D0A AT comcast DOT net> <20060104043616 DOT GA23872 AT trixie DOT casa DOT cgf DOT cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060104043616.GA23872@trixie.casa.cgf.cx> User-Agent: Mutt/1.5.11 Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com 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, >revert to the system speaker. Other sounds are not documentated to work >that way. Otherwise, I probably would just change Cygwin to use 0 since >this is supposed to play the default sound. Or, we could even use our >own nifty .wav file. Sorry to follow up twice on my own message but, I should have read further in the MessageBeep description. It is documented as reverting to the system speaker in all cases if the sound could not be played on a sound card. So, maybe I will just cause the system to use MessageBox(MB_OK) aka MessageBox(0). cgf -- 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/