MD5 calculation problem

[guest]

I downloaded FreeBSD release 6 from their servers onto my Windows XP sp2
(fully patched) machine. I used Firefox 2.0.0.1 for this job. There are 3 iso's in the download:
6.2-RELEASE-i386-disc1.iso
6.2-RELEASE-i386-disc2.iso
6.2-RELEASE-i386-docs.iso

Here is where I went to get them:

ftp://ftp1.freebsd.org/pub/FreeBSD/

When I checked the MD5's I got a result that agreed to the FreeBSD provided numbers for disc2.iso and docs.iso. For disc1.iso I got a different MD5 which caused me to send a bug report to FreeBSD. The FreeBSD people have investigated and are satisfied that their provided MD5 is in fact correct.

Therefore, I downloaded the disc1.iso again, this time from a different server. I got exactly the same MD5 *again* for this iso, which is claimed by the FreeBSD people to be wrong. Curious that Salamander's plugin gets the "correct" md5 for disc2 and docs but consistently gets the wrong one for disc1.

John Watts
Edmonton, Canada

For some reason, I was unable to do the ftp transfer using the Salamander ftp plugin - I am not a whiz at using ftp though. I just used Firefox instead rather than try to figure it out.

[guest]

Sorry, I forgot to post the md5s for disc1.iso

MD5 (6.2-RELEASE-i386-disc1.iso) = 3d27214700687c0b5390e8b6dd3706e3
As calculated by SS plugin CBBD52B257FB1FDE3E22A13CC8EAAE85

Salamander plugin gets the same md5 for disc1.iso, downloaded from different servers.

John Watts
Edmonton, Canada

[guest]

Please hold off on looking into this problem. I think I made an error in reporting *which server* I had downloaded the problem iso file from when I reported it to FreeBSD, which misled them a bit. Now I think they have the problem fixed though.

I verified that a linux system was able to duplicate the same md5 result as I got using salamander md5 plugin, so there was no problem with the calculation done by salamander.

Apologies.

John Watts
Edmonton, Canada