I just learned that I have a reputation for being able to solve really hard problems here at work. Gee...since that's my job wouldn't you think that would be likely. Anyhow.. apparently most people can't figure out what DLLs come from which programs. So when they get a big nasty error box with lots of scary numbers and memory addresses you bring it to me. I did this trick 3-4 times for one of our developers. Somebody else runs into a problem, asks him about it and he brings an audience I swear 3 of them come in to grab a piece of paper off the printer and hand it to me, so I can figure out what is causing the big nasty error.

Allow me to share my secret with you. I find the name of the DLL or OCX or whatever threw the error and if I don't recognize it immedately I search on it on google. Usually after the first 2-3 entries of people who have archived every DLL on earth, you get an entry or three which tell you what program the DLL is from, and you can figure it out without even clicking the link.. just reading the summary. Add a bit of drama here (do a DOS search for the DLL on your box here or soemthing if you must preserve your mystery factor). Then turn around and say... Its Real Player, (or whatever the offending program is). They all go OOOOH and turn and walk away singing you praises. If you are feeling really kind, and the person is usually pretty sharp you can find an entry that might relate and IM the link to their desks. In this case I am fairly sure it was a buffer overrun in a RealPlayer DLL. Yea me. I have reasarch skills.