Path: utzoo!attcan!uunet!ncrlnk!ncr-sd!crash!simpact!jeh
From: jeh@simpact.com
Newsgroups: comp.sys.ibm.pc
Subject: Re: Procomm vs VAX
Message-ID: <676.251aa452@simpact.com>
Date: 23 Sep 89 04:29:53 GMT
References: <42900050@uicsrd.csrd.uiuc.edu> <2517ADEA.28338@maccs.dcss.mcmaster.ca> <1611@tellab5.tellabs.CHI.IL.US>
Organization: Simpact Associates, San Diego CA
Lines: 22

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.  

	--- Jamie Hanrahan, Simpact Associates, San Diego CA
Chair, VMSnet [DECUS uucp] and Internals Working Groups, DECUS VAX Systems SIG 
Internet:  jeh@simpact.com, or if that fails, jeh@crash.cts.com
Uucp:  ...{crash,scubed,decwrl}!simpact!jeh