21 Feb
2013
21 Feb
'13
6:11 a.m.
On 02/20/2013 01:16 AM, Ralf Mardorf wrote:
On Wed, 20 Feb 2013 08:38:19 +0100, david
<gnome(a)hawaii.rr.com> wrote:
A design decision. If simplicity is important to your target user, and
having verified CD burns is also important to them, you just make
verifying burns the default.
IIRC, verification is turned OFF by default in K3B. So a simple user
using it backup files might have the backups silently fail ...
K3B takes the power approach: You want the power, you got the power.
Here's hoping you know how to use it! ;-)
--
David
gnome(a)hawaii.rr.com
authenticity, honesty, community
http://clanjones.org/david/
http://dancing-treefrog.deviantart.com/
On 02/19/2013 10:05 AM, Ralf Mardorf wrote:
Ok, a hidden feature. I never noticed it. K3b then at least is clearer. 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-…
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).