Aargh, sometimes you wonder: What were they thinking? What kind of drugs were they on? And it can't have been a single dev, it must have been just about all the MS employees dog-fooding Longhorn. Or maybe that's just it, the dog food is getting too toxic and causing these side effects.
Anyway: as a pointer (for myself) for all future Vista installs, after install do this: http://weyland.be/wrdprss/index.php/2007/02/08/disable-system-beep-in-windows-vista/
Or for a scripted install here are the instructions: http://blog.netnerds.net/2007/05/5-ways-to-stop-windows-vista-xp-2003-from-beeping/
From a quick search, it seems to be really inconsistent on when it actually happens. My gut feeling: some debug code that is left in Vista. Not that this is the type of debugging that you'd want to do I assume, but it's something that my father has carried over from his Visual Basic days: call beep to see hear if some part of your code is running. Now he is developping a multithreaded real-time model railway control application, interfacing with hardware and such, so while experimenting, having a beep play instead of the application stopping in a breakpoint (and the trains crashing into each other) actually could be a valid use for beep-debugging. But for Vista... naaaah. What a mistaaaike to maaaike!!
posted @ Friday, October 19, 2007 1:51 PM