Default beep - what decides it?

  • Thread starter Thread starter Terry Pinnell
  • Start date Start date
T

Terry Pinnell

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?
 
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. :-)
 
Tim Meddick said:
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 said:
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?
Click to expand...
Click to expand...

Thanks Tim. I was wondering if there was any way to discover what
program had prompted each beep?
 
If this happened to me (which it does sometimes), that I heard the
default 'ding' and nothing apparent was visible, it might take me some
considerable time investigating it before I found the cause - if I even
managed to find the cause!

If I install a new program I always run through it's settings and
explorer them fully.

If I come across an option to set an alert sound - I do it - so that I
will be acquainted with what has caused it.

This narrows down what can have caused the noise you heard, as you will
have set the others differently to the default.

One thing I would do would be to open up the Windows Task Manager and
click on it's 'Processes' tab - to familiarize yourself with what
programs are regularly running on your system.

This, and noticing what just happens on your system, may be one way of
deducing what has caused some sound or error alert.

I'm [very] sorry that I could not be of more help, but if you have a
little persistence and investigate methodically, you do stand a much
better chance of discovering the answer.

==

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




Terry Pinnell said:
Tim Meddick said:
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 said:
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?
Click to expand...
Click to expand...

Thanks Tim. I was wondering if there was any way to discover what
program had prompted each beep?
Click to expand...
 
Terry said:
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?
Click to expand...

There are a multitude of things that can cause the default "beep" to
sound. One thing you could do is replace that .wav file with one of
your own. Better yet, record a small recording of your own voice and
simply say "default beep", save it as a .wav file, and then replace the
default beep with your new voice recording.
Now whenever you hear yourself saying "default beep", you can know
that what you just did most likely caused it.
Usually it's used as an acknowledgement sound to indicate that an
operation you asked for was accomplished.

I've done something similar with many of the system sounds. I won't
bore you with a long story, but it can be pretty useful in a lot of
different situations.

HTH,

Twayne`
 
Please bore us! - I for one, would like to hear [what happened with
your system sounds]


==

Cheers, Tim Meddick, Peckham, London. :-)
 
Tim Meddick said:
Please bore us! - I for one, would like to hear [what happened with
your system sounds]


==

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




Twayne said:
There are a multitude of things that can cause the default "beep" to
sound. One thing you could do is replace that .wav file with one of
your own. Better yet, record a small recording of your own voice and
simply say "default beep", save it as a .wav file, and then replace
the default beep with your new voice recording.
Now whenever you hear yourself saying "default beep", you can know
that what you just did most likely caused it.
Usually it's used as an acknowledgement sound to indicate that an
operation you asked for was accomplished.

I've done something similar with many of the system sounds. I won't
bore you with a long story, but it can be pretty useful in a lot of
different situations.

HTH,

Twayne`
Click to expand...
Click to expand...

Tim, Twayne: Thanks both, appreciate the follow-ups.
 
Tim said:
Please bore us! - I for one, would like to hear [what happened with
your system sounds]
Click to expand...

lol, well, it's no panacea or earthshaking event, but I've found a few
things helpful. One thing I did was create another folder under Media
where the sytem sounds are kept, and created my own voice messages for
each one of the defaults so I could switch back and forth at will.

For instance, there is "Navigtation started" and "Navigation Ended". I
forget the default XP names; Start Navigation and CompleteNavigation, I
think. Anyway, turns out they're triggered by the part of IE code that
does a look for something from within a program. Clicking to go to a
URL triggers the Navigation Started and when the downloaded page
completes and the final "Done" appears in the status bar, you get the
Navigation Ended message.
Sounds kind of mundane, right? But it's handy. When I'm sending in
several reports, etc, I only have to hang around long enough to hear
Navigation Started. I don't have to wait around for Navigation Ended
before I can move on and initiate another report. If you don't wait at
least for that Navigation Started message, then starting another report
will simply replace the first one. But once you hear it, you know
you'll open another tab or window in IE for sure; no need to wait for
the Navigation Ended. Which you'll never hear of course, since you've
left the page where the data is coming back to.
A by-product of that is discovering all the other little apps that
trigger the Navigation Started/Ended messages that have nothing to do
with IE. Parts of IE are used for many things central to the OS and
suddenly you can discover when a program uses that. OTOH I was also
pleased to see that it also notified me of call-home features within
some programs.

Then of course there's the ridiculous Windows Start sound which is now
simply "Windows has started". And "Windows is Ending" instead of the
symphony junk.

Some you'll never want but are interesting for the first few minutes are
the sounds for programs opening/closing and windows opening/closing,
information bar, windows feed, etc.
You start an app, you'd think you'd hear it once, but you also hear
every related background task starting and ending, too, in a long,
seemingly senseless series of thing opening and closing, starting and
ending, etc. <g>. It's fun for a minute or two but has no other value
IMO. Well, ts-ing, but they can all be handy to ts-ing. There's a good
reason some of those are defaulted to NO sound<G>!

It's handy too, to have a handle on the "Notification", "Question",
"Information", "Exclamation", "Error", "Critical Stop", etc. etc. and
what each one means and what triggers them. Can be useful for
troubleshooting when you know what's supposed to be happening but can't
keep all the different sounds straight in your head.
I found "Blocked Popup" handy at one point, along with "Hardware
Fail", "Hardware Installed", " Hardware Removed" and a few others.

Like I said, kinda boring stuff<g>
.. I will add that you get pretty sick of listening to your own voice
pretty quick. For the ones I keep turned on, I finally used a British
woman's voice for the messages; much more pleasant to listen to. I used
OmniPage Pro's text to voice translator to create those. Write the
message, have OP speak it as it gets recorded by Audacity. Works well -
Audacity has that "what u hear" feature that makes it real easy.

Bored yet? :^)

HTH,

Twayne`
 
Twayne,
No, I wasn't bored at all, actually. Twas rather fun,
truth to tell.

In Win98, which is a little more configurable that other versions of
Windows, you can use the registry to define sound events for *any*
executable whatsoever. I used to have many different sounds for various
happenings.

Such as a peculiar and distinctive sound happened when Defrag ended -
which was useful because you know how defrag can drag on a bit,
sometimes.

I never thought of recording my own tags though, if I had, I probably
would have gone overboard.

Unfortunately, in XP there is some sort of 'glitch' with system sounds
not working anymore after a time on certain types of machine. I say
this because it has happened (system sounds dying) on three machines, at
work, of the same type running XP and 2K including my own.

Other sounds are unaffected, it's just that event triggered [system]
sounds don't happen, except for one or two. They can no longer be
configured but stick just as they are. For instance, the 'start'
[navigation] event that was configured to be the 'start.wav' (a click
sound) still sounds, but when I wanted to change it, nothing in the
'Sounds' control panel had any effect. So I changed the name of the
file and renamed another file I wanted to hear, to 'start.wav'.

Weird hur?

Like I said, it's only event driven sounds that are affected, media
player works alright. But it does mean that I could never implement
such a thing as you have done, with "voice tags" for different events...
though I think it's very clever.

I HAVE, however, done something similar on my mobile phone, which says
(in my own voice) "It's a new message" when a new message actually does
arrive, seems to amuse colleagues...


==

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




Twayne said:
Tim said:
Please bore us! - I for one, would like to hear [what happened with
your system sounds]
Click to expand...

lol, well, it's no panacea or earthshaking event, but I've found a few
things helpful. One thing I did was create another folder under Media
where the sytem sounds are kept, and created my own voice messages for
each one of the defaults so I could switch back and forth at will.

For instance, there is "Navigtation started" and "Navigation Ended".
I forget the default XP names; Start Navigation and
CompleteNavigation, I think. Anyway, turns out they're triggered by
the part of IE code that does a look for something from within a
program. Clicking to go to a URL triggers the Navigation Started and
when the downloaded page completes and the final "Done" appears in the
status bar, you get the Navigation Ended message.
Sounds kind of mundane, right? But it's handy. When I'm sending in
several reports, etc, I only have to hang around long enough to hear
Navigation Started. I don't have to wait around for Navigation Ended
before I can move on and initiate another report. If you don't wait
at least for that Navigation Started message, then starting another
report will simply replace the first one. But once you hear it, you
know you'll open another tab or window in IE for sure; no need to wait
for the Navigation Ended. Which you'll never hear of course, since
you've left the page where the data is coming back to.
A by-product of that is discovering all the other little apps that
trigger the Navigation Started/Ended messages that have nothing to do
with IE. Parts of IE are used for many things central to the OS and
suddenly you can discover when a program uses that. OTOH I was also
pleased to see that it also notified me of call-home features within
some programs.

Then of course there's the ridiculous Windows Start sound which is now
simply "Windows has started". And "Windows is Ending" instead of the
symphony junk.

Some you'll never want but are interesting for the first few minutes
are the sounds for programs opening/closing and windows
opening/closing, information bar, windows feed, etc.
You start an app, you'd think you'd hear it once, but you also hear
every related background task starting and ending, too, in a long,
seemingly senseless series of thing opening and closing, starting and
ending, etc. <g>. It's fun for a minute or two but has no other value
IMO. Well, ts-ing, but they can all be handy to ts-ing. There's a good
reason some of those are defaulted to NO sound<G>!

It's handy too, to have a handle on the "Notification", "Question",
"Information", "Exclamation", "Error", "Critical Stop", etc. etc. and
what each one means and what triggers them. Can be useful for
troubleshooting when you know what's supposed to be happening but
can't keep all the different sounds straight in your head.
I found "Blocked Popup" handy at one point, along with "Hardware
Fail", "Hardware Installed", " Hardware Removed" and a few others.

Like I said, kinda boring stuff<g>
. I will add that you get pretty sick of listening to your own voice
pretty quick. For the ones I keep turned on, I finally used a British
woman's voice for the messages; much more pleasant to listen to. I
used OmniPage Pro's text to voice translator to create those. Write
the message, have OP speak it as it gets recorded by Audacity. Works
well - Audacity has that "what u hear" feature that makes it real
easy.

Bored yet? :^)

HTH,

Twayne`


==

Cheers, Tim Meddick, Peckham, London. :-)
Click to expand...
Click to expand...
 
Tim said:
Twayne,
No, I wasn't bored at all, actually. Twas rather fun,
truth to tell.

In Win98, which is a little more configurable that other versions of
Windows, you can use the registry to define sound events for *any*
executable whatsoever. I used to have many different sounds for
various happenings.
Click to expand...

lol, "cacophony" comes to mind there! Even worse than XP!

....
Weird hur?

Like I said, it's only event driven sounds that are affected, media
player works alright. But it does mean that I could never implement
such a thing as you have done, with "voice tags" for different
events... though I think it's very clever.
Click to expand...

Hmm, I haven't come across that. I know if two events trigger one right
after another, the first is fogotten in favor of the last one, but not
what you described; there is no queue-up ability.

I wonder if it's LAN related somehow. Weird, yeah!
I HAVE, however, done something similar on my mobile phone, which says
(in my own voice) "It's a new message" when a new message actually
does arrive, seems to amuse colleagues...
Click to expand...

lol, I know what you mean. Most people get a kick out of it. I'm so
used to it now that the standard bing/bang/bongs drive me up a wall<g>!

'ave a good un!

Twayne

==

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




Twayne said:
Tim said:
Please bore us! - I for one, would like to hear [what happened
with your system sounds]
Click to expand...

lol, well, it's no panacea or earthshaking event, but I've found a
few things helpful. One thing I did was create another folder under
Media where the sytem sounds are kept, and created my own voice
messages for each one of the defaults so I could switch back and
forth at will. For instance, there is "Navigtation started" and
"Navigation Ended".
I forget the default XP names; Start Navigation and
CompleteNavigation, I think. Anyway, turns out they're triggered by
the part of IE code that does a look for something from within a
program. Clicking to go to a URL triggers the Navigation Started and
when the downloaded page completes and the final "Done" appears in
the status bar, you get the Navigation Ended message.
Sounds kind of mundane, right? But it's handy. When I'm sending
in several reports, etc, I only have to hang around long enough to
hear Navigation Started. I don't have to wait around for Navigation
Ended before I can move on and initiate another report. If you
don't wait at least for that Navigation Started message, then
starting another report will simply replace the first one. But once
you hear it, you know you'll open another tab or window in IE for
sure; no need to wait for the Navigation Ended. Which you'll never
hear of course, since you've left the page where the data is coming
back to. A by-product of that is discovering all the other little
apps that trigger the Navigation Started/Ended messages that have
nothing to do with IE. Parts of IE are used for many things central
to the OS and suddenly you can discover when a program uses that.
OTOH I was also pleased to see that it also notified me of call-home
features within some programs.

Then of course there's the ridiculous Windows Start sound which is
now simply "Windows has started". And "Windows is Ending" instead
of the symphony junk.

Some you'll never want but are interesting for the first few minutes
are the sounds for programs opening/closing and windows
opening/closing, information bar, windows feed, etc.
You start an app, you'd think you'd hear it once, but you also
hear every related background task starting and ending, too, in a
long, seemingly senseless series of thing opening and closing,
starting and ending, etc. <g>. It's fun for a minute or two but has
no other value IMO. Well, ts-ing, but they can all be handy to
ts-ing. There's a good reason some of those are defaulted to NO
sound<G>! It's handy too, to have a handle on the "Notification",
"Question",
"Information", "Exclamation", "Error", "Critical Stop", etc. etc. and
what each one means and what triggers them. Can be useful for
troubleshooting when you know what's supposed to be happening but
can't keep all the different sounds straight in your head.
I found "Blocked Popup" handy at one point, along with "Hardware
Fail", "Hardware Installed", " Hardware Removed" and a few others.

Like I said, kinda boring stuff<g>
. I will add that you get pretty sick of listening to your own voice
pretty quick. For the ones I keep turned on, I finally used a
British woman's voice for the messages; much more pleasant to listen
to. I used OmniPage Pro's text to voice translator to create those.
Write the message, have OP speak it as it gets recorded by Audacity.
Works well - Audacity has that "what u hear" feature that makes it
real easy.

Bored yet? :^)

HTH,

Twayne`


==

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




Terry Pinnell wrote:
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?

There are a multitude of things that can cause the default "beep"
to sound. One thing you could do is replace that .wav file with
one of your own. Better yet, record a small recording of your own
voice and
simply say "default beep", save it as a .wav file, and then replace
the default beep with your new voice recording.
Now whenever you hear yourself saying "default beep", you can
know that what you just did most likely caused it.
Usually it's used as an acknowledgement sound to indicate that an
operation you asked for was accomplished.

I've done something similar with many of the system sounds. I
won't bore you with a long story, but it can be pretty useful in a
lot of different situations.

HTH,

Twayne`
Click to expand...
Click to expand...
Click to expand...
 
It happened on three successive clean [xp] installs. After a short
time, all the system event sounds just ceased.

This was way before I had any network, of any description, installed,
and had all networking facilities, disabled, at the time


==

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




Twayne said:
Tim said:
Twayne,
No, I wasn't bored at all, actually. Twas rather fun,
truth to tell.

In Win98, which is a little more configurable that other versions of
Windows, you can use the registry to define sound events for *any*
executable whatsoever. I used to have many different sounds for
various happenings.
Click to expand...

lol, "cacophony" comes to mind there! Even worse than XP!

...
Weird hur?

Like I said, it's only event driven sounds that are affected, media
player works alright. But it does mean that I could never implement
such a thing as you have done, with "voice tags" for different
events... though I think it's very clever.
Click to expand...

Hmm, I haven't come across that. I know if two events trigger one
right after another, the first is fogotten in favor of the last one,
but not what you described; there is no queue-up ability.

I wonder if it's LAN related somehow. Weird, yeah!
I HAVE, however, done something similar on my mobile phone, which
says
(in my own voice) "It's a new message" when a new message actually
does arrive, seems to amuse colleagues...
Click to expand...

lol, I know what you mean. Most people get a kick out of it. I'm so
used to it now that the standard bing/bang/bongs drive me up a
wall<g>!

'ave a good un!

Twayne

==

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




Twayne said:
Tim Meddick wrote:
Please bore us! - I for one, would like to hear [what happened
with your system sounds]

lol, well, it's no panacea or earthshaking event, but I've found a
few things helpful. One thing I did was create another folder under
Media where the sytem sounds are kept, and created my own voice
messages for each one of the defaults so I could switch back and
forth at will. For instance, there is "Navigtation started" and
"Navigation Ended".
I forget the default XP names; Start Navigation and
CompleteNavigation, I think. Anyway, turns out they're triggered by
the part of IE code that does a look for something from within a
program. Clicking to go to a URL triggers the Navigation Started
and
when the downloaded page completes and the final "Done" appears in
the status bar, you get the Navigation Ended message.
Sounds kind of mundane, right? But it's handy. When I'm sending
in several reports, etc, I only have to hang around long enough to
hear Navigation Started. I don't have to wait around for Navigation
Ended before I can move on and initiate another report. If you
don't wait at least for that Navigation Started message, then
starting another report will simply replace the first one. But once
you hear it, you know you'll open another tab or window in IE for
sure; no need to wait for the Navigation Ended. Which you'll never
hear of course, since you've left the page where the data is coming
back to. A by-product of that is discovering all the other little
apps that trigger the Navigation Started/Ended messages that have
nothing to do with IE. Parts of IE are used for many things central
to the OS and suddenly you can discover when a program uses that.
OTOH I was also pleased to see that it also notified me of call-home
features within some programs.

Then of course there's the ridiculous Windows Start sound which is
now simply "Windows has started". And "Windows is Ending" instead
of the symphony junk.

Some you'll never want but are interesting for the first few minutes
are the sounds for programs opening/closing and windows
opening/closing, information bar, windows feed, etc.
You start an app, you'd think you'd hear it once, but you also
hear every related background task starting and ending, too, in a
long, seemingly senseless series of thing opening and closing,
starting and ending, etc. <g>. It's fun for a minute or two but has
no other value IMO. Well, ts-ing, but they can all be handy to
ts-ing. There's a good reason some of those are defaulted to NO
sound<G>! It's handy too, to have a handle on the "Notification",
"Question",
"Information", "Exclamation", "Error", "Critical Stop", etc. etc.
and
what each one means and what triggers them. Can be useful for
troubleshooting when you know what's supposed to be happening but
can't keep all the different sounds straight in your head.
I found "Blocked Popup" handy at one point, along with "Hardware
Fail", "Hardware Installed", " Hardware Removed" and a few others.

Like I said, kinda boring stuff<g>
. I will add that you get pretty sick of listening to your own voice
pretty quick. For the ones I keep turned on, I finally used a
British woman's voice for the messages; much more pleasant to listen
to. I used OmniPage Pro's text to voice translator to create those.
Write the message, have OP speak it as it gets recorded by Audacity.
Works well - Audacity has that "what u hear" feature that makes it
real easy.

Bored yet? :^)

HTH,

Twayne`





==

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




Terry Pinnell wrote:
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?

There are a multitude of things that can cause the default "beep"
to sound. One thing you could do is replace that .wav file with
one of your own. Better yet, record a small recording of your own
voice and
simply say "default beep", save it as a .wav file, and then
replace
the default beep with your new voice recording.
Now whenever you hear yourself saying "default beep", you can
know that what you just did most likely caused it.
Usually it's used as an acknowledgement sound to indicate that an
operation you asked for was accomplished.

I've done something similar with many of the system sounds. I
won't bore you with a long story, but it can be pretty useful in a
lot of different situations.

HTH,

Twayne`
Click to expand...
Click to expand...
Click to expand...
 
Hi Terry.

The guilty party in this case is Sounds and Audio Devices. I don't know any
program that sets their own Default Beep. If you are unhappy with it set it
to nothing.

If you have the category view, it's Control Panel > Sounds, Speech and Audio
Devices > "Change the sound scheme" and click Default Beep, and in the
Sounds: menu choose None. If it's the classic view (just icons) go to
Control Panel, double click Sounds and Audio Devices, go to the Sounds tab,
click Default Beep, and in the Sounds: menu choose None.

Its default setting in Windows XP is "Windows XP Ding".
 
For God's sake Robin, this thread was last posted to over two months ago now?

Anyway, the problem (if you actually read it properly) wasn't that the default "ding"
["Windows XP Ding.wav"] was not heard, but that it was heard too many times in the
opinion of the OP

Unless you have some drastic new pertinent information to contribute - the accepted
protocol is not to post to anything more than 48hrs old!

==

Cheers, Tim Meddick, Peckham, London. :-)
 
Oh, so it's sneer time, is it? GNN!
Tim Meddick said:
For God's sake Robin, this thread was last posted to over two months ago
now?

Anyway, the problem (if you actually read it properly) wasn't that the
default "ding" ["Windows XP Ding.wav"] was not heard, but that it was
heard too many times in the opinion of the OP

Unless you have some drastic new pertinent information to contribute - the
accepted protocol is not to post to anything more than 48hrs old!

==

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




Robin Bailey said:
Hi Terry.

The guilty party in this case is Sounds and Audio Devices. I don't know
any program that sets their own Default Beep. If you are unhappy with it
set it to nothing.

If you have the category view, it's Control Panel > Sounds, Speech and
Audio Devices > "Change the sound scheme" and click Default Beep, and in
the Sounds: menu choose None. If it's the classic view (just icons) go to
Control Panel, double click Sounds and Audio Devices, go to the Sounds
tab, click Default Beep, and in the Sounds: menu choose None.

Its default setting in Windows XP is "Windows XP Ding".
Click to expand...
Click to expand...
 
Back
Top