On 11/12/2010 06:24 PM, Thomas Schmitt wrote:
But first we have to see a successful run with RESERVE TRACK. It is unlikely that the successful cdrskin run used that command. I am not sure about the successful growisofs run. So the proposed experiment is essential for deciding this question: Is the sparse timeout to blame or is it the command generally ?
Is there anything you want me to do in order to figure out this? -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org Archive: http://lists.debian.org/4cde0803.9050...@realss.com
