Win2k driver issue: error Code 31, USB-serial port
Trying to troubleshoot a stubborn old Windows 2000 pc, this one's been bugging me for months, can't nail down a pattern. Just when I think I figured it out, it does the opposite.
It's using a B&B USOPTL4 port convertor, and on almost every cold boot the device isn't recognized and gives error 31 in device manager. Reinstalling the driver manually and rebooting fixes it, and even just rebooting usually fixes it too. I suspected the convertor itself so I bought the new version, USOPTL4, but no change.
The B&B site points me to download a driver package that installs a new entry into Add/Remove programs, but the system will still run without that and just installing the driver manually, it doesn't act any more or less reliable using either method.
Has anyone seen the error 31 and figured out how to get around it in Windows 2k? It's a fairly old system, probably getting close to 10yrs. Could a flaky motherboard be the root cause?
Much thanks for any tips on where to check.
Sounds like hardware incompatibilities and most likely won't be able to use it.
It shouldn't be incompatibilities, the system was designed to run this way, it did for a few years, and there are other units built to copy it that have run fine for almost as many years. Actually the more I think about it, the more it seems like old hardware dieing, motherboard mostly.
I was hoping there was a known fix for error 31 codes in Win2k that I could try quickly before writing the system off.
|All times are GMT -7. The time now is 09:47 PM.|