Path: utzoo!attcan!uunet!mailrus!cs.utexas.edu!uwm.edu!ogicse!plains!wilken
From: wilken@plains.UUCP (Scott Wilken)
Newsgroups: comp.sys.apple2
Subject: Re: PROterm kermit madness
Message-ID: <3743@plains.UUCP>
Date: 10 Mar 90 17:47:20 GMT
References: <223.25f80867@drycas.club.cc.cmu.edu>
Reply-To: wilken@plains.UUCP (Scott Wilken)
Organization: North Dakota State University, Fargo
Lines: 23

In article <223.25f80867@drycas.club.cc.cmu.edu> taxman@drycas.club.cc.cmu.edu (Mike Wommack) writes:
>Has anyone had any problems with Proterm's Kermit protocol? When I 
>needed to upgrade my version of kermit I d/l a BINSCII'd version of 
>kermit, BINSCII barfed saying there was a bad CRC. I retried the d/l, 
>same results..bad CRC from Binscii. Next, I had an old text file that I 
>hadn't unbinscii'd, binscii unpacked it just fine so the binscii side is 
>okay. Is PROterm's kermit a true Kermit? 

I use ProTERM's kermit pretty often actually.  Almost never with our Solbourne
system (it would be nuts to use kermit when you could use x or ymodem), but
several times a week with our IBM mainframe.  I've never had a problem.  Could
it be that maybe you have something configured wrong on the remote kermit?  Or
maybe an early version of ProTERM?  I'm using v2.1 so I guess I cant speak for
2.0 or lower.

Scott


-- 

    Internet:  wilken@plains.nodak.edu           America Online:  Wilken
    UUCP:      ..!uunet!plains!wilken            GEnie:           S.WILKEN1     
    BITNET:    WILKEN@PLAINS                     Delphi:          SWilken