1wodim(1)                                                              wodim(1)
2
3
4

NAME

6       wodim - write data to optical disk media
7

SYNOPSIS

9       wodim [options] track1...trackn
10

NOTE

12       There  may  be  similarities  and  differences between this program and
13       other disk recording application(s). See the CREDITS and  AUTHORS  sec‐
14       tions below to learn about the origin of wodim.
15
16

DESCRIPTION

18       wodim  is  used to record data or audio Compact Discs on an Orange Book
19       CD-Recorder or to write DVD media on a DVD-Recorder.
20
21       The device is the device file or label offered by the operating  system
22       to access the recorder with SCSI GENERIC (sg) interface. Note that some
23       operating systems may provide separate device nodes for  block-oriented
24       and  sg  access. For example, on older Linux systems, the sg access was
25       available through /dev/sg...  files while the block oriented access was
26       done  through associated (but not identical) /dev/hd...  and /dev/sr...
27       (or /dev/scd...  ) files.
28
29       In any case, the user running wodim needs read and write access to  the
30       particular  device file on a Linux system. It is recommended to be root
31       or install the application as suid-root, because  certain  versions  of
32       Linux  (kernel)  limit  the  set  of SCSI commands allowed for non-root
33       users. Even if usage without root identity is possible in  many  cases,
34       some  device  drivers  still  may fail, show unexplainable problems and
35       generally the problems become harder to debug.  The  risk  for  buffer-
36       underruns  is  also increased. See the PROCESS SCHEDULING PRIORITY sec‐
37       tion below for more details.
38
39       There is an alternative way of specifying the device, using the  tradi‐
40       tional  SCSI descriptions in form of devicetype:bus/target/lun specifi‐
41       cation. However, the success of this method is not guaranteed since  it
42       requires  an  adaptation  scheme for your architecture, and the numbers
43       may vary depending on the hardware-internal numbering or on  the  order
44       of hot-plug device detection. If your operating system does not provide
45       a sufficient framework for keeping this numbers persistent, don't  rely
46       on them. See -scanbus and --devices options below for details.
47
48       There  are emulated SCSI compatible device systems, using the SCSI pro‐
49       tocols transported over various hardware/media types.  The  most  known
50       examples is ATAPI ("IDE burners") or USB storage ("external USB case").
51       If the pseudo-SCSI b/t/l device address specification is  used  instead
52       of the native one, you need to prepend the "devicetype:" description to
53       the emulated "bus/target/lun" device address.
54
55       If a file /etc/wodim.conf exists, the parameter to the dev= option  may
56       also be a drive name label in that file (see FILES section).
57
58       As  a  special  exception,  the  device specification can be -1 or just
59       omitted, which invokes automatic guessing of an appropriate device  for
60       the  selected operation. However, this guessing is not available every‐
61       where and is not reliable; it is only available for the  user's  conve‐
62       nience in simple environments.
63
64       In  Track  At  Once  mode, each track corresponds to a single file that
65       contains the prepared data for that track.  If  the  argument  is  `-',
66       standard  input  is  used  for that track.  Only one track may be taken
67       from stdin.  In the other write modes, the direct file to  track  rela‐
68       tion  may  not  be implemented.  In -clone mode, a single file contains
69       all data for the whole disk.  To allow DVD writing on platforms that do
70       not implement large file support, wodim concatenates all file arguments
71       to a single track when writing to DVD media.
72
73

PROCESS SCHEDULING PRIORITY

75       Wodim tries to get higher process  priority  using  different  methods.
76       This  is important because the burn process is usually a realtime task,
77       no long delays should  occur  while  transmitting  fresh  data  to  the
78       recorder. This is especially important on systems with insufficient RAM
79       where swapping can create delays of many seconds.
80
81       A possible workaround on underpowered systems is the use of  the  burn‐
82       free or similar feature, allowing the recorder to resume.
83
84       Root  permissions are usually required to get higher process scheduling
85       priority.
86
87       On SVr4 compliant systems, wodim uses the real time class  to  get  the
88       highest  scheduling  priority  that is possible (higher than all kernel
89       processes).  On systems with POSIX real time scheduling wodim uses real
90       time  scheduling  too,  but  may not be able to gain a priority that is
91       higher than all kernel processes.
92
93       In order to be able to use the SCSI transport subsystem of the OS,  run
94       at  highest priority and lock itself into core wodim either needs to be
95       run as root, needs to be installed suid root  or  must  be  called  via
96       RBACs pfexec mechanism.
97
98

GENERAL OPTIONS

100       General options must be before any track file name or track option.
101
102       -version
103              Print version information and exit.
104
105       -v     Increment  the  level of general verbosity by one.  This is used
106              e.g. to display the progress of the writing process.
107
108       -V     Increment the verbose level in respect of SCSI command transport
109              by  one.   This  helps  to  debug  problems  during  the writing
110              process, that occur in the CD/DVD-Recorder.  If you  get  incom‐
111              prehensible  error messages you should use this flag to get more
112              detailed output.  -VV will show data buffer content in addition.
113              Using -V or -VV slows down the process and may be the reason for
114              a buffer underrun.
115
116       debug=#, -d
117              Set the misc debug value to # (with debug=#)  or  increment  the
118              misc  debug  level  by  one  (with -d). If you specify -dd, this
119              equals to debug=2.  This may help to find problems while opening
120              a  driver  for  libusal  as well as with sector sizes and sector
121              types.  Using -debug slows down the process and may be the  rea‐
122              son for a buffer underrun.
123
124       kdebug=#, kd=#
125              Tell the usal-driver to modify the kernel debug value while SCSI
126              commands are running.
127
128       -silent, -s
129              Do not print out a status report for failed SCSI commands.
130
131       -force Force to continue on some errors. Be  careful  when  using  this
132              option.   wodim  implements several checks that prevent you from
133              doing unwanted things like  damaging  CD-RW  media  by  improper
134              drives.  Many  of the sanity checks are disabled when the -force
135              option is used.
136
137              This option also implements some tricks that will allow  you  to
138              blank bad CD-RW disks.
139
140       -immed Tell  wodim  to  set  the  SCSI  IMMED  flag in certain commands
141              (load/eject/blank/close_track/close_session).  This can be  use‐
142              ful  on  broken systems with ATAPI harddisk and CD/DVD writer on
143              the same bus  or  with  SCSI  systems  that  don't  use  discon‐
144              nect/reconnect.   These  systems  will  freeze while blanking or
145              fixating a CD/DVD or while a DVD writer is filling up a  session
146              to the minimum amount (approx. 800 MB).  Setting the -immed flag
147              will request the command to return immediately while the  opera‐
148              tion proceeds in background, making the bus usable for the other
149              devices and avoiding the system freeze.  This is an experimental
150              feature  which  may  work  or not, depending on the model of the
151              CD/DVD writer.  A correct solution would be to set up a  correct
152              cabling but there seem to be notebooks around that have been set
153              up the wrong way by the manufacturer.  As it  is  impossible  to
154              fix this problem in notebooks, the -immed option has been added.
155
156              A  second  experimental  feature  of  the -immed flag is to tell
157              wodim to try to wait short times while  writing  to  the  media.
158              This  is  expected  to free the IDE bus if the CD/DVD writer and
159              the data source are connected to the same  IDE  cable.  In  this
160              case,  the  CD/DVD  writer would otherwise usually block the IDE
161              bus for nearly all the time making it impossible to  fetch  data
162              from the source drive. See also minbuf= and -v option.
163
164              Use  both  features  at  your own risk.  If it turns out that it
165              would make sense to have a separate option for the wait feature,
166              write to the author and convince him.
167
168       minbuf=value
169              The  #  minbuf= option allows to define the minimum drive buffer
170              fill ratio for the experimental ATAPI wait mode that is intended
171              to  free  the IDE bus to allow hard disk and CD/DVD writer to be
172              on the same IDE cable.  As the wait mode  currently  only  works
173              when the verbose option -v has been specified, wodim implies the
174              verbose option in case the -immed or minbuf=  option  have  been
175              specified.   Valid  values for minbuf= are between 25 and 95 for
176              25%...95% minimum drive buffer fill ratio.
177
178       -dummy The CD/DVD-Recorder will go through all steps of  the  recording
179              process,  but the laser is turned off during this procedure.  It
180              is recommended to run several tests before actually writing to a
181              Compact  Disk  or Digital Versatile Disk, if the timing and load
182              response of the system is not known.
183
184       -clone Tells wodim to handle images  created  by  readom  -clone.   The
185              -clone  may only be used in conjunction with with the -raw96r or
186              with the -raw16 option.  Using -clone together with  -raw96r  is
187              preferred as it allows to write all subchannel data.  The option
188              -raw16 should only be used with drives that do  not  support  to
189              write in -raw96r mode.
190
191       -dao
192
193       -sao   Set  SAO  (Session At Once) mode which is usually called Disk At
194              Once mode.  This currently only works with MMC drives that  sup‐
195              port  Session  At  Once mode.  Note that wodim needs to know the
196              size of each track in advance for this mode (see the genisoimage
197              -print-size  option  and  the EXAMPLES section for more informa‐
198              tion).
199
200       -tao   Set TAO (Track At Once) writing mode.  This is the default write
201              mode  in  previous wodim versions.  With most drives, this write
202              mode is required for multi session recording.
203
204       -raw   Set RAW writing mode.  Using this option  defaults  to  -raw96r.
205              Note  that wodim needs to know the size of each track in advance
206              for this mode (see the genisoimage -print-size  option  and  the
207              EXAMPLES section for more information).
208
209       -raw96r
210              Select Set RAW writing mode with 2352 byte sectors plus 96 bytes
211              of raw P-W subchannel data resulting in a sector  size  of  2448
212              bytes.   This is the preferred raw writing mode as it gives best
213              control over the CD writing process.  If you find  any  problems
214              with  the  layout  of  a  disk or with sub channel content (e.g.
215              wrong times on the display when playing the CD) and  your  drive
216              supports  to write in -raw96r or -raw16 mode, you should give it
217              a try. There are several  CD  writers  with  bad  firmware  that
218              result in broken disks when writing in TAO or SAO mode.  Writing
219              data disks in raw mode needs significantly more  CPU  time  than
220              other  write  modes. If your CPU is too slow, this may result in
221              buffer underruns.  Note that wodim needs to  know  the  size  of
222              each track in advance for this mode (see the genisoimage -print-
223              size option and the EXAMPLES section for more information).
224
225       -raw96p
226              Select Set RAW writing mode with 2352 byte sectors plus 96 bytes
227              of packed P-W subchannel data resulting in a sector size of 2448
228              bytes.  This is the less preferred raw writing mode  as  only  a
229              few  recorders  support it and some of these recorders have bugs
230              in the firmware implementation.  Don't use  this  mode  if  your
231              recorder  supports -raw96r or -raw16.  Writing data disks in raw
232              mode needs significantly more CPU time than other  write  modes.
233              If  your  CPU  is too slow, this may result in buffer underruns.
234              Note that wodim needs to know the size of each track in  advance
235              for  this  mode  (see the genisoimage -print-size option and the
236              EXAMPLES section for more information).
237
238       -raw16 Select Set RAW writing mode with 2352 byte sectors plus 16 bytes
239              of P-Q subchannel data resulting in a sector size of 2368 bytes.
240              If a recorder does not support -raw96r, this  is  the  preferred
241              raw  writing  mode.   It  does  not  allow  to  write CD-Text or
242              CD+Graphics but it is the only raw  writing  mode  in  cheap  CD
243              writers.   As  these  cheap writers in most cases do not support
244              -dao mode.  Don't  use  this  mode  if  your  recorder  supports
245              -raw96r.   Writing  data  disks  in raw mode needs significantly
246              more CPU time than other write modes. If your CPU is  too  slow,
247              this  may  result in buffer underruns.  Note that wodim needs to
248              know the size of each track in advance for this  mode  (see  the
249              genisoimage -print-size option and the EXAMPLES section for more
250              information).
251
252       -multi Allow multi session CDs to  be  made.  This  flag  needs  to  be
253              present on all sessions of a multi session disk, except you want
254              to create a session that will be the last session on the  media.
255              The  fixation  will  be  done  in  a way that allows the CD/DVD-
256              Recorder to append additional sessions later. This  is  done  by
257              generation  a  TOC  with a link to the next program area. The so
258              generated media is  not  100%  compatible  to  manufactured  CDs
259              (except  for  CDplus).   Use only for recording of multi session
260              CDs.  If this option is present, the default track type  is  CD-
261              ROM  XA mode 2 form 1 and the sector size is 2048 bytes.  The XA
262              sector subheaders will be created by the drive.  The Sony drives
263              have  no hardware support for CD-ROM XA mode 2 form 1.  You have
264              to specify the -data option in order  to  create  multi  session
265              disks  on  these drives.  As long as wodim does not have a coder
266              for converting data sectors to audio sectors, you need to  force
267              CD-ROM  sectors  by  including  the  -data option if you like to
268              record a multisession disk in SAO mode.  Not  all  drives  allow
269              multisession CDs in SAO mode.
270
271       -msinfo
272              Retrieve  multi  session info in a form suitable for genisoimage
273              and print it to standard output. See msifile= option for another
274              version.
275
276              This  option  makes  only sense with a CD that contains at least
277              one closed session and is appendable (not finally  closed  yet).
278              Some  drives  create  error messages if you try to get the multi
279              session info for a disk that is not suitable for this operation.
280
281       msifile=filename
282              Like -msinfo option but also stores the multi session info in  a
283              file.
284
285       -toc   Retrieve  and  print  out  the  table of content or PMA of a CD.
286              With this option, wodim will work with CD-R drives and with  CD-
287              ROM drives.
288
289       -atip  Retrieve  and  print  out the ATIP (absolute Time in Pre-groove)
290              info of a CD/DVD recordable or CD/DVD re-writable  media.   With
291              this  option,  wodim  will try to retrieve the ATIP info. If the
292              actual drive does not support to read the ATIP info, it  may  be
293              that  only  a reduced set of information records or even nothing
294              is displayed. Only a limited number of MMC compliant drives sup‐
295              port to read the ATIP info.
296
297              If  wodim  is  able  to  retrieve the lead-in start time for the
298              first session, it will try to decode and print the  manufacturer
299              info  from  the media.  DVD media does not have ATIP information
300              but there is equivalent prerecorded information that is read out
301              and printed.
302
303       -fix   The  disk  will only be fixated (i.e. a TOC for a CD-Reader will
304              be written).  This may be used, if for some reason the disk  has
305              been  written  but  not  fixated. This option currently does not
306              work with old TEAC drives (CD-R50S and CD-R55S).
307
308       -nofix Do not fixate the disk after writing the  tracks.  This  may  be
309              used  to  create  an audio disk in steps. An un-fixated disk can
310              usually not be used on a non CD-writer type drive but there  are
311              audio CD players that will be able to play such a disk.
312
313       -waiti Wait for input to become available on standard input before try‐
314              ing to open the SCSI driver. This allows wodim to read its input
315              from  a  pipe  even  when writing additional sessions to a multi
316              session disk.  When writing another session to a  multi  session
317              disk,  genisoimage needs to read the old session from the device
318              before writing output.  This cannot be done if wodim  opens  the
319              SCSI driver at the same time.
320
321       -load  Load  the  media  and  exit. This only works with a tray loading
322              mechanism but seems to be  useful  when  using  the  Kodak  disk
323              transporter.
324
325       -lock  Load  the  media, lock the door and exit. This only works with a
326              tray loading mechanism but seems to be  useful  when  using  the
327              Kodak disk transporter.
328
329       -eject Eject  disk  after  doing the work.  Some devices (e.g. Philips)
330              need to eject the medium before creating a  new  disk.  Doing  a
331              -dummy  test and immediately creating a real disk would not work
332              on these devices.
333
334       speed=#
335              Set the speed factor of the writing process to #.  # is an inte‐
336              ger,  representing a multiple of the audio speed.  This is about
337              150 KB/s for CD-ROM,  about  172 KB/s  for  CD-Audio  and  about
338              1385 kB/s  for  DVD media.  If no speed option is present, wodim
339              will try to get a drive  specific  speed  value  from  the  file
340              /etc/wodim.conf  and  if  it cannot find one, it will try to get
341              the speed value from the CDR_SPEED environment  and  later  from
342              the  CDR_SPEED=  entry  in  /etc/wodim.conf.   If no speed value
343              could be found, wodim uses a drive specific default speed.   The
344              default for all new (MMC compliant) drives is to use the maximum
345              supported by the drive.  If you use speed=0 with a MMC compliant
346              drive,  wodim will switch to the lowest possible speed for drive
347              and medium.  If you are using an old (non MMC)  drive  that  has
348              problems with speed=2 or speed=4, you should try speed=0.
349
350       blank=type
351              Blank  a  CD-RW  and  exit  or blank a CD-RW before writing. The
352              blanking type may be one of:
353
354              help        Display a list of possible blanking types.
355
356              all         Blank the entire disk. This may take a long time.
357
358              fast        Minimally blank the disk. This  results  in  erasing
359                          the PMA, the TOC and the pregap.
360
361              track       Blank a track.
362
363              unreserve   Unreserve a reserved track.
364
365              trtail      Blank the tail of a track.
366
367              unclose     Unclose last session.
368
369              session     Blank the last session.
370       Not  all  drives support all blanking types. It may be necessary to use
371       blank=all if a drive reports a specified command as being invalid.   If
372       used  together  with  the -force flag, this option may be used to blank
373       CD-RW disks that otherwise cannot be blanked. Note that you may need to
374       specify  blank=all  because  some drives will not continue with certain
375       types of bad CD-RW disks. Note also that wodim does  its  best  if  the
376       -force  flag  is  used  but  it finally depends on the drive's firmware
377       whether the blanking operation will succeed or not.
378
379       -format
380              Format a CD-RW/DVD-RW/DVD+RW disc.  Formatting is currently only
381              implemented  for DVD+RW media.  A 'maiden' DVD+RW media needs to
382              be formatted before you may write  to  it.   However,  as  wodim
383              autodetects  the  need for formatting in this case and auto for‐
384              mats the medium before it starts writing, the -format option  is
385              only needed if you like to forcibly reformat a DVD+RW medium.
386
387       fs=#   Set the FIFO (ring buffer) size to #.  You may use the same syn‐
388              tax as in dd(1), sdd(1) or star(1).  The number representing the
389              size  is taken in bytes unless otherwise specified.  If a number
390              is followed directly by the letter `b', `k', `m',  `s'  or  `f',
391              the  size  is  multiplied by 512, 1024, 1024*1024, 2048 or 2352.
392              If the size consists of numbers separated by `x' or `*',  multi‐
393              plication  of the two numbers is performed.  Thus fs=10x63k will
394              specify a FIFO size of 630 kBytes.
395
396              The size specified by the fs= argument includes the shared  mem‐
397              ory that is needed for administration. This is at least one page
398              of memory.  If no fs= option is present, wodim will try  to  get
399              the  FIFO  size  value  from  the CDR_FIFOSIZE environment.  The
400              default FIFO size is currently 4 MB.
401
402              The FIFO is used to increase buffering for the real time writing
403              process.  It allows to run a pipe from genisoimage directly into
404              wodim.  If the FIFO is active and a pipe from  genisoimage  into
405              wodim  is  used to create a CD, wodim will abort prior to do any
406              modifications on the disk if genisoimage dies before  it  starts
407              writing.  The recommended FIFO size is between 4 and 128 MBytes.
408              As a rule of thumb, the FIFO size should be at  least  equal  to
409              the  size  of  the internal buffer of the CD/DVD-Recorder and no
410              more than half of the physical amount of RAM  available  in  the
411              machine.   If  the  FIFO size is big enough, the FIFO statistics
412              will print a FIFO empty count of zero and the FIFO min  fill  is
413              not  below  20%.   It  is not wise to use too much space for the
414              FIFO. If you need more than 8 MB to write a CD at a  speed  less
415              than  20x  from  an  image  on  a  local  file system on an idle
416              machine, your machine is either underpowered, has hardware prob‐
417              lems  or is mis-configured.  If you like to write DVDs or CDs at
418              higher speed, it makes sense to use at least 16 MB for the FIFO.
419
420              On old and small machines, you need to be more careful with  the
421              FIFO  size.   If  your  machine has less than 256 MB of physical
422              RAM, you should not set up a FIFO size that is more than  32 MB.
423              The sun4c architecture (e.g. a Sparcstation-2) has only MMU page
424              table  entries  for  16 MBytes  per  process.  Using  more  than
425              14 MBytes  for  the  FIFO may cause the operating system in this
426              case to spend much time to constantly  reload  the  MMU  tables.
427              Newer machines from Sun do not have this MMU hardware problem. I
428              have no information on PC-hardware reflecting this problem.
429
430              Old Linux systems for non x86 platforms have broken  definitions
431              for the shared memory size. You need to fix them and rebuild the
432              kernel or manually tell wodim to use a smaller FIFO.
433
434              If you have buffer underruns or similar problems  (like  a  con‐
435              stantly empty drive buffer) and observe a zero fifo empty count,
436              you have hardware problems that prevents the data  from  flowing
437              fast  enough  from the kernel memory to the drive. The FIFO size
438              in this case is sufficient, but you should check for  a  working
439              DMA setup.
440
441       ts=#   Set  the  maximum  transfer size for a single SCSI command to #.
442              The syntax for the ts= option is the same as for wodim  fs=#  or
443              sdd bs=#.
444
445              If  no ts= option has been specified, wodim defaults to a trans‐
446              fer size of 63 kB. If libusal gets lower values from the operat‐
447              ing  system,  the  value is reduced to the maximum value that is
448              possible with the current operating system.  Sometimes,  it  may
449              help  to  further reduce the transfer size or to enhance it, but
450              note that it may take a long time to  find  a  better  value  by
451              experimenting with the ts= option.
452
453       dev=target
454              Sets  the  SCSI target for the CD/DVD-Recorder, see notes above.
455              A typical device specification is dev=6,0 .  A filename or  vir‐
456              tual device name can be passed instead of the symbolic SCSI num‐
457              bers.  The correct device/filename in this case can be found  in
458              the  system specific manuals of the target operating system.  On
459              a FreeBSD system without CAM support, you need to use  the  con‐
460              trol  device (e.g.  /dev/rcd0.ctl).  A correct device specifica‐
461              tion in this case may be dev=/dev/rcd0.ctl:@ .
462
463              On Linux and Windows 2000/XP, drives are accessible  with  their
464              device  (or  drive) names or with the symbolic SCSI numbers (not
465              recommended, mapping is  not  stable  and  could  be  completely
466              removed in the future).
467
468              If  no  dev  option is present, wodim will try to get the device
469              from the CDR_DEVICE environment.
470
471              If the argument to the dev= option does not contain the  charac‐
472              ters  ',',  '/',  '@' or ':', it is interpreted as an label name
473              that may be found in the file /etc/wodim.conf  (see  FILES  sec‐
474              tion).
475
476       gracetime=#
477              Set  the grace time before starting to write to # seconds.  Val‐
478              ues below 2 seconds are not recommended to give  the  kernel  or
479              volume management a chance to learn the new state.
480
481       timeout=#
482              Set  the  default  SCSI command timeout value to # seconds.  The
483              default SCSI command timeout is the  minimum  timeout  used  for
484              sending  SCSI  commands.  If a SCSI command fails due to a time‐
485              out, you may try to raise the default SCSI command timeout above
486              the  timeout  value  of the failed command.  If the command runs
487              correctly with a raised command timeout, please report the  bet‐
488              ter timeout value and the corresponding command to the author of
489              the program.  If no timeout option is present, a default timeout
490              of 40 seconds is used.
491
492       driver=name
493              Allows the user to manually select a driver for the device.  The
494              reason for the existence of the driver=name option is  to  allow
495              users  to  use  wodim  with drives that are similar to supported
496              drives but not known directly by wodim.  All drives  made  after
497              1997  should be MMC standard compliant and thus supported by one
498              of the MMC drivers.  It is most unlikely that wodim is unable to
499              find  the  right  driver  automatically.   Use  this option with
500              extreme care. If a wrong driver is used for a device, the possi‐
501              bility of creating corrupted disks is high.  The minimum problem
502              related to a wrong driver is that the speed= or -dummy will  not
503              work.
504
505              The following driver names are supported:
506
507              help   To  get  a list of possible drivers together with a short
508                     description.
509
510              mmc_cd The generic SCSI-3/mmc  CD-ROM  driver  is  auto-selected
511                     whenever  wodim finds a MMC compliant drive that does not
512                     identify itself to support writing at all, or  that  only
513                     identifies  to  support  media  or write modes not imple‐
514                     mented in wodim.
515
516              mmc_cd_dvd
517                     The generic SCSI-3/mmc  CD/DVD  driver  is  auto-selected
518                     whenever  wodim  finds  a  MMC-2 or MMC-3 compliant drive
519                     that seems to support more than one medium type  and  the
520                     tray  is  open  or no medium could be found to select the
521                     right driver.  This  driver  tries  to  close  the  tray,
522                     checks  the medium found in the tray and then branches to
523                     the driver that matches the current medium.
524
525              mmc_cdr
526                     The generic SCSI-3/mmc CD-R/CD-RW driver is auto-selected
527                     whenever  wodim find a MMC compliant drive that only sup‐
528                     ports to write CDs or a multi system drive that  contains
529                     a CD as the current medium.
530
531              mmc_cdr_sony
532                     The generic SCSI-3/mmc CD-R/CD-RW driver is auto-selected
533                     whenever wodim would otherwise select the mmc_cdr  driver
534                     but   the   device   seems  to  be  made  by  Sony.   The
535                     mmc_cdr_sony is definitely needed for the Sony CDU 928 as
536                     this drive does not completely implement the MMC standard
537                     and some of the MMC SCSI commands have to be replaced  by
538                     Sony  proprietary commands. It seems that all Sony drives
539                     (even newer ones) still implement  the  Sony  proprietary
540                     SCSI  commands  so it has not yet become a problem to use
541                     this driver for all Sony drives. If you find a newer Sony
542                     drive that does not work with this driver, please report.
543
544              mmc_mdvd
545                     The  generic  SCSI-3/mmc-2  DVD-R/DVD-RW  driver is auto-
546                     selected whenever wodim finds a MMC-2 or MMC-3  compliant
547                     drive  that  supports  to  write  DVDs and an appropriate
548                     medium is loaded.  Note that for unknown reason, the DVD-
549                     Plus  alliance  does  not like that there is a simulation
550                     mode for DVD+R and DVD+RW media nor a way to erase DVD+RW
551                     media.   DVD+R  and  DVD+RW  only supports one write mode
552                     that is somewhere between Track At Once and Packet  writ‐
553                     ing;  this  mode is selected in wodim via a the -dao/-sao
554                     option.  As DVD+RW media needs to be formatted before its
555                     first  use,  wodim auto-detects this media state and per‐
556                     forms a format before it starts to write.
557
558                     Note: If you have any problems during burning DVDs  using
559                     wodim,  please  consider  growisofs  from package dvd+rw-
560                     tools, which often works better in these cases.
561
562              cw_7501
563                     The driver  for  Matsushita/Panasonic  CW-7501  is  auto-
564                     selected  when wodim finds this old pre MMC drive.  wodim
565                     supports all write modes for this drive type.
566
567              kodak_pcd_600
568                     The driver for Kodak PCD-600 is auto-selected when  wodim
569                     finds  this  old  pre  MMC drive which has been the first
570                     high speed (6x) CD writer for a  long  time.  This  drive
571                     behaves similar to the Philips CDD-521 drive.
572
573              philips_cdd521
574                     The  driver  for  Philips  CDD-521  is auto-selected when
575                     wodim finds a Philips CDD-521 drive (which is  the  first
576                     CD  writer ever made) or one of the other drives that are
577                     known to behave  similar  to  this  drive.   All  Philips
578                     CDD-521  or  similar  drives  (see  other drivers in this
579                     list) do not support Session At Once recording.
580
581              philips_cdd521_old
582                     The driver for Philips old CDD-521 is auto-selected  when
583                     wodim  finds  a  Philips  CDD-521  with very old firmware
584                     which has some known limitations.
585
586              philips_cdd522
587                     The driver for  Philips  CDD-522  is  auto-selected  when
588                     wodim  finds  a Philips CDD-522 which is the successor of
589                     the 521 or one of its variants with Kodak  label.   wodim
590                     does  not  support  Session  At Once recording with these
591                     drives.
592
593              philips_dumb
594                     The driver for Philips CDD-521 with  pessimistic  assump‐
595                     tions  is  never  auto-selected.   It may be used by hand
596                     with drives that behave similar to the Philips CDD-521.
597
598              pioneer_dws114x
599                     The driver for Pioneer  DW-S114X  is  auto-selected  when
600                     wodim  finds  one of the old non MMC CD writers from Pio‐
601                     neer.
602
603              plasmon_rf4100
604                     The driver for Plasmon  RF  4100  is  auto-selected  when
605                     wodim finds this specific variant of the Philips CDD-521.
606
607              ricoh_ro1060c
608                     The driver for Ricoh RO-1060C is auto-selected when wodim
609                     finds this drive. There is no real support for this drive
610                     yet.
611
612              ricoh_ro1420c
613                     The driver for Ricoh RO-1420C is auto-selected when wodim
614                     finds a drive with this specific variant of  the  Philips
615                     CDD-521 command set.
616
617              scsi2_cd
618                     The  generic  SCSI-2 CD-ROM driver is auto-selected when‐
619                     ever wodim finds a pre MMC drive that  does  not  support
620                     writing  or  a  pre  MMC  writer that is not supported by
621                     wodim.
622
623              sony_cdu924
624                     The driver for Sony CDU-924 /  CDU-948  is  auto-selected
625                     whenever  wodim  finds  one of the old pre MMC CD writers
626                     from Sony.
627
628              teac_cdr50
629                     The driver for Teac CD-R50S, Teac CD-R55S, JVC  XR-W2010,
630                     Pinnacle  RCD-5020  is  auto-selected whenever one of the
631                     drives is found that is known to the non MMC command  set
632                     used  by  TEAC  and  JVC.  Note that many drives from JVC
633                     will not work because they do not correctly implement the
634                     documented  command set and JVC has been unwilling to fix
635                     or document the bugs.  There is no support for  the  Ses‐
636                     sion At Once write mode yet.
637
638              tyuden_ew50
639                     The  driver  for  Taiyo Yuden EW-50 is auto-selected when
640                     wodim finds a drive with this  specific  variant  of  the
641                     Philips CDD-521 command set.
642
643              yamaha_cdr100
644                     The  driver for Yamaha CDR-100 / CDR-102 is auto-selected
645                     when wodim finds one of the old pre MMC CD  writers  from
646                     Yamaha.   There  is  no  support  for the Session At Once
647                     write mode yet.
648
649              cdr_simul
650                     The simulation CD-R driver allows to run timing and speed
651                     tests with parameters that match the behavior of CD writ‐
652                     ers.
653
654              dvd_simul
655                     The simulation DVD-R driver  allows  to  run  timing  and
656                     speed  tests  with  parameters that match the behavior of
657                     DVD writers.
658
659              There are two special driver entries in the list: cdr_simul  and
660              dvd_simul.   These  driver  entries  are designed to make timing
661              tests at any speed or timing tests for drives that do  not  sup‐
662              port  the  -dummy  option.   The  simulation drivers implement a
663              drive with a buffer size of 1 MB that can  be  changed  via  the
664              CDR_SIMUL_BUFSIZE  environment  variable.  The simulation driver
665              correctly simulates even a buffer underrun  condition.   If  the
666              -dummy  option is present, the simulation is not aborted in case
667              of a buffer underrun.
668
669       driveropts=option list
670              Set driver specific options. The options are specified  a  comma
671              separated   list.    To   get   a  list  of  valid  options  use
672              driveropts=help together with the -checkdrive  option.   If  you
673              like to set driver options without running a typical wodim task,
674              you need to use the -setdropts option in addition, otherwise the
675              command  line  parser  in wodim will complain.  Currently imple‐
676              mented driver options are:
677
678              burnfree
679                     Turn the support for Buffer  Underrun  Free  writing  on.
680                     This  only  works for drives that support Buffer Underrun
681                     Free technology, which is available on most drives  manu‐
682                     factured  in  this millennium.  This may be called: Sanyo
683                     BURN-Proof, Ricoh Just-Link, Yamaha Lossless-Link or sim‐
684                     ilar.
685
686                     This option is deprecated and is mentioned here for docu‐
687                     mentation purposes only. The BURN-Free feature is enabled
688                     by  default  if  the  drive supports it.  However, use of
689                     BURN-Free may cause decreased burning quality.  Therefore
690                     it  can be useful to disable it for certain purposes, eg.
691                     when creating a master copy for mass CD production.
692
693              noburnfree
694                     Turn the support for Buffer Underrun Free writing off.
695
696              varirec=value
697                     Turn on the Plextor VariRec writing mode.  The  mandatory
698                     parameter  value  is the laser power offset and currently
699                     may be selected from -2, -1, 0, 1, 2.  In  addition,  you
700                     need  to  set  the  write  speed  to  4 in order to allow
701                     VariRec to work.
702
703              gigarec=value
704                     Manage the Plextor GigaRec writing  mode.  The  mandatory
705                     parameter  value  is  the disk capacity ratio compared to
706                     normal recording and currently may be selected from  0.6,
707                     0.7,  0.8, 1.0, 1.2, 1.3, 1.4.  If values < 1.0 are used,
708                     then the effect is similar to the Yamaha Audio Master  Q.
709                     R.   feature.  If  values  >  1.0 are used, then the disk
710                     capacity is increased.
711
712                     Not all drives support all GigaRec values.  When a  drive
713                     uses  the  GigaRec feature, the write speed is limited to
714                     8x.
715
716              audiomaster
717                     Turn on the Yamaha Audio Master Q. R.  feature which usu‐
718                     ally  should  result  in  high quality CDs that have less
719                     reading problems in Hi-Fi players.   As  this  is  imple‐
720                     mented as a variant of the Session at Once write mode, it
721                     will only work if you select SAO write mode and there  is
722                     no  need to turn it off.  The Audio Master mode will work
723                     with a limited speed but may also be used with data  CDs.
724                     In  Audio Master mode, the pits on the CD will be written
725                     larger then usual  so  the  capacity  of  the  medium  is
726                     reduced  when  turning  this  feature on.  A 74 minute CD
727                     will only have a capacity of 63 minutes if  Audio  Master
728                     is  active  and  the  capacity  of a 80 minute CD will be
729                     reduced to 68 minutes.
730
731              forcespeed
732                     Normally, modern drives know the highest  possible  speed
733                     for  different media and may reduce the speed in order to
734                     grant best write quality.  This technology may be called:
735                     Plextor  PowerRec, Ricoh Just-Speed, Yamaha Optimum Write
736                     Speed Control or similar.   Some  drives  (e.g.  Plextor,
737                     Ricoh  and  Yamaha)  allow  to force the drive to use the
738                     selected speed even if the medium  is  so  bad  that  the
739                     write  quality  would  be  poor. This option tells such a
740                     drive to force to use the selected  speed  regardless  of
741                     the medium quality.
742
743                     Use this option with extreme care and note that the drive
744                     should know better which medium will work at full  speed.
745                     The  default is to turn forcespeed off, regardless of the
746                     defaults of the drive.
747
748              noforcespeed
749                     Turn off the force speed feature.
750
751              speedread
752                     Some ultra high speed  drives  such  as  48x  and  faster
753                     drives  from  Plextor  limit  the  read speed for unknown
754                     media to e.g. 40x in order to  avoid  damaged  disks  and
755                     drives.   Using  this  option tells the drive to read any
756                     media as fast as possible.  Be very careful as  this  may
757                     cause  the  media  to  break  in the drive while reading,
758                     resulting in a damaged media and drive!
759
760              nospeedread
761                     Turn off unlimited read speed.
762
763              singlesession
764                     Turn the drive into a single session  only  drive.   This
765                     allows to read defective or non-compliant (illegal) media
766                     with extremely non-standard  additional  (broken/illegal)
767                     TOC entries in the TOC from the second or higher session.
768                     Some of these disks become usable if only the information
769                     from  the first session is used.  You need to enable Sin‐
770                     gle Session mode before you insert the defective disk!
771
772              nosinglesession
773                     Turn off single session mode. The drive will again behave
774                     as usual.
775
776              hidecdr
777                     Hide the fact that a medium might be a recordable medium.
778                     This allows to make CD-Rs look like CD-ROMs and  applica‐
779                     tions believe that the media in the drive is not a CD-R.
780
781              nohidecdr
782                     Turn off hiding CD-R media.
783
784              tattooinfo
785                     Use this option together with -checkdrive to retrieve the
786                     image size information for the  Yamaha  DiskT@2  feature.
787                     The images always have a line length of 3744 pixel.  Line
788                     number 0 (radius 0) is mapped to the center of the  disk.
789                     If  you  know the inner and outer radius you will be able
790                     to create a pre distorted image  that  later  may  appear
791                     undistorted on the disk.
792
793              tattoofile=name
794                     Use  this  option  together  with -checkdrive to write an
795                     image prepared for the  Yamaha  DiskT@2  feature  to  the
796                     medium.   The file must be a file with raw image B&W data
797                     (one byte per pixel) in a size as retrieved by a previous
798                     call  to  tattoofile=name  .   If  the  size of the image
799                     equals the maximum possible  size  (3744  x  320  pixel),
800                     wodim  will  use  the  first part of the file. This first
801                     part then will be written to the leftover  space  on  the
802                     CD.
803
804                     Note  that the image must be mirrored to be readable from
805                     the pick up side of the CD.
806
807       -setdropts
808              Set the driveropts  specified  by  driveropts=option  list,  the
809              speed  of  the  drive  and the dummy flag and exit.  This allows
810              wodim to set drive specific parameters  that  are  not  directly
811              used by wodim like e.g.  single session mode, hide cdr and simi‐
812              lar.  It is needed in case that driveropts=option list should be
813              called without planning to run a typical wodim task.
814
815       -checkdrive
816              Checks  if  a  driver for the current drive is present and exit.
817              If the drive is a known drive, wodim uses exit code 0.
818
819       -prcap Print the drive capabilities for SCSI-3/mmc compliant drives  as
820              obtained  from  mode  page  0x2A. Values marked with kB use 1000
821              bytes as kilo-byte, values marked with  KB  use  1024  bytes  as
822              Kilo-byte.
823
824       -inq   Do an inquiry for the drive, print the inquiry info and exit.
825
826       -scanbus
827              Scan  all  SCSI devices on all SCSI busses and print the inquiry
828              strings. This option may be used to find  SCSI  address  of  the
829              CD/DVD-Recorder on a system. If some device types are invisible,
830              try using dev=ATA: or similar option to give a  hint  about  the
831              device  type  you  are  looking for.  The numbers printed out as
832              labels are computed by: bus * 100 + target.   On  platforms  and
833              device  systems  without  persistent  SCSI number management the
834              results are not reliable. Use the .B --devices option instead.
835
836       --devices
837              Look for useable devices using the  system  specific  functions,
838              eg.  probing  with usual device nodes in /dev/*, and display the
839              detections using symbolic device names in OS specific syntax.
840
841       -reset Try to reset the SCSI bus where the CD recorder is located. This
842              works not on all operating systems.
843
844       -abort Try  to  send  an abort sequence to the drive.  If you use wodim
845              only, this should never be needed; but other software may  leave
846              a  drive  in an unusable condition.  Calling wodim -reset may be
847              needed if a previous write has been interrupted and the software
848              did not tell the drive that it will not continue to write.
849
850       -overburn
851              Allow  wodim  to  write more than the official size of a medium.
852              This feature is usually called overburning and  depends  on  the
853              fact that most blank media may hold more space than the official
854              size. As the official size of the lead-out area on the  disk  is
855              90  seconds (6750 sectors) and a disk usually works if there are
856              at least 150 sectors of lead out, all media may be overburned by
857              at  least  88 seconds (6600 sectors).  Most CD recorders only do
858              overburning in SAO or RAW mode. Known exceptions  are  TEAC  CD-
859              R50S,  TEAC  CD-R55S  and the Panasonic CW-7502.  Some drives do
860              not allow to overburn as much as you might like  and  limit  the
861              size  of  a  CD  to e.g. 76 minutes. This problem may be circum‐
862              vented by writing the CD in RAW mode because this way the  drive
863              has  no  chance to find the size before starting to burn.  There
864              is no guarantee that your drive  supports  overburning  at  all.
865              Make a test to check if your drive implements the feature.
866
867       -ignsize
868              Ignore  the known size of the medium. This option should be used
869              with extreme care, it exists only for debugging  purposes  don't
870              use  it for other reasons.  It is not needed to write disks with
871              more than the nominal capacity.  This option implies -overburn.
872
873       -useinfo
874              Use *.inf files to overwrite audio options.  If this  option  is
875              used,  the  pregap  size information is read from the *.inf file
876              that is associated with the file that contains  the  audio  data
877              for a track.
878
879              If  used  together  with the -audio option, wodim may be used to
880              write audio CDs from a pipe from icedax if you call  wodim  with
881              the  *.inf  files as track parameter list instead of using audio
882              files.  The audio data is read from stdin  in  this  case.   See
883              EXAMPLES  section below.  wodim first verifies that stdin is not
884              connected to a terminal  and  runs  some  heuristic  consistency
885              checks  on  the *.inf files and then sets the track lengths from
886              the information in the *.inf files.
887
888              If you like to write from stdin, make sure that wodim is  called
889              with a large enough FIFO size, reduce the write speed to a value
890              below the read speed of the source drive and  switch  the  burn-
891              free option for the recording drive on.
892
893       defpregap=#
894              Set  the default pre-gap size for all tracks except track number
895              1.  This option currently only makes sense with the  TEAC  drive
896              when  creating  track-at-once disks without the 2 second silence
897              before each track.
898              This option may go away in future.
899
900       -packet
901              Set Packet writing mode.  This is an experimental interface.
902
903       pktsize=#
904              Set the packet size to #, forces fixed packet mode.  This is  an
905              experimental interface.
906
907       -noclose
908              Do not close the current track, useful only when in packet writ‐
909              ing mode.  This is an experimental interface.
910
911       mcn=med_cat_nr
912              Set the Media Catalog Number of the CD to med_cat_nr.
913
914       -text  Write CD-Text information based on information taken from a file
915              that  contains  ascii  information  for the text strings.  wodim
916              supports CD-Text information based on the content of  the  *.inf
917              files  created  by  icedax  and CD-Text information based on the
918              content from a CUE sheet file.  If a  CUE  sheet  file  contains
919              both (binary CDTEXTFILE and text based SONGWRITER) entries, then
920              the information based on the CDTEXTFILE entry will win.
921
922              You need to use the -useinfo option in addition in order to tell
923              wodim  to  read  the *.inf files or cuefile=filename in order to
924              tell wodim to read a CUE sheet file in addition.  If you like to
925              write  your own CD-Text information, edit the *.inf files or the
926              CUE sheet file with a text editor and change the fields that are
927              relevant for CD-Text.
928
929       textfile=filename
930              Write  CD-Text  based  on  information  found in the binary file
931              filename.  This file must contain information in a  data  format
932              defined  in  the  SCSI-3 MMC-2 standard and in the Red Book. The
933              four byte size header that is defined in the  SCSI  standard  is
934              optional and allows to make the recognition of correct data less
935              ambiguous.  This is the best option to be used to  copy  CD-Text
936              data  from  existing CDs that already carry CD-Text information.
937              To get data in a format suitable for this option use  wodim  -vv
938              -toc   to   extract   the   information  from  disk.   If  both,
939              textfile=filename and CD-Text information from  *.inf  or  *.cue
940              files  are  present,  textfile=filename will overwrite the other
941              information.
942
943       cuefile=filename
944              Take all recording related information from a  CDRWIN  compliant
945              CUE  sheet file.  No track files are allowed when this option is
946              present and the option -dao is currently needed in addition.
947
948

TRACK OPTIONS

950       Track options may be mixed with track file names.
951
952       isrc=ISRC_number
953              Set the International Standard Recording  Number  for  the  next
954              track to ISRC_number.
955
956       index=list
957              Sets an index list for the next track.  In index list is a comma
958              separated list of numbers that are counting from  index  1.  The
959              first entry in this list must contain a 0, the following numbers
960              must be an ascending list of numbers (counting in 1/75  seconds)
961              that  represent  the  start of the indices. An index list in the
962              form: 0,7500,15000 sets index 1 to the start of the track, index
963              2  100  seconds from the start of the track and index 3 200 sec‐
964              onds from the start of the track.
965
966       -audio If this flag is present, all subsequent tracks  are  written  in
967              CD-DA  (similar  to  Red Book) audio format.  The file with data
968              for this tracks should contain stereo, 16-bit digital audio with
969              44100  samples/s.   The  byte order should be the following: MSB
970              left, LSB left, MSB right, LSB right, MSB left and  so  on.  The
971              track  should be a multiple of 2352 bytes. It is not possible to
972              put the master image of an audio track on  a  raw  disk  because
973              data will be read in multiple of 2352 bytes during the recording
974              process.
975
976              If a filename ends in .au or .wav the file is considered to be a
977              structured audio data file.  wodim assumes that the file in this
978              case is a Sun audio file or a Microsoft .WAV file  and  extracts
979              the  audio  data  from  the files by skipping over the non-audio
980              header information.  In all other cases, wodim  will  only  work
981              correctly  if  the  audio  data stream does not have any header.
982              Because many structured audio files do not have an integral num‐
983              ber  of  blocks (1/75th second) in length, it is often necessary
984              to specify the -pad option as well.  wodim recognizes that audio
985              data  in  a  .WAV  file  is stored in Intel (little-endian) byte
986              order, and will automatically  byte-swap  the  data  if  the  CD
987              recorder  requires big-endian data.  wodim will reject any audio
988              file that does not match the Red  Book  requirements  of  16-bit
989              stereo samples in PCM coding at 44100 samples/second.
990
991              Using other structured audio data formats as input to wodim will
992              usually work if the structure  of  the  data  is  the  structure
993              described  above  (raw pcm data in big-endian byte order).  How‐
994              ever, if the data format includes a  header,  you  will  hear  a
995              click at the start of a track.
996
997              If  neither -data nor -audio have been specified, wodim defaults
998              to -audio for all filenames that end in .au or .wav and to -data
999              for all other files.
1000
1001       -swab  If  this  flag  is present, audio data is assumed to be in byte-
1002              swapped (little-endian) order.  Some types  of  CD-Writers  e.g.
1003              Yamaha, Sony and the new SCSI-3/mmc drives require audio data to
1004              be presented in little-endian order, while other writers require
1005              audio  data  to  be  presented  in the big-endian (network) byte
1006              order normally used by the SCSI protocol.  wodim knows if a  CD-
1007              Recorder  needs  audio  data in big- or little-endian order, and
1008              corrects the byte order of the data stream to match the needs of
1009              the  recorder.  You only need the -swab flag if your data stream
1010              is in Intel (little-endian) byte order.
1011
1012              Note that the verbose output of wodim will show you if  swapping
1013              is  necessary  to  make the byte order of the input data fit the
1014              required byte order of the recorder.  wodim will not show you if
1015              the -swab flag was actually present for a track.
1016
1017       -data  If  this  flag  is present, all subsequent tracks are written in
1018              CD-ROM mode 1 (Yellow Book) format. The data size is a  multiple
1019              of  2048  bytes.   The  file  with  track data should contain an
1020              ISO-9660 or Rock Ridge filesystem  image  (see  genisoimage  for
1021              more  details).  If  the  track data is an ufs filesystem image,
1022              fragment size should be set to 2 KB or more to  allow  CD-drives
1023              with 2 KB sector size to be used for reading.
1024
1025              -data  is  the default, if no other flag is present and the file
1026              does not appear to be of one of the well known audio file types.
1027
1028              If neither -data nor -audio have been specified, wodim  defaults
1029              to -audio for all filenames that end in .au or .wav and to -data
1030              for all other files.
1031
1032       -mode2 If this flag is present, all subsequent tracks  are  written  in
1033              CD-ROM mode 2 format. The data size is a multiple of 2336 bytes.
1034
1035       -xa    If  this  flag  is present, all subsequent tracks are written in
1036              CD-ROM XA mode 2 form 1 format. The data size is a  multiple  of
1037              2048  bytes.   The  XA sector sub headers will be created by the
1038              drive.  With this option, the write mode is the same as with the
1039              -multi option.
1040
1041       -xa1   If  this  flag  is present, all subsequent tracks are written in
1042              CD-ROM XA mode 2 form 1 format. The data size is a  multiple  of
1043              2056 bytes.  The XA sector sub headers are part of the user data
1044              and have to be supplied by the  application  that  prepares  the
1045              data to be written.
1046
1047       -xa2   If  this  flag  is present, all subsequent tracks are written in
1048              CD-ROM XA mode 2 form 2 format. The data is a multiple  of  2324
1049              bytes.  The XA sector sub headers will be created by the drive.
1050
1051       -xamix If  this flag is present, all subsequent tracks are written in a
1052              way that allows a mix of CD-ROM XA mode 2 form 1/2  format.  The
1053              data  size is a multiple of 2332 bytes.  The XA sector sub head‐
1054              ers are part of the user data and have to  be  supplied  by  the
1055              application  that  prepares the data to be written.  The CRC and
1056              the P/Q parity ECC/EDC  information  (depending  on  the  sector
1057              type)  have  to be supplied by the application that prepares the
1058              data to be written.
1059
1060       -cdi   If this flag is present, the TOC type for the  disk  is  set  to
1061              CDI.  This only makes sense with XA disks.
1062
1063       -isosize
1064              Use the ISO-9660 file system size as the size of the next track.
1065              This option is needed if you want wodim  to  directly  read  the
1066              image  of a track from a raw disk partition or from a TAO master
1067              CD. In the first case the option -isosize is needed to limit the
1068              size of the CD to the size of the ISO filesystem.  In the second
1069              case the option -isosize is needed to prevent wodim from reading
1070              the  two run out blocks that are appended by each CD-recorder in
1071              track at once mode. These two run out blocks cannot be read  and
1072              would cause a buffer underrun that would cause a defective copy.
1073              Do not use this option on files created by  genisoimage  and  in
1074              case  wodim reads the track data from stdin.  In the first case,
1075              you would prevent wodim from writing the amount of padding  that
1076              has been appended by genisoimage and in the latter case, it will
1077              not work because stdin is not seekable.
1078
1079              If -isosize is used for a track, wodim  will  automatically  add
1080              padding  for  this track as if the -pad option has been used but
1081              the amount of padding may be less than the  padding  written  by
1082              genisoimage.  Note that if you use -isosize on a track that con‐
1083              tains Sparc boot information, the boot information will be lost.
1084
1085              Note also that this option cannot be used to determine the  size
1086              of a file system if the multi session option is present.
1087
1088       -pad   If  the track is a data track, 15 sectors of zeroed data will be
1089              added to the end of this and each  subsequent  data  track.   In
1090              this case, the -pad option is superseded by the padsize= option.
1091              It will remain however as a shorthand for padsize=15s.   If  the
1092              -pad  option  refers to an audio track, wodim will pad the audio
1093              data to be a multiple of 2352 bytes.  The audio data padding  is
1094              done with binary zeroes which is equal to absolute silence.
1095
1096              -pad remains valid until disabled by -nopad.
1097
1098       padsize=#
1099              Set  the  amount  of  data to be appended as padding to the next
1100              track to #.  Opposed to the behavior of  the  -pad  option,  the
1101              value  for  padsize= is reset to zero for each new track.  wodim
1102              assumes a sector size of 2048 bytes  for  the  padsize=  option,
1103              independent  from  the real sector size and independent from the
1104              write mode.  The megabytes mentioned in the verbose mode  output
1105              however  are  counting the output sector size which is e.g. 2448
1106              bytes when writing in RAW/RAW96 mode.  See fs= option for possi‐
1107              ble arguments.  To pad the equivalent of 20 minutes on a CD, you
1108              may write padsize=20x60x75s.  Use this option if  your  CD-drive
1109              is  not  able to read the last sectors of a track or if you want
1110              to be able to read the CD on a Linux system  with  the  ISO-9660
1111              filesystem  read  ahead bug.  If an empty file is used for track
1112              data, this option may be used to create a disk that is  entirely
1113              made  of  padding.   This  may e.g. be used to find out how much
1114              overburning is possible with a specific media.
1115
1116       -nopad Do not pad the following tracks - the default.
1117
1118       -shorttrack
1119              Allow all subsequent tracks to violate the Red Book track length
1120              standard  which  requires  a  minimum track length of 4 seconds.
1121              This option is only useful when used in SAO or  RAW  mode.   Not
1122              all  drives  support  this  feature.  The  drive must accept the
1123              resulting CUE sheet or support RAW writing.
1124
1125       -noshorttrack
1126              Re-enforce the Red Book track length standard. Tracks must be at
1127              least 4 seconds.
1128
1129       pregap=#
1130              Set the  pre-gap size for the next track.  This option currently
1131              only makes sense with the TEAC drive when creating track-at-once
1132              disks without the 2 second silence before each track.
1133              This option may go away in future.
1134
1135       -preemp
1136              If  this  flag  is present, all TOC entries for subsequent audio
1137              tracks will indicate that the audio data has been  sampled  with
1138              50/15  microsec pre-emphasis.  The data, however is not modified
1139              during the process of transferring  from  file  to  disk.   This
1140              option has no effect on data tracks.
1141
1142       -nopreemp
1143              If  this  flag  is present, all TOC entries for subsequent audio
1144              tracks will indicate that the audio data has been mastered  with
1145              linear data - this is the default.
1146
1147       -copy  If  this  flag  is present, all TOC entries for subsequent audio
1148              tracks of the resulting CD will indicate that the audio data has
1149              permission  to  be  copied  without  limit.   This option has no
1150              effect on data tracks.
1151
1152       -nocopy
1153              If this flag is present, all TOC entries  for  subsequent  audio
1154              tracks of the resulting CD will indicate that the audio data has
1155              permission to be copied only once for personal use - this is the
1156              default.
1157
1158       -scms  If  this  flag  is present, all TOC entries for subsequent audio
1159              tracks of the resulting CD will indicate that the audio data has
1160              no permission to be copied anymore.
1161
1162       tsize=#
1163              If  the master image for the next track has been stored on a raw
1164              disk, use this option to specify the valid  amount  of  data  on
1165              this disk. If the image of the next track is stored in a regular
1166              file, the size of that file is taken to determine the length  of
1167              this  track.  If the track contains an ISO 9660 filesystem image
1168              use the -isosize option to determine the length of that filesys‐
1169              tem image.
1170              In Disk at Once mode and with some drives that use the TEAC pro‐
1171              gramming interface, even in Track at Once mode, wodim  needs  to
1172              know  the  size of each track before starting to write the disk.
1173              wodim now checks this and aborts before starting to  write.   If
1174              this happens you will need to run genisoimage -print-size before
1175              and use the output (with `s' appended) as  an  argument  to  the
1176              tsize= option of wodim (e.g. tsize=250000s).
1177              See fs= option for possible arguments.
1178
1179

EXAMPLES

1181       For  all examples below, it will be assumed that the CD/DVD-Recorder is
1182       connected to the primary SCSI bus of the machine. The SCSI target id is
1183       set to 2.
1184
1185       To record a pure CD-ROM at double speed, using data from the file cdim‐
1186       age.raw:
1187
1188           wodim -v speed=2 dev=2,0 cdimage.raw
1189
1190       To create an image for a ISO 9660 filesystem  with  Rock  Ridge  exten‐
1191       sions:
1192
1193           genisoimage -R -o cdimage.raw /home/joerg/master/tree
1194
1195       To check the resulting file before writing to CD on Solaris:
1196
1197           mount -r -F fbk -o type=hsfs /dev/fbk0:cdimage.raw /mnt
1198
1199       On Linux:
1200
1201           mount cdimage.raw -r -t iso9660 -o loop /mnt
1202
1203       Go on with:
1204           ls -lR /mnt
1205           umount /mnt
1206
1207       If  the  overall speed of the system is sufficient and the structure of
1208       the filesystem is not too complex, wodim will run without  creating  an
1209       image of the ISO 9660 filesystem. Simply run the pipeline:
1210
1211           genisoimage -R /master/tree | wodim -v fs=6m speed=2 dev=2,0 -
1212
1213       The  recommended  minimum  FIFO  size  for  running  this pipeline is 4
1214       MBytes.  As the default FIFO size is 4 MB, the fs= option needs only be
1215       present  if  you  want to use a different FIFO size.  If your system is
1216       loaded, you should run genisoimage in the  real  time  class  too.   To
1217       raise the priority of genisoimage replace the command
1218
1219           genisoimage -R /master/tree
1220       by
1221           priocntl -e -c RT -p 59 genisoimage -R /master/tree
1222
1223       on Solaris and by
1224
1225           nice --18 genisoimage -R /master/tree
1226
1227       on  systems  that  don't  have  UNIX  International compliant real-time
1228       scheduling.
1229
1230       wodim runs at priority 59 on Solaris, you should run genisoimage at  no
1231       more  than priority 58. On other systems, you should run genisoimage at
1232       no less than nice --18.
1233
1234       Creating a CD-ROM without file system image on disk has been tested  on
1235       a  Sparcstation-2  with  a Yamaha CDR-400. It did work up to quad speed
1236       when the machine was not loaded.  A faster machine may be able to  han‐
1237       dle quad speed also in the loaded case.
1238
1239       To  record  a  pure CD-DA (audio) at single speed, with each track con‐
1240       tained in a file named track01.cdaudio, track02.cdaudio, etc:
1241
1242           wodim -v speed=1 dev=/dev/cdrw -audio track*.cdaudio
1243
1244       To check if it will be ok to use double speed for  the  example  above.
1245       Use the dummy write option:
1246
1247           wodim -v -dummy speed=2 dev=/dev/cdrw -audio track*.cdaudio
1248
1249       To  record a mixed-mode CD with an ISO 9660 filesystem from cdimage.raw
1250       on the first track, the other tracks being audio tracks from the  files
1251       track01.cdaudio, track02.cdaudio, etc:
1252
1253           wodim -v dev=2,0 cdimage.raw -audio track*.cdaudio
1254
1255       To  handle drives that need to know the size of a track before starting
1256       to write, first run
1257
1258           genisoimage -R -q -print-size /master/tree
1259
1260       and then run
1261
1262           genisoimage -R /master/tree | wodim speed=2 dev=2,0 tsize=XXXs -
1263
1264       where XXX is replaced by the output of the previous run of genisoimage.
1265
1266       To copy an audio CD in the most accurate way, first run
1267
1268           icedax dev=/dev/cdrom -vall cddb=0 -B -Owav
1269
1270       and then run
1271
1272           wodim dev=/dev/cdrw -v -dao -useinfo -text  *.wav
1273
1274       This will try to copy track indices and  to  read  CD-Text  information
1275       from  disk.  If there is no CD-Text information, icedax will try to get
1276       the information from freedb.org instead.
1277
1278       To copy an audio CD from a pipe (without intermediate files), first run
1279
1280           icedax dev=1,0 -vall cddb=0 -info-only
1281
1282       and then run
1283
1284           icedax dev=1,0 -no-infofile -B -Oraw - | \
1285           wodim dev=2,0 -v -dao -audio -useinfo -text *.inf
1286
1287       This will get all information (including  track  size  info)  from  the
1288       *.inf files and then read the audio data from stdin.
1289
1290       If  you like to write from stdin, make sure that wodim is called with a
1291       large enough FIFO size (e.g.  fs=128m), reduce the  write  speed  to  a
1292       value  below  the  read speed of the source drive (e.g.  speed=12), and
1293       get a CD/DVD drive with BURN-Free feature if it is not available yet.
1294
1295       To set drive options without writing a CD (e.g. to switch  a  drive  to
1296       single session mode), run
1297
1298           wodim dev=1,0 -setdropts driveropts=singlesession
1299
1300       If you like to do this when no CD is in the drive, call
1301
1302           wodim dev=1,0 -force -setdropts driveropts=singlesession
1303
1304       To copy a CD in clone mode, first read the master CD using:
1305
1306           readom dev=b,t,l -clone f=somefile
1307
1308       or  (in case the CD contains many sectors that are unreadable by inten‐
1309       tion) by calling:
1310
1311           readom dev=1,0 -clone -nocorr f=somefile
1312
1313       will create the files somefile and somefile.toc.   Then  write  the  CD
1314       using:
1315
1316           wodim dev=1,0 -raw96r -clone -v somefile
1317
1318
1319

ENVIRONMENT

1321       CDR_DEVICE
1322              This may either hold a device identifier that is suitable to the
1323              open call of the SCSI transport library or a label in  the  file
1324              /etc/wodim.conf.
1325
1326       CDR_SPEED
1327              Sets  the  default  speed  value  for  writing  (see also speed=
1328              option).
1329
1330       CDR_FIFOSIZE
1331              Sets the default size of the FIFO (see also fs=# option).
1332
1333       CDR_FORCERAWSPEED
1334              If this environment variable is set, wodim  will  allow  you  to
1335              write  at  the  full  RAW  encoding speed a single CPU supports.
1336              This will create high potential of buffer  underruns.  Use  with
1337              care.
1338
1339       CDR_FORCESPEED
1340              If  this  environment  variable  is set, wodim will allow you to
1341              write at the full DMA speed the system supports.   There  is  no
1342              DMA  reserve  for  reading  the  data that is to be written from
1343              disk.  This will create high potential of buffer underruns.  Use
1344              with care.
1345
1346       RSH    If  the  RSH  environment is present, the remote connection will
1347              not be created via rcmd(3) but by calling the program pointed to
1348              by  RSH.   Use  e.g.   RSH=/usr/bin/ssh to create a secure shell
1349              connection.
1350
1351              Note that this forces wodim to create a pipe to the rsh(1)  pro‐
1352              gram  and  disallows wodim to directly access the network socket
1353              to the remote server.  This makes it impossible to set  up  per‐
1354              formance  parameters and slows down the connection compared to a
1355              root initiated rcmd(3) connection.
1356
1357       RSCSI  If the RSCSI environment is present, the remote SCSI server will
1358              not  be  the  program  /opt/schily/sbin/rscsi  but  the  program
1359              pointed to by RSCSI.  Note that the remote SCSI  server  program
1360              name  will  be  ignored  if you log in using an account that has
1361              been created with a remote SCSI server program as login shell.
1362
1363

FILES

1365       /etc/wodim.conf
1366              Default  values  can  be  set  for  the  following  options   in
1367              /etc/wodim.conf.  For example: CDR_FIFOSIZE=8m or CDR_SPEED=2
1368
1369              CDR_DEVICE
1370                     This may either hold a device identifier that is suitable
1371                     to the open call of the SCSI transport library or a label
1372                     in  the  file  /etc/wodim.conf  that allows to identify a
1373                     specific drive on the system.
1374
1375              CDR_SPEED
1376                     Sets the default speed value for writing (see also speed=
1377                     option).
1378
1379              CDR_FIFOSIZE
1380                     Sets the default size of the FIFO (see also fs=# option).
1381
1382              CDR_MAXFIFOSIZE
1383                     Sets the maximum size of the FIFO (see also fs=# option).
1384
1385              Any other keyword (label) is an identifier (symbolic name) for a
1386              specific drive
1387                     on the system.  Such an identifier may  not  contain  the
1388                     characters ',', '/', '@' or ':'.
1389
1390                     Each line that follows a label contains a whitespace sep‐
1391                     arated list of items.  Currently, four items  are  recog‐
1392                     nized:  the  drive's  target  specification,  the default
1393                     speed that should be used for  this  drive,  the  default
1394                     FIFO  size  that  should be used for this drive and drive
1395                     specific options. The values for speed and  fifosize  may
1396                     be  set  to  -1 to tell wodim to use the global defaults.
1397                     target can be -1 to use the auto-guessing  of  the  drive
1398                     (see above).
1399
1400                     The  value  for driveropts may be omitted or set to "" if
1401                     no driveropts are used.  A typical  line  may  look  this
1402                     way:
1403
1404                     plex760= 0,5,0 12   50m  varirec=1
1405
1406                     pioneer= /dev/hdd   -1   -1
1407
1408                     This tells wodim that a drive named plex760 is at scsibus
1409                     0, target 5, lun 0 and should be used with speed 12 and a
1410                     FIFO  size  of  50  MB. It also uses some device specific
1411                     parameter.  A second drive  may  is  accessible  via  the
1412                     device  file  /dev/hdd and uses the default speed and the
1413                     default FIFO size.
1414
1415

SEE ALSO

1417       icedax(1), readom(1), genisoimage(1), ssh(1).
1418
1419

NOTES

1421       On Solaris you need to stop the volume management if you  like  to  use
1422       the USCSI fallback SCSI transport code. Even things like wodim -scanbus
1423       will not work if the volume management is running.
1424
1425       Disks made in Track At Once mode are  not  suitable  as  a  master  for
1426       direct  mass production by CD manufacturers.  You will need the disk at
1427       once option to record such disks.  Nevertheless the disks made in Track
1428       At  Once  will  normally  be  read in all CD players. Some old audio CD
1429       players however may produce  a  two  second  click  between  two  audio
1430       tracks.
1431
1432       The  minimal  size of a track is 4 seconds or 300 sectors. If you write
1433       smaller tracks, the CD-Recorder will add dummy blocks. This is  not  an
1434       error, even though the SCSI-error message looks this way.
1435
1436       The  Yamaha  CDR-400  and all new SCSI-3/mmc conforming drives are sup‐
1437       ported in single and multi-session.
1438
1439       You should run several tests in all supported speeds of your drive with
1440       the  -dummy  option turned on if you are using wodim on an unknown sys‐
1441       tem. Writing a CD is a real-time process.  NFS, CIFS and other  network
1442       file systems won't always deliver constantly the needed data rates.  If
1443       you want to use wodim with CD-images that are located on a NFS  mounted
1444       filesystem,  be  sure that the FIFO size is big enough.  If you want to
1445       make sure that buffer underruns are not caused by your source disk, you
1446       may use the command
1447
1448           wodim -dummy dev=2,0 padsize=600m /dev/null
1449
1450       to create a disk that is entirely made of dummy data.
1451
1452       There  are also cases where you either need to be root or install wodim
1453       executable with suid-root permissions. First, if you are using a device
1454       manufactured  before  1999  which requires a non-MMC driver, you should
1455       run wodim in dummy mode before writing data.  If  you  find  a  problem
1456       doing this, please report it to the cdrkit maintainers (see below).
1457
1458       Second,  certain  functionality may be unusable because of Linux's SCSI
1459       command filtering. When using wodim for anything except  of  pure  data
1460       writing,  you  should  also  test  the process in dummy mode and report
1461       trouble to the contact address below.
1462
1463       If you still want to run wodim with root permissions, you can  set  the
1464       permissions of the executable to suid-root. See the additional notes of
1465       your system/program distribution or README.suidroot which  is  part  of
1466       the cdrkit source.
1467
1468       You should not connect old drives that do not support disconnect/recon‐
1469       nect to either the SCSI bus that is connected to the CD-Recorder or the
1470       source disk.
1471
1472       A Compact Disc can have no more than 99 tracks.
1473
1474       When  creating  a disc with both audio and data tracks, the data should
1475       be on track 1 otherwise you should create a  CDplus  disk  which  is  a
1476       multi  session  disk with the first session containing the audio tracks
1477       and the following session containing the data track.
1478
1479       Many operating systems are not able to read more  than  a  single  data
1480       track, or need special software to do so.
1481
1482       If  you  have  more  information  or SCSI command manuals for currently
1483       unsupported CD/DVD/BR/HD-DVD-Recorders, please contact the cdrkit main‐
1484       tainers (see below).
1485
1486       Many CD recorders have bugs and often require a firmware update to work
1487       correctly. If  you  experience  problems  which  cannot  be  solved  or
1488       explained by the notes above, please look for instructions on the home‐
1489       page of the particular manufacturer.
1490
1491       Some bugs will force you to power cycle the device  or  to  reboot  the
1492       machine.
1493
1494       The FIFO percent output is computed just after a block of data has been
1495       written to the CD/DVD-Recorder. For this reason, there  will  never  be
1496       100% FIFO fill ratio while the FIFO is in streaming mode.
1497
1498

DIAGNOSTICS

1500       You have 4 seconds to abort wodim start after you see the message:
1501
1502       Starting  to  write  CD at speed %d in %s mode for %s session.  In most
1503       shells you can do that by pressing Ctrl-C.
1504
1505       A typical error message for a SCSI command looks like:
1506
1507              wodim: I/O error. test unit ready: scsi sendcmd: no error
1508              CDB:  00 20 00 00 00 00
1509              status: 0x2 (CHECK CONDITION)
1510              Sense Bytes: 70 00 05 00 00 00 00 0A 00 00 00 00 25 00 00 00 00 00
1511              Sense Key: 0x5 Illegal Request, Segment 0
1512              Sense Code: 0x25 Qual 0x00 (logical unit not supported) Fru 0x0
1513              Sense flags: Blk 0 (not valid)
1514              cmd finished after 0.002s timeout 40s
1515
1516       The first line gives information about the transport  of  the  command.
1517       The text after the first colon gives the error text for the system call
1518       from the view of the kernel. It usually  is:  I/O  error  unless  other
1519       problems  happen.  The  next  words contain a short description for the
1520       SCSI command that fails. The rest of the line tells you if  there  were
1521       any problems for the transport of the command over the SCSI bus.  fatal
1522       error means that it was not possible to transport the command (i.e.  no
1523       device present at the requested SCSI address).
1524
1525       The second line prints the SCSI command descriptor block for the failed
1526       command.
1527
1528       The third line gives information on the SCSI status  code  returned  by
1529       the  command,  if the transport of the command succeeds.  This is error
1530       information from the SCSI device.
1531
1532       The fourth line is a hex dump of the auto request sense information for
1533       the command.
1534
1535       The  fifth  line is the error text for the sense key if available, fol‐
1536       lowed by the segment number that is only valid if  the  command  was  a
1537       copy  command. If the error message is not directly related to the cur‐
1538       rent command, the text deferred error is appended.
1539
1540       The sixth line is the error text for the sense code and the sense qual‐
1541       ifier if available.  If the type of the device is known, the sense data
1542       is decoded from tables in scsierrs.c .  The text  is  followed  by  the
1543       error value for a field replaceable unit.
1544
1545       The  seventh line prints the block number that is related to the failed
1546       command and text for several error flags. The block number may  not  be
1547       valid.
1548
1549       The eight line reports the timeout set up for this command and the time
1550       that the command really needed to complete.
1551
1552       The following message is not an error:
1553
1554              Track 01: Total bytes read/written: 2048/2048 (1 sectors).
1555              wodim: I/O error. flush cache: scsi sendcmd: no error
1556              CDB:  35 00 00 00 00 00 00 00 00 00
1557              status: 0x2 (CHECK CONDITION)
1558              Sense Bytes: F0 00 05 80 00 00 27 0A 00 00 00 00 B5 00 00 00 00 00
1559              Sense Key: 0x5 Illegal Request, Segment 0
1560              Sense Code: 0xB5 Qual 0x00 (dummy data blocks added) Fru 0x0
1561              Sense flags: Blk -2147483609 (valid)
1562              cmd finished after 0.002s timeout 40s
1563
1564       It simply notifies, that a track that is smaller than the minimum  size
1565       has been expanded to 300 sectors.
1566

BUGS

1568       netscsid  does  not  work properly and is generally unmaintained. It is
1569       probably not compatible with rscsi from cdrtools either. Good  bugfixes
1570       are welcome, talk to Cdrkit maintainers.
1571
1572       cuefile  support  is very limited, only one file is allowed. For volun‐
1573       teers, see TODO file in the source.
1574
1575       Specifying an audio file multiple times causes corruption of the second
1576       track (effectively no data plus minimum padding).
1577
1578       Some  of the bugs may be fixed in Joerg Schilling's cdrtools. See there
1579       for details, URL attached below.
1580
1581

CREDITS

1583       Joerg Schilling (schilling@fokus.fhg.de)
1584                      For writing cdrecord and libscg which represent the most
1585                      parts of wodim's code.
1586
1587       Bill Swartz    (Bill_Swartz@twolf.com)
1588                      For helping me with the TEAC driver support
1589
1590       Aaron Newsome  (aaron.d.newsome@wdc.com)
1591                      For letting me develop Sony support on his drive
1592
1593       Eric Youngdale (eric@andante.jic.com)
1594                      For supplying mkisofs
1595
1596       Gadi Oxman     (gadio@netvision.net.il)
1597                      For tips on the ATAPI standard
1598
1599       Finn Arne Gangstad  (finnag@guardian.no)
1600                      For the first FIFO implementation.
1601
1602       Dave Platt     (dplatt@feghoot.ml.org)
1603                      For  creating  the  experimental packet writing support,
1604                      the first implementation of CD-RW blanking support,  the
1605                      first  .wav  file  decoder  and many nice discussions on
1606                      cdrecord.
1607
1608       Chris P. Ross (cross@eng.us.uu.net)
1609                      For the first implementation of a BSDI SCSI transport.
1610
1611       Grant R. Guenther   (grant@torque.net)
1612                      For creating the first parallel port transport implemen‐
1613                      tation for Linux.
1614
1615       Kenneth D. Merry (ken@kdm.org)
1616                      for  providing  the  CAM  port for FreeBSD together with
1617                      Michael Smith (msmith@freebsd.org)
1618
1619       Heiko Eiszfeldt (heiko@hexco.de)
1620                      for making libedc_ecc available  (needed  to  write  RAW
1621                      data sectors).
1622
1623

MAILING LISTS

1625       If  you want to actively take part on the development of wodim, you may
1626       join the developer mailing list via this URL:
1627
1628       https://alioth.debian.org/mail/?group_id=31006
1629
1630       The mail address of the list is: debburn-devel@lists.alioth.debian.org
1631
1632

AUTHORS

1634       wodim is currently maintained as part of  the  cdrkit  project  by  its
1635       developers.  Most of the code and this manual page was originally writ‐
1636       ten by:
1637
1638       Joerg Schilling
1639       Seestr. 110
1640       D-13353 Berlin
1641       Germany
1642
1643       This application is derived from "cdrecord" as included in the cdrtools
1644       package [1] created by Joerg Schilling, who deserves most of the credit
1645       for its success. However, he is not involved into  the  development  of
1646       this  spinoff  and  therefore  he shall not be held responsible for any
1647       problems caused by it. Do not refer to this application as  "cdrecord",
1648       do not try to get support for wodim by contacting the original authors.
1649
1650       Additional information can be found on:
1651       https://alioth.debian.org/projects/debburn/
1652
1653       If you have support questions, send them to
1654
1655       debburn-devel@lists.alioth.debian.org
1656
1657       If you have definitely found a bug, send a mail to this list or to
1658
1659       submit@bugs.debian.org
1660
1661       writing  at  least  a  short description into the Subject and "Package:
1662       cdrkit" in the first line of the mail body.
1663

SOURCES

1665       [1] Cdrtools 2.01.01a08 from May 2006, http://cdrecord.berlios.de
1666
1667
1668
1669
1670                                  Version 2.0                         wodim(1)
Impressum