Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!unmvax!unm-la!lanl!beta!ttp
From: ttp@beta.lanl.gov (T T Phillips)
Newsgroups: comp.binaries.ibm.pc.d
Subject: Re: Thanks to everyone who helped with SIMTEL20
Summary: uuencode-decode vs. Zmodem, Kermit, etc.
Message-ID: <22940@beta.lanl.gov>
Date: 9 Dec 88 18:50:34 GMT
References: <15632@iuvax.cs.indiana.edu>
Organization: Los Alamos National Laboratory
Lines: 23

In article <15632@iuvax.cs.indiana.edu>, bobmon@iuvax.cs.indiana.edu (RAMontante) writes:
> You might try using zmodem/ymodem protocols for host-to-pc transfers.
> Doesn't require uuencoding, and I routinely get better than 230
> chars/sec at 2400bps.

My circumstances are a little peculiar in that our line to our
Unix mail server passes through a couple of computers, encryptors
and decryptors, multiplexers and demultiplexers.  All that
hardware between us and our Unix machine raises havoc with error
correcting packet type protocols.  By trial and error, I have
found that the largest packet that can be passed reliably is 24
bytes.  Larger packets clobber the link and you have to start
over.  

The system is very reliable, however, for ascii transfers at
9600 baud.  I get about 700 chars/sec downloading ascii files,
but as I mentioned in an earlier posting, I don't have a way to
upload ascii characters rapidly.  I may try to write something.
Incidentally, if I use a telephone link directly to the Unix
computer, I can use sz and rz very effectively.

I would still like to find a small Unix program that sets up a
large buffer and accepts ascii transfers at high speed.