Path: utzoo!attcan!uunet!lll-winken!ames!mailrus!sharkey!atanasoff!deimos!eecea!terry
From: terry@eecea.eece.ksu.edu (Terry Hull)
Newsgroups: comp.unix.questions
Subject: Re: File transfers
Keywords: kermit hex codes ms-dos
Message-ID: <543@eecea.eece.ksu.edu>
Date: 26 Jan 89 17:55:11 GMT
References: <8458@dasys1.UUCP>
Reply-To: terry@eecea.eece.ksu.edu (Terry Hull)
Followup-To: comp.unix.questions
Organization: Kansas State University, Manhattan
Lines: 17

In article <8458@dasys1.UUCP> duster@dasys1.UUCP (Harry Milkman) 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?

Yes, you are transferring the file in text mode.  Ckermit on the 3B2
assumes that you want to make the text file UNIX compatible, so it
strips the <cr>.  If you want to keep the <cr>s, use binary mode.
Then ckermit will leave the file contents alone and will not try to 
"fix" it.  

-- 
Terry Hull                    Department of Electrical and Computer Engineering
                                           Kansas State University
INTERNET: terry@eecea.eece.ksu.edu          Manhattan, KS  66502 
UUCP: rutgers!ksuvax1!eecea!terry