You are currently viewing our archived support Forum. Please visit the Current Discussion Forum if you need to post a new message.
[ Home | Archives Contents | Search | Current Discussion Forum ]
Time: 12:59 PM
Well, I was able to work with this machine last night, and feel I have isolated the problem to exactly 2 possible causes. The first, and most probable cause, is his USB NIC adapter. I have worked with other clients who had similar, but not exact problems with their systems using a USB NIC adapter. My advice is simply to use a PCI NIC, and get rid of the USB adapter...it uses more resources, and in my experience causes nothing but trouble. In 4 different, yet similar cases a USB NIC adapter was the culprit. I will let you know what I find in this case, as I will be heading over there later to install a PCI NIC and see if that does the trick (fairly confident it will). The only other thing it can really be is his video card. He is using a PCI Voodoo3 3000 card (blech). Nuff said. Still, all his other applications, including far more graphic intense apps. than IE6, are running just fine. I guess it is POSSIBLE that something with the card doesn't like IE6, but it doesn't seem too probable (but hey, voodoo cards are barely supported now, the PCI versions sucked before they were made, and who knows what the freaky drivers which have ALWAYS sucked are doing in that app). Again, I point to the USB adapter, but I will let you know what I find. Short of this, I have exhausted all other possibilities, having examined his Registry with a fine-tooth comb, and manipulated MSCONFIG to the Nth degree, heh. If it isn't the NIC or Video, its Reformat time, because I can rebuild the drive 10 times faster than I could figure out what the heck would cause such a subtle, strange error now that I have examined the machine from the BIOS up (and yes, there was a BIOS upgrade for his mobo...it didn't help, heh). I'll keep you informed.