The mysterious USB to Serail problem ...
-
What would interfere or cause an interupt? Windows xp pro, usb to serial with prolific 1.8 drivers (I think... sorry tried three diff versions thus far), legacy hardware enabled, power disabled on usb root, serial mouse detection turned off (uses usb mouse anyway and PS2 connected keyboard). 232 data converter to usb to serial and the application is based on .Net 2.0 / Visual Fox Pro (not my app). Besides the monitor, no other connected devices for i/o. Has all updates. Everything seems to test fine. (Telnet to 232 works as well) I am at my end of knowledge or just missing the obvious. Suggestions? It works about an hour'ish and then just stops.
-
What would interfere or cause an interupt? Windows xp pro, usb to serial with prolific 1.8 drivers (I think... sorry tried three diff versions thus far), legacy hardware enabled, power disabled on usb root, serial mouse detection turned off (uses usb mouse anyway and PS2 connected keyboard). 232 data converter to usb to serial and the application is based on .Net 2.0 / Visual Fox Pro (not my app). Besides the monitor, no other connected devices for i/o. Has all updates. Everything seems to test fine. (Telnet to 232 works as well) I am at my end of knowledge or just missing the obvious. Suggestions? It works about an hour'ish and then just stops.
I always use PortMon http://technet.microsoft.com/en-gb/sysinternals/bb896644.aspx[^] to tell me what's really happening with serial problems though of course it may be a USB problem instead. You could use it then have a look for anything when it fails...
-
I always use PortMon http://technet.microsoft.com/en-gb/sysinternals/bb896644.aspx[^] to tell me what's really happening with serial problems though of course it may be a USB problem instead. You could use it then have a look for anything when it fails...
I did not catch anything of significance. I did find that I would get a contious receive. I think the dc is bad. However, with all of this I did switch machines (so to speak ... hit the junk pile and built one from pieces and parts) and had the same problem. After some time, I had a light-bulb go off inside my head. Update the chip set drivers. It worked. Stupid me. I should have considered drivers on the previous machine. It just never even crossed my mind that they could have updated or needed to update with a Win Update. Ouch ... such a newbie mistake.