Page 1 of 1

OPEN COM() Problems with Belken USB/Serial adapter...HELP!

Posted: Thu Dec 28, 2006 10:55 am
by CDRIVE
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

Posted: Sat Jan 06, 2007 12:17 pm
by Dav
Hi CDRIVE. Don't know if I can help you directly, but maybe I can help google search a solution.

As for me, I've never been able to get any USB device to work under DOS. Other have accomplished it, somehow.

From what I've read, DOS programs can't access a USB port directy without a special drivers - even if the port has an adapter on it. I've found one such driver that seems to work with many devices connected on USB ports, so several people claim. Here's one page - may be worth reading...
http://www.computing.net/dos/wwwboard/forum/13447.html

I don't know how this fits in with XP, as I'm still an XP newbie (die-hard win9x/dos user until recently).

I'll post here again if I have anything worth posting. In the meantime, good luck to you.

- Dav

Posted: Sat Jan 06, 2007 2:52 pm
by {Nathan}
Try FreeBASIC. It runs natively under windows and can probably open the COMs.

www.freebasic.net

Posted: Sun Jan 07, 2007 7:33 am
by Antoni
Nathan is right , I regularly use a FreeBASIC program accessing a serial port thru an USB adapter.

Posted: Sun Jan 07, 2007 11:34 am
by CDRIVE
Thanks for the input guys. I installed the Belkin drivers on my W98SE machine but it's not working at all on that machine. Not even in Hyper Terminal. If & when I get it working on W98 I will try Commport access through QB, and I'll let you all know what happens.



Thanks,

CDRIVE

Posted: Thu Feb 15, 2007 1:20 pm
by burger2227
Windows 98 already can use a port. If you need to add one use a cheap PCI card port. USB is tough in 98. Near impossible in XP because it protects the ports from access. Try PortTalk in XP

Posted: Sat Feb 17, 2007 11:24 pm
by seaBiscuit$
When I was fooling around with my parallel port, I found a great driver that opens any I/O ports you want called userport. It could help.

Posted: Sun Feb 18, 2007 11:15 am
by CDRIVE
Do you have the link to the site that you got this from?

Oh! I hate your avatar too! It creeps me out! :shock:

CDRIVE

Posted: Sun Feb 18, 2007 9:37 pm
by seaBiscuit$
Sorry about that. Here it is.

http://www.embeddedtronics.com/design&ideas.html

I'm not sorry about my avatar. The two-legged horse stays! :)

Posted: Sun Feb 18, 2007 11:48 pm
by CDRIVE
Thank you for the link & I'll learn to live with the creepy horse. :)

CDRIVE