On Sunday 23 July 2006 15:49, Anthony DiPierro wrote:
> On 7/23/06, Donald E Haselwood <dhaselwood@verizon.net> wrote:
> > While I wasn't too surprised by the errors in the cd burning, I would
> > have never dreamed that getting two corrupted downloads of the same file
> > was even remotely likely when everything else looked good,.
> >
> > Don
>
> That would surprise me too. What were you using to download? Did you
> have to resume the download at all?
No resumes. Everything seemed normal. I used Konqueror. I presume the file
transfer is ftp for the Suse SLED, definitely the case for the opensource
download.
> Presumably you downloaded from the same site all three times, right?
>
Same site each time. (When I got different md5sums for the 3 downloads I was
beginning to think that maybe there was a time stamp that made each download
different...grasping for explanations at the point!)
> I have run into problems with corrupted downloads while using the
> resume download feature of certain software (not sure which it was,
> though). Other than that, I too would assume this is very rare. TCP
> has its own reliability checksumming, after all.
Yes, I would have thought that the checks at each step would have caught any
problems. I downloaded to "machine A" and transfered it to "machine B" for
CD burning, so I checked the md5sums for the files on both machines and they
matched.
>
> Anthony
-----------------------------------------------------------------------
This list is provided as an unmoderated internet service by Networked
Knowledge Systems (NKS). Views and opinions expressed in messages
posted are those of the author and do not necessarily reflect the
official policy or position of NKS or any of its employees.
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 14:55:23 EDT