Path: utzoo!utgpu!water!watmath!clyde!bellcore!rutgers!mailrus!uflorida!gatech!gitpyr!joel
From: joel@pyr.gatech.EDU (Joel Rives)
Newsgroups: comp.windows.x
Subject: Re: Dated announcement (`pex.tar.Z' on expo)
Keywords: Corrupted File Transfer
Message-ID: <6542@pyr.gatech.EDU>
Date: 11 Oct 88 15:31:46 GMT
References: <8810110820.AA16936@mahendo.Jpl.Nasa.Gov>
Reply-To: joel@pyr.UUCP (Joel Rives)
Organization: Office of Computing Services, Georgia Tech
Lines: 28


I, too,  have experienced problems with getting compressed binaries across 
the Internet before. Occasionally, i have found it necissary to 
transfer the file two or more times before an acceptable local copy
is made. Please, no suggestions that i may have forgotten to set the
type to binary. I'm not a novice at this. The occurances have been rare
enough that i have not been that concerned. Nor do i have the time or
interest in tracking down the source of this anomaly. I was quite willing 
assume that it might have been a problem with my local host. However, if 
others are experiencing the same sort of occasional failures ... well....

In any case, the only other piece to the puzzle that i have to offer is that
the failures i have experienced have been with a particular file and not
spread across a number of files which may have been transferred during
a singel ftp session. For example, i logged into a remote host using ftp
and transferred several compressed tar files. Afterwards, i uncompressed
them and untarred them. One of the files was corrupt. So, i went back to
the host and got that one file again. It was corrupt again. A third or
fourth try produced a viable copy of the original. 

joel


-- 
		The thief
		  Left it behind--
		    The moon at the window.
						-Ryokan