Today marks my 1-year anniversary of joining Yahoo to work on the Messenger team. I should probably chart my blog postings during that time to see how they’ve slowed — last year I had a better balance between work and personal time but in 2005 it’s really swung towards work.
On the plus side, it’s good to be working for a company with a generally-rising stock price. Of course, Palm was like that for a while too, so I know better than to count on these things… :)
I just returned from a few days in Vegas for this year’s Perforce User Conference. Overall it was a great event. We had two pretty full days of presentations by both Perforce as well as users. The talks were pretty good, but the best value was meeting many of the folks from Perforce and industry, making contacts, and getting our questions answered.
For the past week or so, I’ve been having trouble with running Messenger where I could when a buddy was typing and I could send text, but could not receive. I figured it was something funky with the current project we’re working on, so I uninstalled and went back to 6.0 which had the same problem.
I know that Messenger uses host IE browser controls for much of the dynamic content, so I dug a little deeper and found some other similar applications were also busted (like System Restore and Windows Help Center). (It was a little disconcerting that System Restore doesn’t seem to have a command-line alternative. If you somehow honk your IE installation, System Restore won’t be of any use.)
My home machines have all been upgraded to Windows XP Service Pack 2, so I went so far as to uninstall, then reinstall it. Even after that sequence, the problem remained.
I noticed that in the About box, the version number and product ID were blank which is really odd. But, it was the right clue that helped me search for the ultimate solution.
The IEFix utility site revealed the problem, pointing to a topic on WinXPTutor.com that listed several symptoms caused by some IE components that were not registered (or became unregistered at some point). A quick re-registration of mshtmled.dll, jscript.dll, and mshtml.dll solved the problem!
Now to figure out what caused this mess. Hopefully it wasn’t something from my current project…