[comp.sys.amiga] Is this a known kermit bug?

chris@a.cs.okstate.edu (Chris Schuermann) (06/21/88)

And speaking of kermit...
I believe I have run into a bug in the kermit protocol.
This bug manifests itself when transfering 'ARCed' files.
For those who don't use micros, this is a method to compress one or
several files into and 'archive'.  The archive software uses several
different methods of compression depending on what the data looks like.
Anyway, obviously these archives contain binary data.  I have been using
kermit (binary mode of course) to transfer these archives. 
Now here is the problem:  About one file in twenty kermit corrupts!
I have tried using several different versions of kermit on several
different machines and have seen the same results. I am using an
Amiga 1000 computer.  I have tried the 'official' kermit release,and
several PD software packages with kermit.  I have talked to several
different brands of micros running several defferent versions of kermit.
Also several larger systems including VAXEN and Perkin Elmer machines.

Has anyone else seen this problem?  Is there a string in the archives
that is fooling the kermit protocol?  I just don't understand what is
happening...  As of late I have started using XMODEM-CRC whenever kermit
trashes a file and it will xfer it just fine....


Chris Schuermann
Oklahoma State Univ. Electronics Research and Development Laboratory
Department of Electronics and Computer Technology 
Department of Computing and Information Sciences
Oklahoma State University

UUCP:  {cbosgd, ea, ihnp4, isucs1, mcvax, pesnta, uokvax}!okstate!chris

Internet:       chris@a.cs.okstate.edu

acs@amdahl.uts.amdahl.com (Tony Sumrall) (06/22/88)

In article <3627@okstate.UUCP> chris@a.cs.okstate.edu (Chris Schuermann)
writes of a problem that he's been having with a number of kermit
implementations.  The problem manifests when trying to transfer a binary
file (in his (her?) case it was ARCed files).  There is a problem in
earlier releases of C-Kermit (at least) where a binary transfer would
occasionally go awry.  Check the okstate kermit archives for more info.
(Sorry, I don't have it).  BTW, I've never seen this problem myself
even when I used the C-Kermit modules that supposedly had the problem.

>Chris Schuermann
>Oklahoma State Univ. Electronics Research and Development Laboratory
>Department of Electronics and Computer Technology 
>Department of Computing and Information Sciences
>Oklahoma State University
>
>UUCP:  {cbosgd, ea, ihnp4, isucs1, mcvax, pesnta, uokvax}!okstate!chris
>
>Internet:       chris@a.cs.okstate.edu


-- 
Tony Sumrall acs@amdahl.uts.amdahl.com <=> amdahl!acs

[ Opinions expressed herein are the author's and should not be construed
  to reflect the views of Amdahl Corp. ]