"Tim Meddick" wrote:

Maybe you have more than 'Default Beep' set to be 'ding.wav' in 'Sounds
and Audio Devices' control panel?

Any application that calls for the standard computer beep (pc speaker)
is interrupted by Windows and the 'Default Beep' that you have defined
(ding.wav) is played instead - IF Windows detects you have a soundcard
installed.

If you have no soundcard, then programs calling for this beep just sound
a vary basic beep from the pc speaker instead.

Many applications use this function of calling for a 'beep' and many
Windows events and errors use this default beep as well.

If you change the 'Default Beep' item in the 'Sounds...' control panel
('Sounds' tab) to a new wave file, then *all* the times that *any*
program or event calls for the 'Default Beep' your new [wav] file should
be played instead.

==

Cheers, Tim Meddick, Peckham, London. :-)




"Terry Pinnell" wrote in message
.. .
On this XP Pro PC the 'Default beep' sound is currently set in CP
Sounds and Audio Devices Sounds as Ding.wav. I haven't noticed it
much before but I recall it occurs when I do something obviously
dis-allowed, like trying to type text where it's invalid, etc.

But sometimes I'm hearing it when I don't expect it and it seems
inappropriate. What are the rules here please? Presumably it can be
programmed in each application? But are there any 'Windows' operations
on top of those?

--
Terry, East Grinstead, UK


Thanks Tim. I was wondering if there was any way to discover what
program had prompted each beep?

--
Terry, East Grinstead, UK