Amiga Explorer

[Oldsmobile_Mike]

You already said it was working fine until it suddenly stopped. Why do you think an older version would work?

[kirk_m]

Is your Amiga networked?  If so, why not configure it to use ethernet for transfer instead of null modem?  I just did that 2 days ago to backup my A3000's entire HD to my laptop PC.

[Kernel]

I've had issues using a USB to COM adapter when connecting it to a USB HUB... straight to computer USB port and all is well.  I've had to play with port speed as well to get a stable transfer.  Might not be your issue but figured I'd chime in...

[RiP]

I have even tried different fresh OS (Win7 x64) but no luck, tried Workbench 1.3, works fine when I write Type SER: to RAM:Setup
Also pressing Ctrl+C then OK will show *BREAK* on Amiga side but fails in the next step: RAM:Setup (+RX in WB 2.0)

I connected 56k modem to the PC to check if the port is healthy or not but don't know what to do more

Is your Amiga networked?  If so, why not configure it to use ethernet for transfer instead of null modem?  I just did that 2 days ago to backup my A3000's entire HD to my laptop PC.

No LAN card in my Amiga 2000.

[Thomas]

Connect the Amiga to the PC with your nullmodem cable and run a terminal program on both computers (for example HyperTerm on Windows and NComm on the Amiga). Enter some text on one end and check what is received on the other end. If you see what you entered, everything is fine. If you receive garbage, either the parameters (baud rate, start-/stop-/parity-bits) aren't matching or the hardware does not work correctly. If you receive nothing, it's surely the hardware.

[RiP]

Connect the Amiga to the PC with your nullmodem cable and run a terminal program on both computers (for example HyperTerm on Windows and NComm on the Amiga). Enter some text on one end and check what is received on the other end. If you see what you entered, everything is fine. If you receive garbage, either the parameters (baud rate, start-/stop-/parity-bits) aren't matching or the hardware does not work correctly. If you receive nothing, it's surely the hardware.

Would you please explain more? I'm newbie =/

I have TeleTerm and Term 4.3 with USR 56K EXT COM modem. Would it be useful to test the port?
I tried to dial a number with default settings but didn't work. "TR" LED turns on when I open those programs but no more things.

[kirk_m]

Would you please explain more? I'm newbie =/

I have TeleTerm and Term 4.3 with USR 56K EXT COM modem. Would it be useful to test the port?
I tried to dial a number with default settings but didn't work. "TR" LED turns on when I open those programs but no more things.

A null modem is just a cable with an identical gender connector on each end. Forget about using the actual USR modem to test in this scenario. The Null modem cable allows you to connect two computers together via their serial ports for communication, in lieu of a modern ethernet connection.  Both computers need to be running a terminal program as Thomas said, and, the serial ports on both computers have to have the same settings (baud, parity, xon/xoff or cts/rts flow control, bits (data and stop)).  Use settings 8 N 1, CTS/RTS, and 19200 baud settings on both computers and see if it works.  8 Data bits, No parity, 1 stop bit, Clear to send/Ready to Send flow control, 19200 baud is what all that mean.  Follow Thomas' instructions to verify you've set them both the same.  If you get the same output on both screens, you know your hardware is working right.

[utri007]

I did this just few weeks ago. PC/Windows sida I used Putty, configured it to use serial, speed was 9600. I made identical settings to Amiga side. Worked easily, set up took about 3 minits.

[RiP]

A null modem is just a cable with an identical gender connector on each end. Forget about using the actual USR modem to test in this scenario. The Null modem cable allows you to connect two computers together via their serial ports for communication, in lieu of a modern ethernet connection.  Both computers need to be running a terminal program as Thomas said, and, the serial ports on both computers have to have the same settings (baud, parity, xon/xoff or cts/rts flow control, bits (data and stop)).  Use settings 8 N 1, CTS/RTS, and 19200 baud settings on both computers and see if it works.  8 Data bits, No parity, 1 stop bit, Clear to send/Ready to Send flow control, 19200 baud is what all that mean.  Follow Thomas' instructions to verify you've set them both the same.  If you get the same output on both screens, you know your hardware is working right.

Then won't an external modem with straight com cable (not null modem cable) work with Amiga?
I just need to check if the Amiga's COM port is healthy or not.

I did this just few weeks ago. PC/Windows sida I used Putty, configured it to use serial, speed was 9600. I made identical settings to Amiga side. Worked easily, set up took about 3 minits.

Would you please show me step by step?

[Oldsmobile_Mike]

Would you please show me step by step?

You guys should make a YouTube video, that's what I do when folks ask for stuff like this.  Probably faster than trying to type 983457938457 words.  

[kirk_m]

From a terminal screen, issue the command ATDT followed by a phone number and see if it dials, then.  I'd still use 8N1 CTS/RTS settings and whatever the max speed the amiga com port supports.  Modem, of course, will need to be plugged into a phone line, else it might detect no dialtone and not follow the command.

[RiP]

Well, I tried "Method A1: TYPE command and prepared file" from here: (buffer:1024)
http://adfsender.stoeggl.com/adfsenderterminal/methods.html

I got 'Transdisk' tool successfully in df0:c

12/2/2016, 1:48:11 AM
SENDING 'C:\Users\...\Desktop\transdisklong' at 19200,n,8,1 RTS/CTS
100% sent!
Transfer time = 00:00:09 for 'C:\Users\...\Desktop\transdisklong'
CRC32: 6B81914E

12/2/2016, 1:48:51 AM
SENDING 'C:\Users\...\Desktop\transwarp' at 19200,n,8,1 RTS/CTS
Transfer cancelled!
Transfer time = 00:00:12 for 'C:\Users\...\Desktop\transwarp'
CRC32: E2EF5C6F

But I don't know what to do with it later. I opened it in WB 1.3 or even 2.05 but got this:
https://vid.me/SDTy

:angry:

Edit: I tried this command: "transdisk -w ser: -d trackdisk 1" but I got this error: "unable to open trackdisk.device"

EDIT2: I tried this command and finally it worked!!!
"transdisk -w ser: -d trackdisk 0"

Now I want to know that is my COM port healthy 100%? If yes so why doesn't Amiga Explorer work? :angry: