Xref: utzoo comp.sys.ibm.pc:15018 comp.unix.questions:6753
Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!bloom-beacon!mit-eddie!ll-xn!ames!umd5!vrdxhq!ms3!msicv01
From: msicv01@ms3.UUCP (Jay G. Heiser)
Newsgroups: comp.sys.ibm.pc,comp.unix.questions
Subject: Transferring binary files from VAX BSD 4.2 to MS-DOS
Summary: Xfer of binaries from BSD VAX to PC is easy -- set BOTH to binary
Keywords: kermit, binary, file transfer,
Message-ID: <786@ms3.UUCP>
Date: 27 Apr 88 21:11:47 GMT
Organization: Automation Management Consultants, Inc., Arl. VA
Lines: 27

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.  I've
successfully transferred a number of binary files (ftp'ed to our VAX host
from SIMTEL20) from BSD 4.2 to my PC.  We have an added problem because we
use a broadband LAN and the packet communication units have not been con-
figured for transparent operation.  Kermit is the ONLY way we have of
transferring binary files from our hosts to PCs.

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.  I'm using
MS-KERMIT 2.30 (Jan 88) and it works just fine w/o having to set a file type.
However, CrossTalk XVI & CrossTalk Mark IV will not transfer binary files
correctly unless you explicity set file type to binary.

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.

I strongly recommend Frank DeLaCruz's book "KERMIT: a file transfer protocol"
from DIGITAL Press.


Jay Heiser                   UUCP: ..!umd5!vrdxhq!ms3!msicv01
                             ARPA: msicv01@hios-pent.arpa
-- 
Jay Heiser                   UUCP: ..!umd5!vrdxhq!ms3!msicv01
                             ARPA: msicv01@hios-pent.arpa