20 Feb
2013
20 Feb
'13
8:38 a.m.
On 02/19/2013 10:05 AM, Ralf Mardorf wrote:
On Tue, 19 Feb 2013 14:48:43 +0100, Len Ovens
<len(a)ovenwerks.net> wrote:
Apparently Brasero verifies burns by default using the MD5 checksum. Its
CheckSum plugin can be set to use SHA1 or SHA256.
http://askubuntu.com/questions/54367/how-can-i-verify-data-after-burn-when-…
--
David
gnome(a)hawaii.rr.com
authenticity, honesty, community
http://clanjones.org/david/
http://dancing-treefrog.deviantart.com/
I have had problems with k3b as well (two bad
dvds before I gave up),
if I use brasero it's ok. I think brasero cd burning (from a toc file)
uses
cdrdao. gcdmaster is the tool I like best though.
My very old Suse 11.2 install or an older install of Suse that already
is removed can't burn one kind of DVD, + or -, but I experienced K3b as
the most usable burning tool, usually ok for Debian, Ubuntu and Arch
installs. Some days ago K3b and Brasero for FreeBSD were unable to
detect a CD RW. For other burning tools I'm missing functionality, such
as verifying (in the past sometimes an issue for K3b).