Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!tj
From: tj@utgpu.UUCP
Newsgroups: comp.sys.ibm.pc
Subject: Re: Kermit and Procomm
Message-ID: <1987Jun24.235923.4691@gpu.utcs.toronto.edu>
Date: Wed, 24-Jun-87 23:59:23 EDT
Article-I.D.: gpu.1987Jun24.235923.4691
Posted: Wed Jun 24 23:59:23 1987
Date-Received: Fri, 26-Jun-87 02:04:35 EDT
References: <12809@topaz.rutgers.edu>
Reply-To: tj@gpu.utcs.UUCP (tj)
Organization: University of Toronto Computing Services
Lines: 17
Checksum: 16473

This is a real simple one... It is a bug in PROCOMM Kermit as far as I can
tell. You are running with no parity (otherwise the problem doesn't show 
up from my experience) and so Procomm thinks that there is no need to
do anything with the 8th bit quote character and they get stored in the
file you receive. Debug it and you will see it littered with the quote 
character around where an 8 bit value should have been. Now I admit that
when running with no parity it should be possible to send all values
without 8th bit quoting, but if 8th bit quoting is on then PROCOMM should
handle it. If I set Unix Kermit to no parity and receive a binary with
procomm at no parity it expands (and therefore fails) but if i set Unix kermit
to even parity and receive with procomm at even parity then the binary gets
transfered properly. From our local BBS I have to use Xmodem since it is
fixed at no parity and Kermit fails for binaries!!!

As an aside we have our own licensed version of Procomm and have been having
troubles getting through to them to get bugs fixed. We got a "special" bbs
number. It takes 3-8 hours of repeated dialing to get through.