Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!mips!pacbell.com!ucsd!hub.ucsb.edu!ucsbuxa!6500erik
From: 6500erik@ucsbuxa.ucsb.edu (Erik Adams)
Newsgroups: comp.sys.apple2
Subject: Re: Request for Comment on Kermit...
Message-ID: <10684@hub.ucsb.edu>
Date: 19 Apr 91 03:48:04 GMT
References: <hub.ucsb.edu!ucsbuxa!6500erik@UCSD.EDU> <91Apr18.091711edt.23337@ugw.utcs.utoronto.ca>
Sender: news@hub.ucsb.edu
Lines: 16

In article <91Apr18.091711edt.23337@ugw.utcs.utoronto.ca> GRAY@ADMIN.HumberC.ON.CA (Kelly Gray) writes:

stuff deleted

>Kermit was written  specifically for data transfer to and from mainframes
>via the terminal ports. Speed, elegance, and just about everything else
>was sacrificed for RELIABILITY. Kermit may be slow, but it keeps on going
>long after everything else has given up.

This goes completely against my experiences with Kermit, Xmodem,
and Ymodem.  I have found Kermit to be extremely suceptible to
line noise--it stops the transfer at the slightest hint of noise
and I have to start over.  A simple test:  pick up the phone
while transferring a file, and then put the phone back on the
hook.  More often than not, Kermit stops cold.  Xmodem and Ymodem
keep going.  Or at least that's my experience.