Version: (using KDE KDE 3.2.0) Sometimes I forget to check verify written data before burning. K3B could need a function to verify a burned disk afterwards.
this whould be really nice. I vote for it.
I also like this idea
While we're at proposing improvements for verifying I suggest speeding it up somehow. Here k3b takes ~25 mins to verify a disk while diffing the files takes ~3.5 mins...
k3b computes a md5sum for both files, then compares them. md5sum is quite slow, indeed diffing might be faster...
*** This bug has been confirmed by popular vote. ***
*** Bug 103490 has been marked as a duplicate of this bug. ***
*** Bug 116427 has been marked as a duplicate of this bug. ***
Just to clarify, you want a redo of the md5 sums later on, as opposed to some quick way on inserting a cd and checking if this is the cd that was burned from this project (This is different, because the file content might have changed in the meantime and no md5 can be calculated)
Ideally it would display the different files as requested in Bug 77310: verification: mark different files in the project view
If that is the ideal solution, is it ok to close this one as a duplicate of bug 77310?
no this bug is about verifying after burning, bug 77310 is about how to display the result of verification in general
*** Bug 162689 has been marked as a duplicate of this bug. ***