Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!mips!news.cs.indiana.edu!noose.ecn.purdue.edu!en.ecn.purdue.edu!platkus
From: platkus@en.ecn.purdue.edu (Shawn W Platkus)
Newsgroups: comp.sys.apple2
Subject: Re: Request for Comment on Kermit...
Message-ID: <1991Apr16.045328.17682@en.ecn.purdue.edu>
Date: 16 Apr 91 04:53:28 GMT
References: <8593@crash.cts.com>
Organization: Purdue University Engineering Computer Network
Lines: 19

In article <8593@crash.cts.com> edwatkeys@pro-sol.cts.com (Ed Watkeys) writes:
>What's the big deal with Kermit?  Ther version I saw isn't that great.  I'm
>not trying to put the thing down, but is there something about it that is
>special?  What is the deal with the "Server" command in Kermit?  I
>downloaded the application, but I never spent the three hours getting the
>docs...  
>


I agree with you that Kermit isn't that great, and if you have ever used Kermit
on unix or a mac or IBM pc or any other machine, it takes about 2 sec to figure
out the Apple 2 version.  But to answer your question, if you have to use Kermit protocol, what other program on the Apple 2 (e or GS) are you going to use?

I do use Proterm's kermit for most things that I need kermit for, but it
doesn't seem to be a true standard kermit.  I use the Apple 2 Kermit for 
sending and receiving data from my HP48SX.  I tried the kermit in proterm
for this, but it royally screwed things up when receiving from the HP.  

Platkus