Path: utzoo!mnetor!uunet!husc6!bloom-beacon!oberon!skat.usc.edu!blarson
From: blarson@skat.usc.edu (Bob Larson)
Newsgroups: comp.sys.misc
Subject: Re: Error-Checking Xfer Protocols
Message-ID: <7454@oberon.USC.EDU>
Date: 7 Mar 88 00:33:30 GMT
References: <8803022236.AA25500@ucbvax.Berkeley.EDU>
Sender: news@oberon.USC.EDU
Reply-To: blarson@skat.usc.edu (Bob Larson)
Organization: USC AIS, Los Angeles
Lines: 20

In article <8803022236.AA25500@ucbvax.Berkeley.EDU> 7GMADISO@POMONA.BITNET writes:
>Part of the beauty of the Xmodem standard is that it's a compact, simple
>standard that can be implemented on virtually anything (and it has been).

Part of the ugly of Xmodem standard is that it can't be implmented on
much of anything.  It's fine for what it was designed for (cpm to cpm
file transfer) but not for what some people are claiming it is good
for (anything to anything file transfer).  Xmodem requeires full 8-bit
non-translated data paths that can handle 132 character bursts.  The
fact that single character errors can ruin a whole session is just
something extra to help me avoid it.

Kermit is much more portable and works under hostle conditions.
Windowed kermit is much faster than standard xmodem.  Many versions of
kermit are available from the columbia archives, contact
info-kermit-request@cu20b.columbia.edu if you don't know how to get them.
Bob Larson	Arpa: Blarson@Ecla.Usc.Edu	blarson@skat.usc.edu
Uucp: {sdcrdcf,cit-vax}!oberon!skat!blarson
Prime mailing list:	info-prime-request%fns1@ecla.usc.edu
			oberon!fns1!info-prime-request