Quote:We tried to pick names that were unlikely to collide
You did that real good, but still my fault.

It was right there in front of me.
Good news is that we now have another Known Problem to be added to the checklist.
Are there any guidelines about when it will/(not) work?
Is it all parameters: "BEEP", "SOUND", and "SOUND"
Any specific OS / BIOS?
Is there another function to provide an audible alert to the user? Here is a function that I just created.
Quote:// =============== PLAY WAV SOUND ============
SubRoutine srPlaySound(vSound as String) //Plays a WAV file
/* This uses a utility, wav.exe, freeware available from
http://www.cmdtools.com/files/wav.zip /q is quiet mode. /vnnn is volume
Properties of command need to be set to run in minimized mode.
Basic structure example is on the next line:
n = @SHELL("C:\Utils\wav.exe C:\Windows\media\chimes.wav /q /v100")
SubRoutine would be called like srPlaySound(ALARM)
A database of sound files is created, each with a unique User-Friendly name.
That name (ID) is looked up to retrieve the name and
path of the wav file. This allows different locations for files.
A. The path XLU could be eliminated and the path can be hardcoded.
B. An XLU could also be done for sound program to allow other file types
such as MIDI. That returned value would replace "C:\Utils\wav.exe".
C. The value for volume could also become a variable.
*/ vSoundFile = @XLU(@FN,vSound,"frmSounds!ID","SoundFile")
vSoundPath = @XLU(@FN,vSound,"frmSounds!ID","SoundFilePath")
n = @SHELL("C:\Utils\wav.exe " & vSoundPath & "\" & vSoundFile & " /q /v100")
End subroutine
It does not play frequency notes, and has no duration period, but it can be used to alert the operator of certain conditions/errors/MSGBOX, etc. Different conditions could have different sounds.
This could run once, or be looped to run x number of times. or for x minutes (See Loiter()

), or to run indefinitely.