Currently, ADTPro is working directly into a serial port on an old Windows XP machine. Works like a charm. I would like to retire the computer and use ADTPro with my desktop machine which, of course, has no serial ports. Run to Fry's Elec and buy an AirLink USB Serial Adapter. Install the driver, configure ADTPro for com 3 (that's where the com port shows up in Device manager), 115,000 b/s, 8 data, no parity, 1 stop, no flow control.
Turn off the firewall and anti-virus on the XP machine.
No changes to the gs.
Fire up ADTPro server and client. Attempt a file xfer. All seems to be working until I select the volume to xfer to, the xfer starts but no xfer happens. And the server side times out.
The server dos box says "SerialTransport opened port named Com3 at speed 115,000'
CommsThread.sendPacket<> block: 0 offset: 0
CommsThread.sendPacket<> backoff sleeping for 0 seconds
The last two lines repeat until it times out.
Suggestions ?
It could be that the driver would rather have the port mapped to COM1 or COM2. But the most likely culprit is the driver itself. Do you have any indication of the chipset? HugePine, Prolific, other?
It's a Prolific driver, ver 2.0.0.18, dated 7/16/2003. Would another driver work ?
Went ahead and installed a newer Prolific driver and there is partial success. The file xfer is working but slowly. The new driver is Prolific, dated 11/20/2007, ver 2.0.2.8.
The speed is approx 10-15% compared to a direct serial connection on the other XP machine.
Hmmm. Turns out that's the same driver I have for my prolific USB converter. Macs won't work at all with older drivers, and need the most up-to-date ones to survive. PCs have been a different story, though there are lots and lots of USB cable builders that use Prolific chipsets.
That's pretty strange too. I haven't heard of that happening before...
Well, maybe I'll just pick up a serial card. Any excuse to go to Fry's !!
Looking at Device Manager, it shows a com 1, but there is no DB9 anywhere on the motherboard. I've tried disabling it, but no difference.
I'll keep poking around, if you think of anything ...
If I plug in a USB serial adapter to a machine that has a serial port or two in it already, it gets assigned to COM6. The ADTPro serial library doesn't seem to play nice with that high a port, so I always map it back down to COM1 or 2. Windows sometimes complains that the port is already occupied, but it seems to ultimately allow it. And that allows me to use the USB adapter too. So, long and short of it: Try mapping it down low, and see what happens.
Remapped the com port from com3 to com1, no change.
I did find the serial port on the motherboard. The header is hiding between the ram slots. Went ahead and ordered a cable, I'm sure all will function correctly when ADTPro sees a proper serial port.
In the meantime, the old machine will just have to remain operational.
Thanks for your help, David.
I could never get this USB/RS232 converter to work with ADT, though I didn't know that you could remap ports. After fussing with it a bit, I borrowed a port replicator/docking station which had real, low numbered RS-232 ports. I'd be interested to know if someone solves this issue, since it would save having to borrow that docking station, in the future.
Regards,
Mike Willegal
Some USB converters are better than others. I have a couple that simply don't work well. Do you have a branded one, or a no-name import?
I had a keyspan adaptor and an IBM branded one with parallel printer port included. I believe I tried both, but it's been a while. I recently obtained a cut little job with a CODI label on it. Maybe I'll give that one a try.
Regards,
Mike WIllegal