-------------- Original message ----------------------
Yes, it had finished two days ago and I was finally burning the individual disks to do an upgrade on a CD-Drive only system. I burn and then I check the md5sums.
Why not check the iso's against the SL-10.1/iso/MD5SUMS file *first*, to be sure you've got uncorrupted files?
Thank you for this obvious thing, which I overlooked. :( The files have good md5sums. I'm not sure about the copies, but I reburned the disks with k3b and they check out good now. I started copying them to different partitions due to the fact I dl'ed them to my fat32 partition which had the room, but wouldn't allow me to make the DVD from the makeSUSEdvd script, as it created lower case directories but tried to write to upper case directories. Definitely time for a larger /home drive.
Of course you can check the md5sum from the burned iso too, after burning. But by /assuming/ you've got uncorrupted files (instead of verifying them) you can't be sure if the downloading went wrong or the burning went wrong. ;)
Cheers,
I burned a disk the other day, under K3B and it came out bad, I hadn't waited for it to calculate the md5 sum. The next try (same batch of disks) I burned after it had calculated the md5 sum. Is the calculation required for a sucessfull burning (checks while burning). I knew the iso was good, just needed another hand out copy. Thanks