In the for what it's worth department, I had a burner (Acer) that produced disks where I was unable to read the md5sum using any combination of options. It always wrote run out sectors to the disk. Using readcd or dd and calculating the correct size, I could get them.
My CDR is an Acer. It worked alright with RH 7.3. I have never tried it through WinME. (Not There any longer)So I don't know how or if it even worked with the default software supplied.
These burned CDRs work for mediacheck and the MD5SUM come back OK, from both the reader and from the Acer CDR, that I still use. They just seem to not be portable. They are sort of customized CDRs for the native system.
The ACER model might have problems specific to it. But I don't think that it should be different enough to cause so much of a departure from usability.
If the other person, with similar problems also has an ACER CDR, I think that the vendor needs to put out an upgrade for the firmware. Throwing out a few hundred dollars is a bit extreme to solve a common problem.
Thanks for your experience and solution to the CDR problem. I hope it isn't the CDRW unit though.
Jim C.
I replaced the burner with a a Plex writter, and haven't had a problem since. I can get the md5sum with 'md5sum /dev/hdc'. With the older burner, this always resulted in IO errors.
- -- - -Michael
-- E = MC ** 2 +- 3db
