pm@cwruecmp.UUCP (Prabhaker Mateti) (05/22/87)
The rx/sx entry was inadvertently omitted from the Gulam manual; so
here it is. Note also that due to a lazy editing error, some shell
vars are listed as ..._command where they should really be ..._cmd.
--
>> rx/sx -- Xmodem File Transfers <<
These are built-in commands. Rx receives a file from the remote
system; and sx sends a file to the remote system using Xmodem
protocol.
rx fnm
command opens/creates file fnm for writing. If the shell
variable `rx_remote_cmd' is set, Gulam constructs a command for
the remote system as "$rx_remote_cmd fnm", and sends this
command through the rs232 port, and then awaits the packets.
For use with our 4xBSD Unix, we set this var to `xm st'. Unless
the `xm' on the remote machine is of the quiet type (one that
does not respond with, say, "Xmodem: Ready to send..."), setting
rx_remote_cmd actually prolongs the first synchronization. If
this var is unset, you should first switch to remote (say using
te command), and issue the appropriate command to the remote,
and then switch back to AtariST and the give the rx fnm
command.
sx fnm
is essentially similar. Gulam opens fnm for reading, sends
"$sx_remote_cmd fnm", if that var is set, and awaits the first
sync. For our 4xBSD Unix, we set sx_remote_cmd to 'xm rt'.
If sending/receiving binary files use 'xm rb' or 'xm sb'. Note
that files received with Xmodem usually contain extraneous bytes
at the very end of the file. With text files, you often see a
bunch of ^Zs.
--
prabhaker mateti, case western reserve university, cleveland, oh 44106
decvax!cwruecmp!pm pm@Case (pm%Case@csnet-relay) (216) 368-2816!