Hi,
Sorry if this has already been covered; but I didn't find it in the
expert/cooker archives.
Thinking I'd just created a couple of coasters, I was surprised to see that each
CD's md5sum, while not matching those in the "md5sums" file, were consistent
between "coasters"...
Investigation showed that xcdroast adds some "pad data"... here's the relavent
output from CD1:
Track 01: writing 30 KB of pad data.
Track 01: Total bytes read/written: 679673856/679704576 (331887 sectors).
expected size of CD ^^^^^^^^^
actual size of CD ^^^^^^^^^
The extra padding causes a different md5sum. I've tried:
dd if=/dev/cdrom bs=679673856 | md5sum # start of CD
tail -c 679673856 /dev/cdrom | md5sum # end of CD
but these md5sums don't match the official "md5sums" file... I'm quite certain
that both copies of CD1 are correct, especially given that they give the same
md5sum and that xcdroast reports padding...
This is the first time I've ever encountered xcdroast padding ISO images... has
anyone else run into this...?
I'm continuing to burn the other CDs; and will report the results when I'm done.
Cheers,
Pierre
Want to buy your Pack or Services from MandrakeSoft?
Go to http://www.mandrakestore.com
