Xref: utzoo comp.binaries.ibm.pc.d:2409 comp.sys.ibm.pc:26453
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!bloom-beacon!gatech!jkg
From: jkg@gatech.edu (Jim Greenlee)
Newsgroups: comp.binaries.ibm.pc.d,comp.sys.ibm.pc
Subject: PROCOMM <-> C-Kermit problems (was: Problems with DSZ - Zmodem)
Keywords: file transfer, protocol, lockup
Message-ID: <18222@gatech.edu>
Date: 23 Mar 89 14:33:23 GMT
References: <447@holin.ATT.COM>
Reply-To: jkg@gatech.UUCP (Jim Greenlee)
Followup-To: comp.sys.ibm.pc
Organization: Georgia Institute of Technology
Lines: 24

[ This article and follow-ups are re-directed to comp.sys.ibm.pc. I hope 
  nobody over there minds. - jkg ]

In article <447@holin.ATT.COM> doc@holin.ATT.COM (David Mundhenk) writes:
>On that same note, does anyone know why PROCOMM's kermit would have
>problems talking to C-Kermit on the 3B's mentioned above? The parameters
>all seem to be set OK....again, either direct or thru a modem.

Well, I pretty much gave up on Procomm after 1000-byte packets were added 
to Kermit. This is a common problem, though (my students have asked this 
question so many times that I now include the answer in the write-up for 
my courses! :-). 

Unfortunately, I don't have the exact details handy, so this will be from 
memory. What you have to do is change the checksum parameter in the Kermit 
set-up menu. I think the default of "1-byte" checksum must be changed to 
"2-byte" checksum. It may be the other way around, though.

						Jim Greenlee
-- 
Jim Greenlee - Instructor, School of ICS, Georgia Tech     jkg@gatech.edu

Jryy, abj lbh'ir tbar naq qbar vg! Whfg unq gb xrrc svqqyvat jvgu vg
hagvy lbh oebxr vg, qvqa'g lbh?!