Amiga.org
Amiga computer related discussion => Amiga Software Issues and Discussion => Topic started by: apsteinmetz on May 13, 2016, 04:17:23 AM
-
This error message is on the windows side.
I carefully matched the com port specs on the Amiga and Windows side.
I am using a new Startech.com "1 port FTDI USB to RS232 null modem adapter."
The weird thing is, I successfully bootstrapped the Amiga side by transferring AExplorer to the Amiga over the serial cable and am running it successfully. So I know my settings are correct. Is it possible the cable works in one direction and not the other? There was handshaking during the bootstrapping, I assume.
So, I'm running AExplorer on the windows side but Windows explorer throws the "error reading from com port" messasge and doesn't see the Amiga.
Can anyone help? Thanks.
-- Art
-
Chceck if the cable is "7 wire". While there are also 3- and 5-wire nullmodem cables, AmigaExplorer uses hardware control flow, so it needs 7 wires.
-
Thanks. The chip used from FTDI supports all 9 lines into USB but I guess I need to check the DB15->db9 adapter.
-
Closing the loop on this thread. AmigaExplorer spontaneously started working. Don't know why. I checked my pins and they were correct but I didn't do anything. FWIW, I get the "Error reading from COM port" message now when there is a disk read error on the Amiga side (as there often is with ancient disks).
AmigaExplorer is pretty cool, especially the way it bootstraps itself from the Windows side. I jacked up the BAUD rate to 57900 on my Amiga 2000/'030 2.04 without a problem.
These were the connectors I used:
USB to DB9 Serial
https://www.amazon.com/gp/product/B008634VJY
and
DB9 to DB25
https://www.amazon.com/gp/product/B000087RYP