Peter Rabbitson <[EMAIL PROTECTED]> wrote:
> > README.copy
> > README.verify
> >
> > You may save us a lot time when you read the documentation before sending
> > mail.
>
> Good point, however although this solves the problem (that I already solved
> by experimenting) it does not answer my fundamental question - why software
> that is used 95% of the time to burn iso images (since mostly used in
> conjunction with mkisofs) defaults to a writing mode that (as per the README
> you pointed me to) is guaranteed to produce inconsistent or even damaged
> CDRs.
Well, I did already send a view for the next time with cdrtools.
I cannot change the known standard behavior from cdrecord without introducing a
long long and well documented transition time.
J�rg
--
EMail:[EMAIL PROTECTED] (home) J�rg Schilling D-13353 Berlin
[EMAIL PROTECTED] (uni)
[EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/
URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
