diff options
Diffstat (limited to 'doc/wodim')
| -rw-r--r-- | doc/wodim/README.DiskT@2 | 67 | ||||
| -rw-r--r-- | doc/wodim/README.WORM | 10 | ||||
| -rw-r--r-- | doc/wodim/README.cdrw | 17 | ||||
| -rw-r--r-- | doc/wodim/README.clone | 27 | ||||
| -rw-r--r-- | doc/wodim/README.raw | 71 |
5 files changed, 192 insertions, 0 deletions
diff --git a/doc/wodim/README.DiskT@2 b/doc/wodim/README.DiskT@2 new file mode 100644 index 0000000..f94e124 --- /dev/null +++ b/doc/wodim/README.DiskT@2 @@ -0,0 +1,67 @@ +New driveropts= option "tattoofile=". Use together with -checkdrive +to write an image of the right size to disk. + + DiskT@2 hints: + + In order to have "DISKTATTOO" listed in the "Driver flags", + the disk currently inserted must be usable for the DiskT@2 feature. + This means that there needs to be enough space on it. + + You need an B&W image with 3744 pixels per line + + Best start with a 3744 x 320 pixel image. + The correct size may be retrieved with + wodim driveropts=tattooinfo -checkdrive + + To get RAW image data: + + - Take 'xv' and save the image in PBM/PGM/PPM (raw) mode + + - use a binary aware (must support unlimited linelength) + editor such as 'ved' and remove the header lines. + These lines look like: + + P5 + # CREATOR: XV Version 3.10a Rev: 12/29/94 (PNG patch 1.2) + # CREATOR: XV Version 3.10a Rev: 12/29/94 (PNG patch 1.2) + 3744 144 + 255 + + Now you should have (in case of the file above) a file that + has exactly 539136 Bytes. + + - Note that the tattoo image must be left to right flipped + (a mirror image). + +From a hint from "E. Robert Bogusta" <rob23@tmr.com>: + +Take an image, and do: + + djpeg myface.jpg | ppmtopgm | pnmflip -lr | + pnmscale -xsi 3744 -ysi 320 | sed '1,/255/d' >myface.tattoo + +So: + djpeg extracts ppm from a jpeg. Use your favorite other way of getting +this far is you wish. + + ppmtopgm changes color to grey scale + + pnmflip -lr flips left to right, the small image is faster + + pnmscale makes it 3644x320 regardless of starting size. This may make it +look really odd on the CD if it doesn't start off the right size. More on +this after I try it. + + sed strips from the first line to the line containing 255, which is the +last header line. + +Note that it would be better to use the actual height of the applicable image instead +of the maximum value of 320 and it would be even more correct to create an +image that has the right width/height ratio for the target on CD in order +get an undistorted view of the image on CD. + +For best visibility, use black text on light background. + +Source: README.cdtext from cdrtools package +Edited for cdrkit by Christian Fromme <kaner@strace.org> + diff --git a/doc/wodim/README.WORM b/doc/wodim/README.WORM new file mode 100644 index 0000000..d3e2ace --- /dev/null +++ b/doc/wodim/README.WORM @@ -0,0 +1,10 @@ +CD-R drives are anything but WORM drives, but older drives identify themselves +as WORM drives. +A Worm drive is able to write each sector once at any time without preparation. +A CD-R drives is not and never will be able to do this. +However some old drives identify as WORM drives. + +For this reason the SCSI-3 standard tells CD-R drives simply CD drives +with multi media extensions. + + diff --git a/doc/wodim/README.cdrw b/doc/wodim/README.cdrw new file mode 100644 index 0000000..cda86e9 --- /dev/null +++ b/doc/wodim/README.cdrw @@ -0,0 +1,17 @@ +Using CD-RW media Mini Howto FAQ + +CD-RW drives usually support packet writing, but as there +is currently no usable UDF filesystem support you may only use +the simple wodim approach. + +wodim writes to CD-RW media in exactly the same way as it +does with CD-R. + +You may erase a complete disk in preparation to reuse it. +Check the man page entry for the blank= option of wodim. +Not all drives support all blanking modes. Usually +blank=fast or blank=full are working. + +Source: README.cdtext from cdrtools package +Edited for cdrkit by Christian Fromme <kaner@strace.org> + diff --git a/doc/wodim/README.clone b/doc/wodim/README.clone new file mode 100644 index 0000000..4964730 --- /dev/null +++ b/doc/wodim/README.clone @@ -0,0 +1,27 @@ +Hints for how to copy a CD using the clone method: + +Step 1 (read master CD): + + Call "readcd dev=b,t,l -clone f=somefile" and the files + + somefile + and + somefile.toc + + will be generated. + + If the disk contains many sectors that are unreadable by intention, + call "readcd dev=b,t,l -clone -nocorr f=somefile" + + +Step 2 (write copy): + + Call "wodim dev=b,t,l -raw96r -clone -v somefile" + +If wodim complains that your drive does not support -raw96r, but the +drive is able to do clone writing at all, then wodim will propose you +a different write mode that works with the drive. + +Source: README.clone from cdrtools package +Edited for cdrkit by Christian Fromme <kaner@strace.org> + diff --git a/doc/wodim/README.raw b/doc/wodim/README.raw new file mode 100644 index 0000000..4629f66 --- /dev/null +++ b/doc/wodim/README.raw @@ -0,0 +1,71 @@ +Tips for MMC RAW mode writing. + + This allows to do disk at once recording on Philips drives that + do not support SAO. + + You may write audio tracks in RAW mode. There are some new + and most likely transient options: + + -raw16 Write 2352 Bytes sectors + P+Q Subchannel + + -raw96r Write 2352 Bytes sectors + P+W Subchannel (R-W in raw mode) + + -raw96p Write 2352 Bytes sectors + P+W Subchannel (R-W in packed mode) + + NOTE that the MMC standard does not allow -dummy in RAW mode. + There may be drives which allow it but don't bother if it does not work. + + Indices are fully supported in RAW mode. + + MCN & ISRC are not yet supported in RAW mode, they are silently discarded. + + If you find other problems in RAW mode or if you find + new bugs introduced in old write modes, please send a bug report. + + wodim now checks the properties of the writer. If a specific write + mode is not supported by the writer, wodim warns you and makes + a suggestion for a similar alternate write mode. + + With the curent structure of wodim, it is not possible to silently + e.g. change the write mode from -dao to -raw96r + + MMC compliant drives are automatically scanned for supported write modes. + This should help to make wodim work without manual static configuration. + My hope is still to have no need to know all drive properties in + advance, so new drives will continue to work as long as they + are standard compliant enough for wodim. + +EXAMPLES: + + wodim dev=1,0 -v -raw96r *.wav + + will write a audio CD in raw mode using (computed) 2448 byte sectors + with raw P-W subchannels. This works e.g. with Plextor drives. + + + wodim dev=1,0 -v -raw16 *.wav + + will write a audio CD in raw mode using (computed) 2368 byte sectors + with raw P+Q subchannels. This works e.g. with Philips drives. + + + NOTE: The input sector size always is 2352 bytes for audio. + +IMPORTANT: + + - if the drive supports RAW/R96R among with other raw write modes, + use -raw96r + + - if the drive does _only_ supports RAW/R16, use -raw16 + + - ... else if the drive supports RAW/R96P, use -raw96p + + The packed raw mode (RAW/R96P) is buggy in Plextor drives and + the RAW/R16 mode is buggy in TEAC drives. Plextor creates + unreadable disks and TEAC hangs the drive. + + For this reason, it is important to select the raw writing + mode accoding to the notes above. + +Source: README.raw from cdrtools package +Edited for cdrkit by Christian Fromme <kaner@strace.org> |