Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!usc!wuarchive!sdd.hp.com!hplabs!pyramid!athertn!steveh
From: steveh@athertn.Atherton.COM (Steve Harding)
Newsgroups: comp.binaries.ibm.pc.d
Subject: Re: Problem retrieving archive programs via FTP
Keywords: archive FTP Kermit
Message-ID: <34469@gumbo.athertn.Atherton.COM>
Date: 15 Feb 91 21:30:56 GMT
References: <1991Feb13.042158.25755@csuvax1.csu.murdoch.edu.au> <1991Feb13.152910.16132@linus.mitre.org> <460@adphdw20.UUCP>
Reply-To: steveh@Atherton.COM (Steve Harding)
Distribution: usa
Organization: Atherton Technology, Sunnyvale, CA
Lines: 34

In article <460@adphdw20.UUCP> dtb@adpplz.UUCP (Tom Beach) writes:
>In article <1991Feb13.152910.16132@linus.mitre.org>, dhf@linus.mitre.org (David H. Friedman) writes:
>> 
>>    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
>... stuff deleted
>
>My PC is connected to our local UNIX server over PC/NFS ethernet link.
>This setup allows me to access files on the UNIX system either by doing
>a remote login to the workstation or accessing directly through NFS
>from the PC. I have found that when I UUDECODE the files with the PC
>they will not unzoo because of extraneous LFs evidently either appended
>by my UUDECODE or DOS itself. If I run UUDECODE from UNIX, switch back
>to the PC to run looz212 it works as expected. The point is it may
>not be kermit that's introducing the extraneous linefeeds.
>
>Tom:  dtb@adpplz.uucp

As I recall (not having used PC/NFS for sometime) there is a couple of
utilities included ... UNIX2DOS and DOS2UNIX that converts the CR/LFs
from one system to the other.  Unfortunately, these are not standalone.
The PC/NFS server must be running.

Based on the above, it would appear that there IS a difference twixt UNIX
and DOS files and how the CRs are handled.  As a test, upload a text file
from your DOS box to UNIX, then view the file on the UNIX side; you will
see a ^M appended to the end of each line.

SRH