X-Spam-Check-By:	sourceware.org
From:	ericblake AT comcast DOT net (Eric Blake)
To:	cygwin AT cygwin DOT com
Subject:	Re: Does "^G" work on Windows 9x/Me?
Date:	Wed, 04 Jan 2006 04:55:35 +0000
Message-Id:	<010420060455.26040.43BB55470009A10B000065B822007340760A050E040D0C079D0A@comcast.net>
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

> 
> 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.

Indeed - on Win98, when I disable the default sound altogether (in
other words, HKCU/AppEvents/Schemes/Apps/.Default/.Default.current/@
is now zero-length), then MessageBeep(MB_OK) did indeed fall back to the
same faint motherboard beep that I was always getting from MessageBeep(-1).

> 
> So, maybe I will just cause the system to use MessageBox(MB_OK) aka
> MessageBox(0).

I think you mean MessageBeep, not MessageBox.

Well, MSDN did document that on NT 4.0, MessageBeep(-1) calls Beep(), which
forwards on to the client, whereas all other message beep parameters are
not forwarded (but talk about confusing language to read). 

--
Eric Blake


--
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/

- Raw text -