Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 30 Jul 2005 12:05:42 +0200
From:      Fabian Keil <freebsd-listen@fabiankeil.de>
To:        garys@opusnet.com (Gary W. Swearingen)
Cc:        Brian Henning <brian.henning@gmail.com>, freebsd-questions@freebsd.org
Subject:   Re: burncd - verify burn
Message-ID:  <20050730120542.7f0008bb@localhost>
In-Reply-To: <jek6je23d2.6je@mail.opusnet.com>
References:  <1f75ab0e05072510117c119a1d@mail.gmail.com> <jek6je23d2.6je@mail.opusnet.com>

next in thread | previous in thread | raw e-mail | index | archive | help
--Signature_Sat__30_Jul_2005_12_05_42_+0200_H+ciiWPerBl_=4vh
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

garys@opusnet.com (Gary W. Swearingen) wrote:

> Brian Henning <brian.henning@gmail.com> writes:
>=20
> > I would like to know a process to verify that I my cd burner has
> > burned an ISO file correctly with burncd. I know I can take some
> > precautions like checking the md5sum of the iso during a transfer from
> > the Internet. I also read on the Internet that burncd does puts some
> > extra padding at the end of the cd. I am not sure if that is true or
> > not. Could someone tell me how to verify a cd burn?
>=20
> Here's a crummy script I just used to burn and verify a CD, but I've
> only tested it with the "cdrecord" setup.  Older versions of it worked
> with "burncd" on older OS versions, but I can tell you that the reason
> I'm using "cdrecord" is that my manual efforts to do this with
> "burncd" on 5.4-RELEASE (and maybe 5.4-STABLE a couple weeks ago)
> failed, because I couldn't "dd" a CD burned with "burncd". (IE, I
> couldn't sucessfully "dd" /dev/acd0, while I could "dd" /dev/cd0).
>=20
> (Search this for "diff" to find the "verify".  ISO images generally
> get an extra two blocks of something on the CD "for run-out". See
> "-isosize" description of "cdrecord" manpage.)

Not generally, only if you burn in TAO mode.

BTW you can use readcd -c2scan to check the burning quality at
a deeper level and there even is a patch out there to make reading
c1 error pointers possible. Haven't tested it though.=20

Fabian
--=20
http://www.fabiankeil.de/

--Signature_Sat__30_Jul_2005_12_05_42_+0200_H+ciiWPerBl_=4vh
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (FreeBSD)

iD8DBQFC61D2oomUOj0wp30RAjdCAKCKB7Bk+WM6igCX3+dLXCGBnhLp+ACfRYIj
WdJHRsvidPLtZyS2fkMbY8o=
=eny4
-----END PGP SIGNATURE-----

--Signature_Sat__30_Jul_2005_12_05_42_+0200_H+ciiWPerBl_=4vh--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050730120542.7f0008bb>