Amiga.org
Amiga computer related discussion => Amiga Software Issues and Discussion => Topic started by: Caius on February 06, 2008, 02:01:05 PM
-
Ok, I need some help here guys and gals.
I got this brand new A1200 (Escom). Now I need to install some software on it. My plan was to transfer files over null modem cable with NComm or similar. But first I need to get NComm over to the A1200. Problem is that I got all the AmigaOS 3.1 disks, EXCEPT the Extras disk. And that's where CrossDOS is. So I can't copy NComm from the PC via floppy.
So is there a way to copy files over a null modem cable from the Amiga shell? I seem to remember it's possible to use the AUX device, but I haven't found much info on it so far.
Any suggestions?
EDIT: I know there was a thread about this yesterday, but it concluded with using terminal software, which I obviously can't do.
-
If your A1200 has an harddrive, connect it to your pc and use WinUAE to transfer files.
-
It's a 2.5" drive, and I don't have an adapter to hook it to the PC. :madashell:
-
A 2.5" -> 3.5" adapter is easily bought at a pc hardware store. Beats the hell out of a very slow nullmodem transfer :-o
-
True. But it's a little wasteful in my case. I have a PCMCIA Ethernet card, but I can't use that either until I have the right software on my harddrive.
Thanks, though.
-
According to this web site (in german) (http://caspervalley.my100megs.com/knowhow_seriell.html#adf_2.3), you can run the command "type ser: to dh0:file.bla" on a shell and then start the transfer of a single file on the PC (e.g. with the mentioned program ADF-Transfer). As you already seem to have a suitable PCMCIA network card, I'd recommend transferring the NetworkBootDisk (http://jpv.wmhost.com/NetworkBootDisk/) ADF and tsgui from Aminet (http://aminet.net/disk/misc/tsgui.lha) to put it on floppy. You can transfer everything else you need via FTP afterwards.
EDIT: Typos fixed. :roll:
-
IIRC, using "type file.bla >com1: (or com2:, depending on your pc), can do the very same trick, no needing any program in peecee.
Maybe you need to set the com_x: properties before trying it.
-
Thanks Colani1200, seems we're getting some progress here. I'm now able to transfer files, but they're corrupted when they arrive. Since I don't have the preferences program for the serial port I can't alter the serial settings. That is, I have no idea how to do it outside the prefs prog.
However, I'm pretty sure the default settings are 9600 baud, XON/XOFF handshaking, 8 databits, no parity, 1 stop bit. I've tried both the "type" approach (which apparently doesn't work correctly with binary files from WB2.x and up, the files are chopped off at the end, but text works), and an Arexx script that can be used with ADF Sender Terminal. The latter yields correct file size on arrival, but they're still corrupted.
I've followed the instructions here (http://adfsender.stoeggl.com/adfsenderterminal/methods.html) carefully. God, I feel like such a newbie again. Lol.
EDIT: I have this nagging feeling I should use RTS/CTS for handshaking rather than XON/XOFF. Is it possible to change this from outside the serial prefs program?
-
Turned out I had the fat95 implementation from Aminet, so I got transferred with floppy after all.
Thanks to everyone who answered anyway. I learned a couple of new things in the process.
-
For the record:
PC2Amiga is really hard to beat for that type of thing. Sure, it`s slow (to put it lightly) compared to Ethernet, but is as stable as a big stabley thing.
I used it with my PortJnr years ago at reasonable speed to good effect.
Aminet...
-
I haven't tried that one. I'm transferring at 9-10KB/sec right now with NComm. 19MB in 30 minutes. Nothing to brag about, but it works.
Seems I don't have the adapter for the network card to attach a standard ethernet cable, so I'm stuck with serial transfer for the moment. Oh, well. Reminds me of the old days.
-
Seriously, give that PC2Amiga a whirl. It`s hard to believe how good it is, until you use it every day!!!
-
I may just do that. I'm sure it's more convenient, but I wonder if it can sustain the same speed/stability ratio as NComm?
-
I think it would be easier for someone to let you borrow a disk.
-
No need, it's all sorted. :-)
-
I did something like this a few years back, so my memory will be kinda hazy...
First, NEVER use "type" to transfer files, as it truncates the high-order bit to give you ASCII. This results in a bad file. Rather, use the copy command:
C:\> SET COM1:,9600,N,8,1,X
(you can substitute higher values for the baud rate of 9600)
C:\> COPY filename >COM1:
I'm thinking that the type command has a "/b" (binary) option, but I haven't played with an MS-DOS system for so long...
Also, I just used a "Laplink" cable, which has both 25 and 9 pin connectors on each end, and is supported by Window's "Direct Cable Connection" feature. Also, it has the RTS/CTS wired up, so that option will give you faster transfers.
FYI: When using three-wire serial cables, the sender and receiver need to know when to stop and go. So, they use the Xon/Xoff codes to signal this, which takes time. Also, since there is no clocking signal, the two MUST have really good sync to understand each other, so nothing faster than 9600 is recommended. Alternately, using RTS/CTS allows the hardware to do the handshaking, which means low overhead for the data transfered, as well as higher speeds. The aforementioned connection I used above got transfers between an '030 A2000 and '486DX66 PC at 56Kbps.
On the Amiga side, just go into Prefs and set the serial to match the PC (example above is 9600 baud, 8 bits, 1 stop bit, No parity, RTS/CTS hardware handshaking). I used JRComm on the Amiga, and Telix on the PC to do this, since they both handle Z-Modem transfers back and forth with auto-challenge and negotiation. You could also use DCC or Hyperterminal on the PC.
Hope this helps anyone else looking or needing to do this.
banzai
-
Oopsie! My DOS skills are really lacking...
Try:
MODE COM1:9600,N,8,1,X
COPY filename COM1 /b
The "/b" (binary) mode tells the copy command to ignore any EOFs in the file itself, and to transmit the file based on byte size. This insures that any 68K code in the file isn't read as some form of control code by the PC side, screwing up the transfer.
If you do this from a terminal in Windows, then whatever the serial port is set to with Device Manager will be the mode used, so that command may not be necessary if it's already set.
These, and many more, DOS commands can be found at EasyDOS (http://www.easydos.com)!
banzai
-
MessyDOS... Pah!!