|
Register or have you forgotten your password?
|
|
|
| Amiga Software Issues and Discussion This forum exists for the discussion of the use, issues with, and fun brought about by classic and next generation Amiga software. |
![]() |
|
|
Thread Tools | Display Modes |
|
|
#16 | ||||||||
|
Hobbyist
![]()
Join Date: Dec 2005
Posts: 66
|
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 |
||||||||
|
|
|
|
|
#17 | ||||||||
|
Hobbyist
![]()
Join Date: Dec 2005
Posts: 66
|
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! banzai |
||||||||
|
|
|
![]() |
| Bookmarks |
| Tags |
| modem , software , terminal , null , transfer |
| Thread Tools | |
| Display Modes | |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| WTB: null modem cable 25/9 | Amiduffer | Amiga Marketplace | 4 | 02-24-2008 12:46 PM |
| null modem cable | amiga4001 | Amiga Hardware Issues and discussion | 3 | 11-05-2007 03:20 PM |
| Problems with transfering files with null modem cable via Adf sender terminal | GreenBeret | Amiga Hardware Issues and discussion | 4 | 10-12-2007 11:25 AM |
| Null modem the next Gen ? | Godfather | Amiga Hardware Issues and discussion | 4 | 01-06-2007 11:41 AM |
| Null modem cables | Managarm | Amiga Marketplace | 14 | 04-29-2005 07:44 AM |