On Fri, 9 Dec 2016 09:43:24 +0100, R.Wieser wrote:
Thank you, I did not even remember that win.ini file anymore ... But alas,
no "beep" in there either.
But have you tried adding that setting there?
I also found the Beep() description from Windows 95 SDK help file.
http://i.imgur.com/PN1DtKs.png
Quote:
Parameters
dwFreq
Windows NT:
Specifies the frequency, in hertz, of the sound. This parameter must be in
the range 37 through 32,767 (0x25 through 0x7FFF).
Windows 95:
The parameter is ignored.
dwDuration
Windows NT:
Specifies the duration, in milliseconds, of the sound.
One value has a special meaning: If dwDuration is - 1, the function
operates asynchronously and produces sound until called again.
Windows 95:
The parameter is ignored.
Return Value
If the function succeeds, the return value is TRUE.
If the function fails, the return value is FALSE. To get extended error
information, call GetLastError.
Remarks
Windows NT:
The Beep function is synchronous in all but one case; the function does not
generally return control to its caller until the sound finishes. The
exception to this occurs when dwDuration has the value - 1. In that case,
Beep is asynchronous, returning control immediately to its caller while the
sound continues playing. The sound continues until the next call to Beep.
Windows 95:
The Beep function ignores the dwFreq and dwDuration parameters. On computers
with a sound card, the function plays the default sound event. On computers
without a sound card, the function plays the standard system beep.
|
So just for the sake of testing, try disabling your audio device.
Also try the BELL character echo test:
Open a command prompt window, then type "echo ^G" where "^G" is the BELL
character generated by pressing CTRL+G. It should beep the PC speaker.