Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ncar!tank!eecae!cps3xx!gcook
From: gcook@cps3xx.UUCP (Greg Cook)
Newsgroups: comp.sys.ibm.pc
Subject: Re: using Procomm's Kermit file xfer
Message-ID: <5594@cps3xx.UUCP>
Date: 30 Nov 89 04:16:57 GMT
References: <1778@bucket.UUCP>
Sender: usenet@cps3xx.UUCP
Distribution: usa
Lines: 25

From article <1778@bucket.UUCP>, by leonard@bucket.UUCP (Leonard Erickson):
> scottb@ogccse.ogc.edu (Scott Baker) writes:
> Procomm's implementation of Kermit will *only* work if you are running
> 8-N-1. You'll have to start the send or receive on the Vax, and then use
> Alt-P to switch to 8-n-1 and *then* start the upload or download. After
> the xfer, use Alt-p to switch bach to your old parameters.

Not True!

I use procomm's kermit transfers with "E71" routinely and have had
no problems.  Actually, it would not work with "N71" but changing
parity to "E" solved the problem for me.

Maybe the "8th bit quote char" parameter in procomm has something to
do with this.  But I don't really know.  All that matters to me is
that what I am doing works.


Is anyone familiar enough with procomm/kermit to enlighten us as to
why there are different successes with different parities/bits etc?

=========================================================================
Greg Cook                             Chemistry IS life! 
gcook@horus.cem.msu.edu        Watch for the next generation of Enamines 
cook@frith.egr.msu.edu             coming to a Journal near you!