Re: Null modem problems

[rubywand@aol.com]

In article <32AB926B.446C@earthlink.net>, Michael Ater
<michaelater@earthlink.net> writes:

>
>I am trying to move some files from an Apple IIC+ to an IBM an I am 
>unable to get the null modem drivers on the different systems to work 
>together. Any useful assistance would be appreciated.
>
>

     It could be that using "NULL modem drivers" is complicating things.
You should be able to do transfers with modem software in 'terminal mode'
on each machine. (If a "NULL modem driver" is just a simple setup for
machine-to-machine transfers, it probably does no harm.)

     Mainly, you need to match baud rates (e.g. both programs are set for
2400 Baud, 9600 Baud, or whatever) and protocols (e.g. the sender and
receiver are both set to X-modem, Z-modem, etc.).  Also, you do not want
either program to send a bunch of special setup codes to the other--
sometimes, these can mess up transfers.

     Check your settings for timing out. Both programs should be set to
wait for at least 30 seconds for the Sender (or Receiver) to get started.
This gives you time to, say, start Send on one machine and, then, get
Receive going on the other. (There is no need to start both operations at
once-- in fact, it is probably not a good idea.)

     Check your PC comm port settings. If you are using an internal modem
on the PC, you may have to diddle some "Config" or "Options" setting in
your telecom program to use the external serial port. 

     Check your connections. There should be a modem cable coming from
each machine. Each cable plugs into the NULL modem connector. 


Rubywand