And so you should. You are correct. The problem seems to occur most when it goes like this > DL ISO>Burn ISO as a bootable CD> Rip (copy) CD to ISO Image and then ck md5sum.

I am not sure but it is indeed one of those things that cannot be anticipated. I copied that section of the comment from someone much more knowlegeable than I in our local LUG.

I usually have few problems myself but people I know have problems mostly on older CDRom drives/burners.

Regards,

Jason

PS, get a Windows md5sum checker here:
http://etree.org/software/md5sum.exe

I believe...

Guy Rouillier wrote:
Jason Greenwood wrote:

The implementation of the isofs in
Linux is quite bad (e.g. the method of making inodes will prevent
hardlinked files from ever being stored properly on an isofs). The
kernel also has the habit (ever since the first version) of reading too
much data from the device, i.e. it reads past end of file on the disk.


Jason, just curious, is this only a create issue. I downloaded and created the Mandrake 9.0 CDs in Windows 2000 using Adaptec CD Creator. After installing Mandrake, I ran md5sum against the downloaded ISO images (shared FAT32 partition) and the CD (using the dd method) and got exacly the same number on both. I also ran md5sum against the 3 RedHat 8.0 CDs using the dd method and again got the correct results.




------------------------------------------------------------------------


Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com


Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com

Reply via email to