Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!okstate!uokmax!rmtodd
From: rmtodd@uokmax.UUCP (Richard Michael Todd)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Kermit and Procomm
Message-ID: <403@uokmax.UUCP>
Date: Wed, 17-Dec-86 17:25:21 EST
Article-I.D.: uokmax.403
Posted: Wed Dec 17 17:25:21 1986
Date-Received: Thu, 18-Dec-86 05:08:38 EST
References: <75800005@uiucdcsp>
Organization: University of Oklahoma, Norman, OK
Lines: 20
Summary: Maybe parity problem?

In article <75800005@uiucdcsp>, vanzandt@uiucdcsp.cs.uiuc.edu writes:
> 
> 
> 	Would someone please explain (in full detail) to me how to get
> Procomm 2.4 to do Kermit transfers. I can get Xmodem to work fine, I can
> get Kermit to Kermit to work fine, I just can't get Procomm to Kermit to
> work...
> 
One thing that might be fouling things up is confusion on parity.  Make sure
that whatever you have the byte length, parity type, etc. set to is the
same as what the UNIX Kermit thinks it is.  Typing "show" at the Unix Kermit
system prompt should show what everything's set at.  Use the "set" command
to change anything Kermit seems to have set incorrectly.  Then go on with
"RECEIVE", etc. and everything should work.  I use Procomm regularly to
up/download to UNIX, no problems.  I use a setting of 8-bit bytes, no parity,
so Kermit doesn't have to bother with 8th-bit quoting. Hope this helps. 
___________________________________________________________________________
Richard Todd
USSnail:820 Annie Court,Norman OK 73069
UUCP: {allegra!cbosgd|ihnp4}!okstate!uokmax!rmtodd