The point here is that, for multiple people, using an older version of
cdrecord gets rid of the problem. This means, if I am not mistaken, that
some code was written that breaks cdrecord for some writers (for me,
this code was introduced in cdrtools 2.01 (2.00.3 works without a hitch
for me)). Doesn't that mean that there's something wrong with that code?
Keep in mind, in my case at least, I changed absolutely nothing but the
version of cdrtools/cdrecord used. I was always using kernel 2.6.10 and
I always passed dev=/dev/hdc to cdrecord. So, the only variable is the
version of cdrtools used. Therefore, the bug has to be in
cdr{tools|record}. I SO wish I knew enough C to figure out which part of
2.01 breaks it for me, but I don't. So I email this bug until things get
fixed.
-Garrett
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]