Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!unmvax!gatech!ncsuvx!ecemwl!jnh
From: jnh@ecemwl.ncsu.edu (Joseph N. Hall)
Newsgroups: comp.sys.mac
Subject: Re: Kermit question
Message-ID: <3303@ncsuvx.ncsu.edu>
Date: 30 Jun 89 17:53:23 GMT
References: <320@umabco.UUCP> <7233@cg-atla.UUCP> <32533@apple.Apple.COM> <3769@viscous.sco.COM> <6197@microsoft.UUCP>
Sender: news@ncsuvx.ncsu.edu
Reply-To: jnh@ecemwl.UUCP (Joseph N. Hall)
Organization: North Carolina State University
Lines: 24

In article <6197@microsoft.UUCP> stuartb@microsoft.UUCP (Stuart Burden) writes:
>In article <3769@viscous.sco.COM> jamesm@sco.COM (James M. Moore) writes:
>>One thing I've noticed about Kermit (using 9(40)) is that the transfer
>>rate seems very slow.  I'm running a 9600 baud direct connect to a XENIX
>>box, and kermit reports the effective baud rate for file transfers at
>>about 1200. Is there any way to get this speed up, or is this just something
>>I have to live with? 
>Yes, unfortunately, even though the title is very froggy, Mac Kermit is
>a bit of a dog.  It does terminal emulation (vt100) very well, but the
>througput of kermit file transfers is pretty pathetic.
>
Well, you can PAY for a program that Kermits faster, but why bother.
If you're only transferring text files (I've never transferred anything
that wasn't), then you can just TYPE or 'cat' files remotely and capture
them to a text file.  9600 baud throughput (Mac Kermit DOES echo text
FAST, unlike many other terminal programs), no problems.  Sure you
might get an occasional error, but I never have, and my attitude is that
if it's just a text file, a garbled letter won't make any difference, and
if it's a BinHexed file I'll know when it gets decoded.  I suppose if it
was numerical data or something then you might take some extra
precaution, but ...

Anyway, use Kermit for 2400 baud phone modem transfers ... but try just
capturing the text if you've got a 'safe' connection.  Works for me!