Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!usc!elroy.jpl.nasa.gov!swrinde!zaphod.mps.ohio-state.edu!think.com!linus!linus!tatum!dhf From: dhf@tatum.mitre.org (David H. Friedman) Newsgroups: comp.windows.ms Subject: Re: Unable to unzip files from CICA??? Message-ID: <1991Mar6.184200.771@linus.mitre.org> Date: 6 Mar 91 18:42:00 GMT References: <21774@yunexus.YorkU.CA> <27208@uflorida.cis.ufl.EDU> <4410@cernvax.cern.ch> Sender: dhf@linus.mitre.org (David H. Friedman) Distribution: usa Organization: The MITRE Corporation, Bedford, MA 01730 Lines: 32 Nntp-Posting-Host: tatum.mitre.org . Judging from the number of times the topic has come up lately, this particular "gotcha" must be claiming about one victim per week (I was one of them), and maybe the FTP sites could consider sending out a reminder message to everyone doing an anonymous login (sort of like putting up a "dangerous intersection" sign at a bad corner). There are basically two things to do: 1) at the ftp> prompt, before getting a file, give the command binary to be sure the ftp processor knows that's what you want. 2) when downloading from the Unix box to the PC, before putting the Unix Kermit into server mode, give it the command set file type binary or it'll convert CR codes to LF-CR's. Some sanity checks: 1) Compare the file size in bytes as reported by the ftp "get" command with the size in your Unix directory - should be the same. For good measure, do a "ls" at the ftp> prompt first, to get the size of the actual file at the ftp site. 2) Compare the above file size with the size in the local PC directory - should also be the same, possibly different by 1 byte (I'm not sure where this happens, but sometimes it seems to be rounded up or down to an even number). If all else fails, you can uuencode the file on your Unix box, then uudecode it on the PC. If anyone has any comments, additions, etc. (no flames, please), I'd be thankful for further enlightenment on the topic. dhf@linus.mitre.org