On Sun, Jun 7, 2009 at 11:11 AM, Mark Knecht<markknecht(a)gmail.com> wrote:
- FOLLOW-UP
<SNIP>
k3b seems to use:
/usr/bin/cdrecord -v gracetime=2 dev=/dev/hda speed=40 -raw96r
driveropts=burnfree -clone -eject /home/mark/backups/k3b_0.img
to build an image file for what that program calls a Clone. I then see this:
/usr/bin/readcd -v dev=/dev/hda f=/home/mark/backups/k3b_0.img -clone
retries=128 ts=128k
I suspect to write the CD-Rs that aren't working in my car.
<SNIP>
Obviously I have the two commands above backwards.
Clone read of CD:
readcd -v dev=/dev/hda f=/home/mark/backups/k3b_0.img -clone retries=128 ts=128k
The use of the readcd -clone option puts the whole disk info into a single file.
Clone write of CD:
cdrecord -v gracetime=2 dev=/dev/hda speed=40 -raw96r
driveropts=burnfree -clone -eject /home/mark/backups/k3b_0.img
The -raw96r option tells cdrecord it's reading a Clone type file.
According to the man page gracetime=2 is not allowed as it's below a
minimum of 3.
burnfree is write drive dependent.
- Mark