Path: utzoo!mnetor!uunet!husc6!mailrus!ames!umd5!purdue!i.cc.purdue.edu!j.cc.purdue.edu!pur-ee!uiucdcs!uxc.cso.uiuc.edu!hamilton
From: hamilton@uxc.cso.uiuc.edu
Newsgroups: comp.sys.ibm.pc
Subject: Re: UNIX to PC File transfer
Message-ID: <174200072@uxc.cso.uiuc.edu>
Date: 9 Mar 88 00:29:00 GMT
References: <4655@teddy.UUCP>
Lines: 25
Nf-ID: #R:teddy.UUCP:4655:uxc.cso.uiuc.edu:174200072:000:1223
Nf-From: uxc.cso.uiuc.edu!hamilton    Mar  8 18:29:00 1988


jpn@teddy says:
> Kermit is a protocol that 1. works
> good for text (7 bit) files, and 2.  works on the most brain-damaged of
> mainframe systems (because it uses 7 bit ascii printable characters,
> and does not strain an 80 character input queue).  If this fits your needs,
> then kermit is clearly the protocol of choice.  However, xmodem is almost
> ALWAYS faster (especially with binary files) because it uses an 8 bit
> data path (kermit has a rather inefficient 8'th bit quoting scheme),
> and because it uses a larger packet size.  Using kermit, it is faster
> to download a uuencoded file than it is to download the corresponding
> binary!

    the kermits i've seen use 8th bit quoting ONLY if you specify that
even/odd/space/mark (anything but "no") parity is to be used.  also,
the kermit i use on our unix systems implements the sliding window
protocol, and works just dandy with procomm's sliding window kermit.
only Zmodem is faster.

	wayne hamilton
	U of Il and US Army Corps of Engineers CERL
UUCP:	{ihnp4,seismo,pur-ee,convex}!uiucuxc!hamilton
ARPA:	hamilton@uxc.cso.uiuc.edu	USMail:	Box 476, Urbana, IL 61801
CSNET:	hamilton%uxc@uiuc.csnet		Phone:	(217)333-8703
CIS:    [73047,544]			PLink:  w hamilton