Bug#265747: I think we've found the problem

[Garrett McLean]

This is in the changelog for a33 (the one that broke my drive). From 
ftp://ftp.berlios.de/pub/cdrecord/alpha/OLD/2.01aX/AN-2.01a33:

-	cdrecord now tries to check the DMA speed if the drive supports to read the
	drive buffer. If the DMA speed is not sufficient, then cdrecord requires 
	that burnfree is activated. If the environment variable "CDR_FORCESPEED"
	is set or -force has been specified, then cdrecord does not try to enforce
	that the available DMA speed is 2x the expected write speed.

So something about this is causing the breakage with our drives...hopefully a swift 
workaround is now somewhat in sight...

-Garrett

--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]