Path: utzoo!attcan!uunet!ginosko!gem.mps.ohio-state.edu!uwm.edu!cs.utexas.edu!swrinde!ucsd!ucbvax!agate!garnet.berkeley.edu!jwhite
From: jwhite@garnet.berkeley.edu (Jonathan White)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Procomm vs VAX
Message-ID: <1989Sep24.010701.17485@agate.berkeley.edu>
Date: 24 Sep 89 01:07:01 GMT
References: <42900050@uicsrd.csrd.uiuc.edu> <2517ADEA.28338@maccs.dcss.mcmaster.ca> <1611@tellab5.tellabs.CHI.IL.US> <676.251aa452@simpact.com>
Sender: usenet@agate.berkeley.edu (USENET Administrator;;;;ZU44)
Reply-To: jwhite@garnet.berkeley.edu (Jonathan White)
Organization: University of California, Berkeley
Lines: 30

In article <676.251aa452@simpact.com> jeh@simpact.com writes:
>In article <42900050@uicsrd.csrd.uiuc.edu> look@uicsrd.csrd.uiuc.edu writes:
>>I am trying to use Procomm v2.4.2 to down-load files from a VAX785 running
>>BSD 4.3 UNiX here to a XT. I am using Kermit on the VAX and attempting to use
>>the Kermit protocol in Procomm with no success. All I get are "exchanging 
>>parameters" and "packet resent" messages until I abort the attempt. I have 
>>[...]
>
>Hmmmm.  I haven't had insurmountable troubles with this, either using the 
>PgUp and PgDn keys OR using Server mode (Alt-K).  
>
>In each case where I have seen the messages you describe, parity has been the
>culprit.  Have you checked your parity settings?  I am not a Unix person by 
>any means, but most of the Unix systems I've talked to like to send and 
>receive in 7E1 format.  But they don't seem to CHECK the incoming parity, and 
>many comm. programs ignore the high bit anyway, so you can run interactively all
>day long with your PC set to 8N1 with no problem.  But Kermit cares, and must 
>be told that the host is using even (or whatever) parity.  
>


When I first started using Procomm to down load I had problems. It turned
out to be parity. 

From the Kermit prompt on the UNIX machine say 'set parity even' and then
the 'send' command. using pg dn on the redieving side.

This has fixed all my problems.

Jonathan