Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I did a similar thing in the Win9x days. I had some sound alert going off once in a while and I couldn't figure out what was causing it, worse, I didn't even recognize the sound. (It wasn't the standard "ding" or "chord".)

And when I went into the Windows sound scheme configurator, it had wacky names for some events like "asterisk" and "critical stop", with no explanation of what might trigger them.

So as a first step of narrowing it down, I made self-explanatory sounds for everything: I just recorded my voice saying "open program", "program error", "restore down", "exclamation", and so on, through the whole list, and assigned each sound to its respective event. There were a lot of them!

(Mind you, it was all the rage at the time to have whole collections of funny sounds assigned to all this stuff, movie lines and SFX and what-not, so there were these subtle games of one-upmanship to have a cooler sound scheme than anyone else.)

Not me. I had created the world's most humorless sound scheme. The only possible improvement would've been Ben Stein voicing the whole thing.

But in doing so, after a while, it took on this air of absolute hilarity. Like here's this machine that's capable of anything, it could make a star-trek-transporter sound, but there's just some guy's voice saying "empty recycle bin" with a flat, bored affect.



Did you ever figure out what was causing the sound?


Nope. And every time I asked "is there some sort of program that just logs every time another program makes a sound?", I was told it was deeper system-level magic than anyone sane would ever attempt.




Consider applying for YC's Fall 2026 batch! Applications are open till July 27.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: