>>>>its independent.
>>>>"set bell to wavefile" : fires always the computer bell even if "set bell off" or "on".
>>>>(one case can be the computer bell is out of service ! "
>>>
>>>OK so it's obvious I never used the feature :). When I started coding, there were a few XT boxes around where people thought it would be cool for it to beep on each .lostfocus()... which everyone hated. So we decided using the 'bell' would be rude and never did it.
>>
>>Annoying would be a beep on each keystroke (sort'a like how computers used to be portrayed in TV or movie -- making a "boop" noise for every keystroke and character displayed -- or simply a teletype noise -- on a CRT) -- and could be made even more annoying by varying the tone for each keystroke. Used to have a TSR that did just that.
>
>IIRC the offenders were mostly the few XT machines with fresh domestic software, where it didn't react on each keystroke, but only on enter, those being the years before data entry was replaced with data tabby. And, of course, the cash register and other similar machines which were serving in public areas, i.e. post offices, bank tellers etc. Someone's bright idea that the sound of machines will create an illusion of brisk business. Everybody was PO'd, for a few months or even years, until it dawned on them that they can actually complain to programmers.

A bell or sound would probably be OK on error situations, though one might have to be careful about choice of sound clip. The warning noise Kaspersky Antivirus used a number of years ago (often called "pig squeal") was quite startling --it did achieve the goal of getting your attention, though many might describe it as being "heart attack" level of startling.