Hi, did you wait the time necessary to write a full gigabyte when -use-the-force-luke=dao was in effect ?
Why i ask: -use-the-force-luke=dao:96525 tells growisofs to use write type DAO rather than Incremental. Further it predicts the track size as 96525 blocks of 2048 bytes. The number has to match exactly the size of the input ISO image. I.e. show-musikprojekt.iso must have 197,683,200 bytes. Since you did not have to remove option -use-the-force-luke=tracksize:96525, i assume that ISO size and number do match. You already noticed a difference between DAO and Incremental at the start of a burn session. DAO knows the size of the track in advance and thus writes the table-of-content first. Incremental does not know how many blocks will be written and thus writes the table-of-content after the track was written. Another difference is that DAO results in a medium state that complies with the DVD-ROM standard ECMA-267. Its section 10.6 demands that the medium gets burned a ring of at least 70 millimeters. This is the width of a session of about 1 GB. So any DAO session lasts at least as long as a 1 GB session. If your drive does not end a DAO session after a due waiting time, then it is probably at the edge of failure. In this case you should be mistrusting towards its allegedly successful runs. Do checkread. Have a nice day :) Thomas -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1356528 Title: k3b dvd burning crashes with growisofs and -use-the-force-luke=dao: option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/k3b/+bug/1356528/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
