OPEN COM() Problems with Belken USB/Serial adapter...HELP!
Posted: Thu Dec 28, 2006 10:55 am
I just installed a Belkin (F5U109) USB to Serial adapter on my XP laptop which has no serial ports. I assigned it to COM1 in the Device Manager and attempted a Hyper Terminal connection through one of my old Hayes modems. Windows recognized it as a serial port and the connection went off without a hitch. I thought I was all set to go in QB and that QB would also recognize the port. Well that notion was short lived. My COMM programs are kicking back a "DEVICE TIME OUT"- (ERROR CODE 24) on the OPEN COM line. Interestingly enough a short TSR program using "SHELL" & "MODE" returns the port parameters ok (so DOS sees the port) but it also generates an error on the OPEN COM() line. This time I get a "DEVICE FAULT" (ERROR CODE 25). Both are related to time outs.
Is anyone out there using one of these adapters on XP? If so, do you experience the same problems? I've read that XP does not permit direct access to ports, and that even if I had a REAL serial port on this machine I wouldn't be able to access it with an OPEN COM() statement. Is this true? If so, then how do I call this port / adapter? It's listed in the Device Manager as ......................
"Ports (COM & LPT)". The drop down is listed as "Belken Serial On USB Port (COM1)". Both lines display the typical cable plug icon for ports.
Can someone suggest a work around? Do I have to call the device through the Windows API? If so, I don't have a clue as where to start.
Any input will be appreciated.
Thank you,
CDRIVE
Is anyone out there using one of these adapters on XP? If so, do you experience the same problems? I've read that XP does not permit direct access to ports, and that even if I had a REAL serial port on this machine I wouldn't be able to access it with an OPEN COM() statement. Is this true? If so, then how do I call this port / adapter? It's listed in the Device Manager as ......................
"Ports (COM & LPT)". The drop down is listed as "Belken Serial On USB Port (COM1)". Both lines display the typical cable plug icon for ports.
Can someone suggest a work around? Do I have to call the device through the Windows API? If so, I don't have a clue as where to start.
Any input will be appreciated.
Thank you,
CDRIVE