While I concur with all the others who recommend not doing this, there are some (few) products where start-up sounds makes sense:
- Hardware boot, where the Mac startup chime and the IBM POST beep codes, both of which signify that nothing has gone wrong with the hardware (or, alternatively, that something has gone wrong with the hardware). Depending on the hardware issue, the audible alert may be the only indication of the problem. In the days before Mac OS X (when rebooting a Mac was a fairly common occurrence), the startup chime also solved another, somewhat novel purpose:
Turning the Mac on is one thing, but being forced to reboot from a crash is a totally different experience. I wanted to avoid a sound that would be associated with the crash. I wanted it to sound more like a palette cleanser.
- The Operating System (especially 3+ years ago), which took so long to start up that the chime notified people that it was worth bothering to come back to the computer from, e.g., making a coffee. Microsoft commissioned Brian Eno to create the Windows 95 startup sound:
…he received a brief from Microsoft with “about 150 adjectives” to describe the desired noise. “The piece of music should be inspirational, sexy, driving, provocative, nostalgic, sentimental…” said Eno.
[They changed the sound in Windows Vista][6] (the same sound carried over to Windows 7):
Ball is the first to admit that the percussive beeps in past Windows versions could be jarring enough to bother nearby workers or interrupt others in a meeting. With the number of intrusive sounds from cell phones, handheld devices and other gadgets only increasing, that's something Ball and his colleagues were keen to avoid with Vista.
If you're keen, [here's a blog with all the Windows Startup Sounds from 3.1 to 7][7].
- An application which automatically connects to the Internet, to notify the user that it has done so in the background (e.g. instant messaging apps).