Xref: utzoo comp.sys.ibm.pc:15146 comp.unix.questions:6806
Path: utzoo!mnetor!uunet!husc6!bloom-beacon!gatech!uflorida!novavax!maddoxt
From: maddoxt@novavax.UUCP (Thomas Maddox)
Newsgroups: comp.sys.ibm.pc,comp.unix.questions
Subject: Re: Transferring binary files from VAX BSD 4.2 to MS-DOS
Message-ID: <459@novavax.UUCP>
Date: 1 May 88 21:36:31 GMT
References: <786@ms3.UUCP>
Reply-To: maddoxt@novavax.UUCP (Thomas Maddox)
Organization: Nova University, Fort Lauderdale, Florida
Lines: 24
Keywords: kermit, binary, file transfer, Procomm
Summary: It works

In article <786@ms3.UUCP> msicv01@ms3.UUCP (Jay G. Heiser) writes:
>I've seen several postings lately in response to someone who is having
>difficulty transferring files from a VAX using unix to an MS-DOS PC. 
> [ . . . ] 
>No one mentioned setting file type to binary on both the PC and the remote
>host.  You MUST do it on the remote host, or every ^J will be turned into a
>^M^J combo.  I believe the -i flag does the exact same thing. 
> [ . . . ] 
>Also, parity will screw things up too, if you happen to have anything along
>the line set to 7 bits.  Our IBM host only works with kermit with space parity.

	For those who followed the earlier discussion concerning
transmission difficulties involving Unix/kermit at the Vax end,
Procomm/kermit at the other, there appears to be a definitive
solution.  If for some reason you must stay in Procomm (for instance,
you don't have an external kermit package), then you use kermit si
[filename] at the Unix end, then from Procomm change from E71 to N81,
using alt-p, and the file will be received fine (afterwards, of course, 
you must change back to E71, or your screen will contain only gibberish).
Alternatively, you can shell out of Procomm with alt-F4 and run kermit
as an external protocol. 
	Apologies for repeating this information if you already know
it, but I know from experience how frustrating this little problem can
be.