The MicroShaft update problems never cease to amaze me. ;-) On WinME, I was getting constant "msimn caused a [something] in mshtml.dll". This would happen almost EVERY time when I was typing an email, and would use my mouse's thumb button to [enter]. The mouse is a Logitech MouseMan Cordless optical. Since they are as bad with drivers as ATI, I tried new drivers. Well, with them, you can't EVER remove the mouse icon from the system tray! Also, it did not fix the problem. Now what got me is the EXACT error ALSO happened when I was hitting the [enter] key on my keyboard! So, that's obviously NOT a mouse problem. it's a really serious crash, the email I'm working on disappears, OE totally crashes, and the system stability gets messed up. On XP Pro, the same thing happened, but the stability was OK afterwards. THIS time I traced the cause of the problem (surprise surprise) to the #$%& updates! I did not have this problem on XP AT ALL, until I installed some updates! I trashed all the updates (restored) and the problem is gone.
Now, the obvious problem is trying to find out which update is causing this. Sure, I could install one by one, one per day, and wait a week, but with 30 XP updates, I'd be at this for months. I could not find anything on this EXACT problem, but many similar regarding mshtml.dll problems. Most were the displaying of webpages, dragging things to Word, etc, but I could not find any that were caused by hitting the [enter] key on the keyboard or the thumb button on my mouse (it's programmed to perform the [enter] function). Does anyone have any idea just which update could be causing this problem? Or, would anyone know how to fix the problem after the updates have been installed? I've thought of the following: saving copies of mshtml.dll (of which I already did, I have several. One original from the XP CD, one in the SP1 folder, one I found in another folder, and the one that was in the system folder of which had the problem). There are 3 different sizes; one is 99k, one is 124k, the other size is 125k. All versions are the same prefix, but a different suffix. Would it be feasible to simply drag these one by one into the system folder until the problem is corrected? I would think using the one that is in the SP1 update might be the one to go with, since I had no problems with it. Or would the command, run: regsvr32 mshtml.dll fix the problem with the problematic mshtml file? I've heard that DID fix other mshtml.dll problems. I'm about 60 seconds from NEVER EVER screwing with an MS update again. I'll run my AV software, firewalls, etc, and take my chances. The patches and updates are nothing but a computer destroyer. I now see just how dozens of M$ security updates and patches make a PC more "secure".....it destroys it! <laughs> After all, it *is* pretty hard to ha*k into a PC that won't run! LOL! -Clint God Bless Us All Clint Hamilton, Owner Want to exchange links with us? http://OrpheusComputing.com © ============= PCWorks Mailing List ================= Don't see your post? Check our posting guidelines & make sure you've followed proper posting procedures, http://pcworkers.com/rules.htm Contact list owner <[EMAIL PROTECTED]> Unsubscribing and other changes: http://pcworkers.com =====================================================
