Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!usc!samsung!think.com!linus!linus!linus!dhf
From: dhf@linus.mitre.org (David H. Friedman)
Newsgroups: comp.binaries.ibm.pc.d
Subject: Re: Problem retrieving archive programs via FTP
Keywords: archive FTP Kermit
Message-ID: <1991Feb13.152910.16132@linus.mitre.org>
Date: 13 Feb 91 15:29:10 GMT
References: <1991Feb13.042158.25755@csuvax1.csu.murdoch.edu.au>
Sender: dhf@linus.mitre.org (David H. Friedman)
Distribution: usa
Organization: The MITRE Corporation, Bedford, MA 01730
Lines: 14
Nntp-Posting-Host: linus.mitre.org


   I was doing essentially the same thing, ftp'ing files from wustl and
kermit'ing to a PC for copy to a diskette. In my case, .ZIP files wouldn't
unZIP properly on the PC. I finally compared hex dumps on the PC and on my
UNIX box, and found that the Kermit-to-Kermit transfer was introducing extra
characters - it looked like every 0Ah was being changed to 0Dh 0Ah, i.e.,
every CR was being changed to LF-CR even though the transfer mode was
supposedly BINARY! I couldn't find which Kermit parameter, if any, enabled
or disabled this translation. (I was using MS-Kermit 2.31 on the PC.) The
fix I had to use is to UUENCODE the files on the UNIX box, Kermit them to
the PC, and UUDECODE them back to binary. If you need UUDECODE for the PC,
it's in the starter kit that's periodically posted to comp.binaries.ibm.pc.

dhf@linus.mitre.org