Vista Startup Sound to be Mandatory?
Toreo asesino writes "There has been lots of debate in the past few days over Microsoft's plan to make the startup sound in Windows Vista something that can't be specifically silenced by changing the sound settings in the control panel. Users would be able to avoid hearing it by manually turning down the speaker volume, but then they would have to turn that volume back up to hear anything else."
They will have to come up with some kind of way to turn it off. The majority of broadcast automation applications still run on Windows. When I worked at KDKD, we had all the on-air PCs set to "No Sounds"... It's always funny to hear a Windows sound on the radio.
Only if you haven't muted audio. If you mute the audio output and then reboot (or shutdown and then power on), you won't hear the power-on chime.
It is NOT mandatory.
o pper/Startup%20Chime%20Stopper.html1 005165919533
Turn down your sound (in the OS X volume control), or mute your speakers.
Restart.
Tada! No startup sound.
There are also applications and Applescripts that will do it automatically for you:
http://alphaomega.software.free.fr/startupchimest
http://www.macosxhints.com/article.php?story=2003
http://www.macupdate.com/info.php/id/16780
By the way, the Apple startup sound is more akin to the PC Bios Boot-Beep. It's a hardware test, and it will play a different sound if there is a video card failure or ram failure, something which prevents the system from reaching the GUI.
WhiteWolf666 an exBush supporter. All you new-school,compassionate,save the children Republicans can rot in hell
You can always just hold down the mute button during boot and it won't make the noise (at least I think, it's been awhile since I last restarted). You then let go of the mute button and it will return you to your pre-determined volume level while it's finishing booting.
Not just the startup sound, but all of the sounds, like I want to hear if I click my mouse, my mouse can make that sound on its own, and I don't need a sound every time one of those alert buttons pop up, they are on top anyway so I'll see them, right?
But then again, with OSX it isn't possible to disable the startup sound either (or so I've heard) so if people would make a fuss about this, then why not continue at apple?
Mozilla Firefox is a counter-example to this argument. There are about a bazillion things you can change by entering "about:config" in the url bar. The vast majority can't be changed via the menus and thus don't clutter the UI. Yet they're readily available for anyone who does want to change them.
Moderating "-1, Disagree" is simple censorship. Have the guts to post your opinion.
You don't even have to mute it before you shut down. You can shut the laptop down with the sound on. When you press the power on button, start holding down the Audio Off/Mute button on the keyboard. Hold it until you see the Apple. Bingo. No startup chime, and sound is still enabled (or disabled, whatever it was before) once you get to the desktop.
It's not manditory, and I believe it works the way most "non-geeks" would expect.
a c_help/pages/0025-startup_sound.html
It follows the software volume setting from when you turned off your Mac.
You can also mute it by holding F3 while booting your Mac, which on any Apple keyboard has the "mute speaker" icon, which is also how you mute the speaker in software.
There are also many free utilities that can disable it for you.
I suppose using Google to search for "mac startup sound mute" and hitting I'm feeling lucky was too hard. The result is pretty clear....
http://homepage.mac.com/geerlingguy/mac_support/m
Yeah, there's this nasty BITCH of a mechanism called Windows File Protection - where many of the common system files have backup copies in a hidden subdirectory called dllcache. If you delete the system copy, the os "detects" it (via a filter-driver), and copies the backup from dllcache.
.CAB file in dllcache - and that .CAB file has a manifest that has checksums and digital signatures socked away in a jet database or registry hive somewhere - theoretically, one could ONLY update one of these files via the Microsoft Installer Service API.
In some cases, the fix is to simply delete the dllcache version - if what you're trying to do is delete the file. But there's also an added level of hackery for a subset of these protected files, because they're also redundantly backed up in a
So for files that are protected with this extra level, no, it's not really possible to change them via hex editor. I know that there used to be hacks in 2000 to disable WFP. I also know that in 2002, Microsoft did not have the expertise, in house, to answer a developer support question on WFP behavior (for a developer of BACKUP software - ie. "what happens if I restore the system to a previous version via backup software? - answer: nasty stuff. Which is why imaging software became a very popular way of backup and restore windows desktops).
No - I know that guys like Marc Russinovich probably have a much better understanding of how WFP works. But this is my understanding after having to deal with it. Frankly, in the past few years, when I've had to remove spyware and malware from systems, there's an eerie resemblance in self-protection techniques between WFP and malware.
These are my friends, See how they glisten. See this one shine, how he smiles in the light.