|
|
Post by sarossell on Dec 11, 2019 0:36:11 GMT -5
I can't figure why this is the cases, but BEEP just won't beep.
PLAYWAV and PLAYMIDI work fine, and program error dialogs play the standard Windows alert sound, but no matter what settings I adjust in Windows 10 Pro 32-bit, I can't get BEEP to make a sound.
|
|
|
|
Post by Chris Iverson on Dec 11, 2019 1:11:21 GMT -5
...huh. I wonder when that happened. I wish I had a running Windows 7 machine at the moment, as I'd test it on there. I know the way that the beep is implemented changed in Windows 7 due to a conflict between ADA requirements and changing standard PC requirements, but that shouldn't affect how applications trigger it. (Actually, it changed in XP, then again in Vista, then again in 7, all for different reasons). Even weirder, for me(Windows 10 pro, 64 bit), while the BEEP command doesn't work, the Beep() Win32 API(which is what I imagine the beep command would be based around) DOES work. freq = 750
duration = 300
callDLL #kernel32, "Beep",_
freq as long,_
duration as long,_
ret as long |
|
|
|
Post by sarossell on Dec 11, 2019 2:31:55 GMT -5
...huh. I wonder when that happened. I wish I had a running Windows 7 machine at the moment, as I'd test it on there. I know the way that the beep is implemented changed in Windows 7 due to a conflict between ADA requirements and changing standard PC requirements, but that shouldn't affect how applications trigger it. (Actually, it changed in XP, then again in Vista, then again in 7, all for different reasons). Even weirder, for me(Windows 10 pro, 64 bit), while the BEEP command doesn't work, the Beep() Win32 API(which is what I imagine the beep command would be based around) DOES work. freq = 750
duration = 300
callDLL #kernel32, "Beep",_
freq as long,_
duration as long,_
ret as longThanks! Especially for the DLL solution. I tested BEEP on XP and Win10 - no go. But even more perplexing, your DLL call worked in Win10 but not XP. BUT, PLAYWAVE works on both. Crazy.
|
|
|
|
Post by Rod on Dec 11, 2019 4:44:03 GMT -5
We have not had an operational BEEP for quite a while. Windows dropped the function years ago. It needed a hard wired speaker on the motherboard at a specific address. few motherboards have such a speaker these days so whether it works or not depends on your specific motherboard. Playwave on the other hand uses the MMI to play sound. This sound will pass through the sound chip hardware in whatever form it exists.
Our bug fix for a long while has been playwave "beep". You don't need to have a file named beep.wav, because it does not exist you get the default error beep via the sound chip.
|
|
|
|
Post by sarossell on Dec 11, 2019 13:49:10 GMT -5
We have not had an operational BEEP for quite a while. Windows dropped the function years ago. It needed a hard wired speaker on the motherboard at a specific address. few motherboards have such a speaker these days so whether it works or not depends on your specific motherboard. Playwave on the other hand uses the MMI to play sound. This sound will pass through the sound chip hardware in whatever form it exists. Our bug fix for a long while has been playwave "beep". You don't need to have a file named beep.wav, because it does not exist you get the default error beep via the sound chip. Ha! Clever. Beep by attrition. I love it. Thanks Rod! |
|
