K3b has a bug where it sometimes fails to verify a newly written disk, even though it's a good burn.<br><br>The fix is in k3bchecksumpipe.cpp. The function K3bChecksumPipe.open needs to be changed as follows:<br><br>OLD VERSION: (body of K3bChecksumPipe.open):<br>
<br> if( K3bActivePipe::open( closeWhenDone ) ) {<br> d->reset();<br> d->checksumType = type;<br> return true;<br> }<br> else<br> return false;<br><br>NEW VERSION:<br><br> d->reset();<br> d->checksumType = type;<br>
return K3bActivePipe::open( closeWhenDone );<br><br>*************<br><br>I believe what was happening was that, during the write, the call on K3bActivePipe would start the disk read going before control was returned to the calling routine and the reset could be done. The result was that the checksum was getting reset AFTER it had already seen some of the data. This made the checksum from the write wrong, so the compare failed after the verify read. Experiments showed that it was the "write" checksum that was wrong, not the read/verify checksum.<br>
<br>Numerous tests show that this fix fixes the bug.<br><br>I hope you can make and distribute the change soon.<br><br>k3b is an excellent program and I'd be lost without it.<br>Thanks!!!<br><br>Yours,<br>Phil Petit<br>
<<a href="mailto:ppetit69@gmail.com">ppetit69@gmail.com</a>><br><br>