Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!utgpu!water!watmath!clyde!burl!codas!killer!wnp From: wnp@killer.UUCP Newsgroups: comp.sys.ibm.pc Subject: Re: uudecode and downloading Message-ID: <2279@killer.UUCP> Date: Tue, 1-Dec-87 21:23:14 EST Article-I.D.: killer.2279 Posted: Tue Dec 1 21:23:14 1987 Date-Received: Sat, 5-Dec-87 08:41:21 EST References: <2808@sphinx.uchicago.edu> Reply-To: wnp@killer.UUCP (Wolf Paul) Organization: The Unix(tm) Connection BBS, Dallas, Tx Lines: 24 In article <2808@sphinx.uchicago.edu> z7m8@sphinx.uchicago.edu.UUCP (ari shlomo zymelman) writes: > >I have recently saved a bunch of uuencoded files off the network. >I then have extracted them using uudecode. This then leaves me >with a binary arc format file. I have then downloaded this file >using Kermit from the Pyramid (on which I access the network) to >my AT&T 6300 running DOS 2.11. When I go to dearc the files, >though, I get a CRC error. This has happened consistently over >at least three arc files sent in uuencode format. Any suggestions? > >-- Ari Zymelman Have you invoked kermit on the Pyramid with the 'i' flag? This is required for binary files (as opposed to textfiles). If you didn't, all instances of 0x0a (linefeed) got changed to the two- character sequence CR/LF, which throws arc. One quick way to check for that is to do a "ls -l" on the Pyramid, and compare the size of the archive there with the size of the archive on your 6300. If it is not exactly the same, then that might be the cause of your problem. Wolf Paul ihnp4!killer!dcs!wnp