0SX Start-up chime disabler
- Type:
- Applications > Mac
- Files:
- 3
- Size:
- 3.77 KiB (3857 Bytes)
- Uploaded:
- 2012-10-05 09:30:01 GMT
- By:
- macomaniac
- Seeders:
- 1
- Leechers:
- 0
- Comments
- 4
- Info Hash: BD2F3FC8AEB90B2CDB315BBBF48E2FCDB86AF166
(Problems with magnets links are fixed by upgrading your torrent client!)
Since Lion, and now with Mountain Lion, the start-up chime when launching Mac OS X cannot be disabled any longer by the application 'Start-upSoundPreferencePane' which is not supported. For the ones unwilling to hear such a strident sound on launch (very annoying in public spaces, isn't it?), but also not very in love with using the command-line, I have written using nano in the Terminal two scripts, one to disable the chime on launch, the other to enable back the sound at the level chosen on quit when the user session opens. You will find in the package the two scripts and a text of instruction, saying where to drag them and how to activate them writing two very succinct commands in a Terminal window before re-starting your computer. For the ones willing to enable back the chime, two commands are added disabling the precedent . The method works on Snow Leopard, Lion and Mountain Lion (successfully tested by myself). For the ones suspicious about unknown scripts, double-click them and you will be able to check in TexEdit their very innocuous content strictly related to the topic. Cheers
| File list not available. |
Sounds great (pardon the pun). I'm not game to use them yet, and I don't understand scripts, so will wait for someone to do so. Thanks in advance.
I Cant get it to work, Followed the guide
@Fionkey.
The two script files, located in the General Library/Scripts folder, once activated by the terminal commands work fine on my MacBookPro running Mountain Lion. Also on a MacBookAir running Lion, and on an iMac running Snow Leopard as well. As I have created them on my MacBookPro, and transported a copy of them afterward to the other computers by way of a thumb drive, I wonder if through updoading them unzipped their properties might not get corrupted. For the commands in the Terminal, when the right scripts in the right folder, work necessarily.
The two script files, located in the General Library/Scripts folder, once activated by the terminal commands work fine on my MacBookPro running Mountain Lion. Also on a MacBookAir running Lion, and on an iMac running Snow Leopard as well. As I have created them on my MacBookPro, and transported a copy of them afterward to the other computers by way of a thumb drive, I wonder if through updoading them unzipped their properties might not get corrupted. For the commands in the Terminal, when the right scripts in the right folder, work necessarily.
Hi guys!
Stop downloading that. I have downloaded my own torrent on another MacBookPro, dragged the script files to the Library/Scripts folder and activated the commands in the Terminal. Result : failure. The start-up chime stays as loud as before. Then, by way of an USB thumb drive, I have transferred the same script files at root from my computer to this new computer and changed the files in the Script folder. The Terminal command being activated, no other thing to do. On re-starting, the chime is muted this time. In consequence, the properties of the script files got corrupted through uploading.
I start another torrent, this time uploading a zipped folder. I hope it will work!
Stop downloading that. I have downloaded my own torrent on another MacBookPro, dragged the script files to the Library/Scripts folder and activated the commands in the Terminal. Result : failure. The start-up chime stays as loud as before. Then, by way of an USB thumb drive, I have transferred the same script files at root from my computer to this new computer and changed the files in the Script folder. The Terminal command being activated, no other thing to do. On re-starting, the chime is muted this time. In consequence, the properties of the script files got corrupted through uploading.
I start another torrent, this time uploading a zipped folder. I hope it will work!
Comments