On 27/08/2010 00:03, Carlos E. R. wrote:
On 2010-08-26 14:38, Basil Chupin wrote:
On 26/08/2010 19:17, DenverD wrote:
i'm pretty sure the answer to his problems is to fetch a full and correct image...
I've seen such responses before - and they puzzle me.
Since the 1980s we have had download protocols which use CRC to ensure that the file being transmitted is received correctly. So what has happened to this feature?
Yes, but it appears that http/ftp don't have that feature.
Instead, people could use the metalink "link" to make the download with a good metalink downloader, because that protocol _can_ guarantee a correct download, correcting errors. I use aria2c.
Caveat: it requires that the metalink metadata contains error correction blocks. The DVD links at suse do. The system works by redownloading a bad block, and the dvd link has 129 such blocks of ~33 MB.
Once a download is bad, probably rsync is more efficient at correcting it. Do we have this info easily found in the wiki, near the download page?
A torrent downloader can also correct it.
Incredible....We are in this situation after some close to 30 years of having error-correcting protocols.....Unbelievable :-( . I use a Firefox Extension called DownThemAll! which has never given me a bad CD or DVD - and it resumes from where I lost the connection (which never happens now :-) .) I also find that the downloader in Firefox now also resumes from where the connection was lost and it also produces a "clean" file - but this latter downloader has not been under any "real strain" since it was upgraded by Mozilla. The reference to DownThemAll! is shown in this Wikipedia link: http://en.wikipedia.org/wiki/Download_manager BC -- Gumperson's Law: The probability of anything happening is in inverse proportion to its desirability. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org