Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!clyde!uunet!cs.utexas.edu!wuarchive!kuhub.cc.ukans.edu!shawl
From: SHAWL@kuhub.cc.ukans.edu
Newsgroups: comp.sys.atari.st
Subject: Re: What Kermit/UNITERM bugs?
Message-ID: <19315@kuhub.cc.ukans.edu>
Date: 5 Dec 89 20:04:55 GMT
References: <2748@dogie.macc.wisc.edu>
Organization: University of Kansas Academic Computing Services
Lines: 22

In article <2748@dogie.macc.wisc.edu>, gilmore@vms.macc.wisc.edu (Neil Gilmore) writes:
> In article <8912010813.AA04349@ucbvax.Berkeley.EDU>, 01659@AECLCR.BITNET (Greg Csullog) writes...
> 
>>One netter mentioned problems with UNITERM's Kermit. On our site, which
>>has a CYBER 830/990 combo and various VAXs, such as an 8550, the only Kermit
>>that works flawlessly with full server support is UNITERM's Kermit. Some
>>20 - 40 people use it almost daily. I use UNITERM Kermit in text or binary
>>mode almost every day and I have never had one problem. I've tried Versa-Term
>>Pro and Red Ryder under Mac emulation but they do not have server support.
>>Neither does ZSTEM or SmarTerm 240 for the PCs. The ONLY Kermit I trust is
>>UNITERM's so WHAT problems are there?
> 
I agree with much of what is said, but with some modification.  Until
very recently, I was using version 1.7b; it worked flawlessly in all
cases EXCEPT sending DEGAS format pictures to our VAX.  Before I was
even aware of UNITERM, I purchased ANSIGRAPH; I have had no troubles
with its KERMIT at all.  So, while I use UNITERM as my standard, I
changed to ANSIGRAPH for any long binaries.  I have not
tried UNITERM 2.0e on a degas picture yet.

Steve Shawl
bitnet:  SHAWL@kuhub.cc.ukans.edu