roberts
Group: Members
Posts: 4983
Joined: Oct. 2003 |
 |
Posted: April 14 2005,17:04 |
 |
Joel & Chris,
After you get the checksum alert screen, open up an xterm and cd to /tmp or where ever you specified for the download files. Since I do not delete aborted downloads, you should see in that directory both the md5 and the extension.
Now manually do a checksum on the suspect extension, i.e.,
md5sum -c jre1_5_0.tar.gz.md5.txt
Downloading via other means won't tell me much, as the most variable of all is the latency of the internet. Unless a reproducible error can be produced, there is not much I can do. I have yet to get a checkcum error on any file that I have downloaded. In fact, I had to make a BAD md5 file on my webserver just to verify that the code would produce the checksum alert.
Also, Chris, if it works on some extensions and not others that would then not point to the code. The code is not variable, the extensions and conditions of the network and the internet are.
Checksuming was one of the most requested features as users were loading corrupted extensions caused by bad downloads. For liveCD just reboot but for hard drive installs it was causing much grief.
But please let me know the results for the manual checksum check.
|
.
DSL Market ,
Great VPS hosting provided by Tektonic
