Subject: Re: Second Monitor From: Greg Wettstein <NU013809@NDSUVM1.BITNET> Date: Fri, 20 Nov 1992 09:15:25 CST
My newsreader does not include text but this is a followup to the
gentleman who would use kermit if it could do rz/sz.
First of all the new kermit protocols with large block sizes and sliding
windows is not the dog of yesteryear. It may not be as speedy as zmodem
but it is close and it is embedded in kermit.
Secondly it is very easy to start a zmodem transfer from within kermit
provided that you have a slightly older version of rs/sz. You have to
know of course which serial port you are using. Start, for example, sz
on the remote to begin a download, then escape back to the kermit
prompt with ^-ã C (CNTRL backslash, then the letter c). At the kermit
prompt type the following: ! rz </dev/ttys0 >/dev/ttys0
The complete command line should look like this:
C-Kermit>! rz </dev/ttys0 >/dev/ttys0
Note that ttys0 refers to the first serial port, if you were on the second
the device would be /dev/ttys1 etc...
When the download finishes you will be returned to the Kermit prompt,
type connect to get back to the remote host.
Rumor has it that newer versions of rz/sz have been intentionally crippled
by its author to prevent I/O redirection from being used like this. I
cannot attest to this personally but have heard it from a couple of places.
If this is true another sterling example of why the kermit protocol should
be used. Mr. Forsberg seems to have a history of wanting the Zmodem
protocol to become the public standard but doesn't want things to be too
free. Just my opinion of course.
Good luck. The new kermits (we are using 186) have an extraordinary
amount of features built into them. Solid, proven software.
As always,
Dr. G.W. Wettstein
Oncology Research Division Computing Facility
Fargo Clinic / MeritCare
UUCP: uunet!plains!wind!greg
INTERNET: greg%wind.uucp@plains.nodak.edu
Phone: 701-234-2833
`The truest mark of a man's wisdom is his ability to listen to other
men expound their wisdom.'