Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!nrl-cmf!ukma!rutgers!att!petsd!pedsga!tsdiag!scr1!billp
From: billp@scr1.UUCP
Newsgroups: comp.unix.questions
Subject: Re: File transfers
Summary: Kermit Text mode
Keywords: kermit hex codes ms-dos
Message-ID: <285@scr1.UUCP>
Date: 28 Jan 89 04:21:43 GMT
References: <8458@dasys1.UUCP>
Organization: CONCURRENT,OCEANPORT, NJ
Lines: 25

In article <8458@dasys1.UUCP>, duster@dasys1.UUCP writes:
> After transferring a file from an MS-DOS PC to a 3B2 running UNIX, using
> kermit, the <cr> character (hex 0D) is stripped from my file.
> 
> Does anyone have any idea why this happens?

Kermit transforms textfiles into the correct text format for the receiving
system if it is told the file is a textfile.

If you want to move a non-text file between a Unix box and an MS-DOS machine
you must tell the Unix side the file is BINARY.  Otherwise Kermit will change
the Unix newline (linefeed) to carriage return/linefeed going to DOS and strip
the CR going to Unix.  Unix sees dos' cr/lf pair as a ^M followed by newline
which is incorrect for Unix.

Kermit will also translate on other os's including Unix, OS/32 and ascii<-->
ebcdic on IBM.

Hope this helps explain why this happens.

-- 
Bill Pechter -- Home - 103 Governors Road, Lakewood, NJ 08701 (201)370-0709
Work -- Concurrent Computer Corp., 2 Crescent Pl, MS 172, Oceanport,NJ 07757 
Phone -- (201)870-4780    Play/ .. rutgers!pedsga!tsdiag!scr1!billp
"Why do they call it software when the manual's so hard to understand?"