cdrecord.man

刻录光盘的程序

CDRECORD(1)          Schily's USER COMMANDS           CDRECORD(1)



     to create a disk  that  is  entirely  made  of  dummy  data.
     CCCCddddrrrreeeeccccoooorrrrdddd needs to run as root to get access to the ////ddddeeeevvvv////ssssccccgggg????
     device nodes and to be able to lock itself into memory.

     If you don't want to allow users to become root on your sys-
     tem, ccccddddrrrreeeeccccoooorrrrdddd may safely be installed suid root. This allows
     all users or a group of users with no root privileges to use
     ccccddddrrrreeeeccccoooorrrrdddd....  CCCCddddrrrreeeeccccoooorrrrdddd  in  this  case checks, if the real user
     would have been able to read the specified files.   To  give
     all user access to use ccccddddrrrreeeeccccoooorrrrdddd,,,, enter:

          chown root /usr/local/bin/cdrecord
          chmod 4711 /usr/local/bin/cdrecord

     To give a restricted  group  of  users  access  to  cdrecord
     enter:

          chown root /usr/local/bin/cdrecord
          chgrp cdburners /usr/local/bin/cdrecord
          chmod 4710 /usr/local/bin/cdrecord

     and add a group _c_d_b_u_r_n_e_r_s on your system.

     Never give write permissions  for  non  root  users  to  the
     /_d_e_v/_s_c_g?   devices   unless  you  would  allow  anybody  to
     read/write/format all your disks.

     You should not  connect  old  drives  that  do  not  support
     disconnect/reconnect  to  either  the  SCSI bus that is con-
     nected to the CD-Recorder or the source disk.

     A Compact Disc can have no more than 99 tracks.

     When creating a disc with both audio and  data  tracks,  the
     data  should  be  on  track  1 otherwise you should create a
     CDplus disk which is a multi session  disk  with  the  first
     session  containing  the audio tracks and the following ses-
     sion containing the data track.

     Many operating systems are not able to read more than a sin-
     gle data track, or need special software to do so.

     More information on the SCSI command set of a HP CD-Recorder
     can be found at:

          http://www.hp.com/isgsupport/cdr/index.html

     If you have more information or  SCSI  command  manuals  for
     currently   unsupported   CD-Recorders  please  contact  the
     author.





Joerg Schilling     Last change: Version 1.8                   16






CDRECORD(1)          Schily's USER COMMANDS           CDRECORD(1)



     The Philips CDD 521 CD-Recorder (even in the  upgraded  ver-
     sion) has several firmware bugs. Some of them will force you
     to power cycle the device or to reboot the machine.

     When using ccccddddrrrreeeeccccoooorrrrdddd  with  the  broken  LLLLiiiinnnnuuuuxxxx  SSSSCCCCSSSSIIII  ggggeeeennnneeeerrrriiiicccc
     ddddrrrriiiivvvveeeerrrr....  You  should  note  that  ccccddddrrrreeeeccccoooorrrrdddd uses a hack, that
     tries to  emulate  the  functionality  of  the  scg  driver.
     Unfortunately,  the  sg  driver  on LLLLiiiinnnnuuuuxxxx has several severe
     bugs:

     +o     It cannot see if a SCSI command could not be  sent  at
          all.

     +o     It cannot get the SCSI status byte. CCCCddddrrrreeeeccccoooorrrrdddd for  that
          reason  cannot  report  failing  SCSI  commands in some
          situations.

     +o     It cannot get real DMA  count  of  transfer.  CCCCddddrrrreeeeccccoooorrrrdddd
          cannot tell you if there is an DMA residual count.

     +o     It cannot get number of  bytes  valid  in  auto  sense
          data.   CCCCddddrrrreeeeccccoooorrrrdddd cannot tell you if device transfers no
          sense data at all.

      +o     It  fetches  to  few  data  in  auto  request   sense
          (CCS/SCSI-2/SCSI-3 needs >= 18).

     The fifo percent output is computed just after  a  block  of
     data  has  been written to the CD-Recorder. For this reason,
     there will never be 100% fifo fill, while  the  fifo  is  in
     streaming mode.


DDDDIIIIAAAAGGGGNNNNOOOOSSSSTTTTIIIICCCCSSSS
     You have 9 seconds to type ^C to abort  ccccddddrrrreeeeccccoooorrrrdddd  after  you
     see the message:

     Starting to write CD at speed %d in %s mode for %s session.

     A typical error message for a SCSI command looks like:

          cdrecord: I/O error. test unit ready: scsi sendcmd: no error
          CDB:  00 20 00 00 00 00
          status: 0x2 (CHECK CONDITION)
          Sense Bytes: 70 00 05 00 00 00 00 0A 00 00 00 00 25 00 00 00 00 00
          Sense Key: 0x5 Illegal Request, Segment 0
          Sense Code: 0x25 Qual 0x00 (logical unit not supported) Fru 0x0
          Sense flags: Blk 0 (not valid)

     The first line gives information about the transport of  the
     command.   The  text  after  the first colon gives the error
     text for the system call from the view  of  the  kernel.  It



Joerg Schilling     Last change: Version 1.8                   17






CDRECORD(1)          Schily's USER COMMANDS           CDRECORD(1)



     usually  is:   IIII////OOOO  eeeerrrrrrrroooorrrr  unless other problems happen. The
     next words contain a short description for the SCSI  command
     that fails. The rest of the line tells you if there were any
     problems for the transport of the command over the SCSI bus.
     ffffaaaattttaaaallll  eeeerrrrrrrroooorrrr means that it was not possible to transport the
     command (i.e.  no  device  present  at  the  requested  SCSI
     address).

     The second line prints the SCSI command descriptor block for
     the failed command.

     The third line gives information on  the  SCSI  status  code
     returned  by  the  command,  if the transport of the command
     succeeds. This is error information from the SCSI device.

     The fourth line is a hex dump  of  the  auto  request  sense
     information for the command.

     The fifth line is the error text for the sense key if avail-
     able,  followed  by the segment number that is only valid if
     the command was a _c_o_p_y command. If the error message is  not
     directly  related  to the current command, the text _d_e_f_e_r_r_e_d
     _e_r_r_o_r is appended.

     The sixth line is the error text for the sense code and  the
     sense  qualifier if available.  If the type of the device is
     known, the sense data is decoded from tables in _s_c_s_i_e_r_r_s._c .
     The text is followed by the error value for a field replace-
     able unit.

     The seventh line prints the block number that is related  to
     the  failed  command  and  text for several error flags. The
     block number may not be valid.

     The following message is not an error:
          Track 01: Total bytes read/written: 2048/2048 (1 sectors).
          cdrecord: I/O error. flush cache: scsi sendcmd: no error
          CDB:  35 00 00 00 00 00 00 00 00 00
          status: 0x2 (CHECK CONDITION)
          Sense Bytes: F0 00 05 80 00 00 27 0A 00 00 00 00 B5 00 00 00 00 00
          Sense Key: 0x5 Illegal Request, Segment 0
          Sense Code: 0xB5 Qual 0x00 (dummy data blocks added) Fru 0x0
          Sense flags: Blk -2147483609 (valid)

     It simply notifies, that a track that is  smaller  than  the
     minimum size has been expanded to 300 sectors.

BBBBUUUUGGGGSSSS
     CCCCddddrrrreeeeccccoooorrrrdddd has even more options than llllssss.

     CCCCddddrrrreeeeccccoooorrrrdddd currently only warns if the input data will not fit
     on  the  disk.   If you don't abort the command you will get



Joerg Schilling     Last change: Version 1.8                   18






CDRECORD(1)          Schily's USER COMMANDS           CDRECORD(1)



     unpredictable results.

     There should be an option to write index numbers  for  audio
     tracks.

     There should be a recover option to make disks usable,  that
     have been written during a power failure.


CCCCRRRREEEEDDDDIIIITTTTSSSS
     Bill Swartz    ([e-mail])
                    For helping me with the TEAC driver support

     Aaron Newsome  ([e-mail])
                    For letting me develop Sony  support  on  his
                    drive

     Eric Youngdale ([e-mail])
                    For supplying mkisofs

     Gadi Oxman     ([e-mail])
                    For tips on the ATAPI standard

     Finn Arne Gangstad  ([e-mail])
                    For the first FIFO implementation.

     Dave Platt     ([e-mail])
                    For creating the experimental packet  writing
                    support,  the  first  implementation of CD-RW
                    blanking support, the first .wav file decoder
                    and many nice discussions on cdrecord.

     Chris P. Ross ([e-mail])
                    For the first implementation os a  BSDI  SCSI
                    rtansport.

     Grant R. Guenther   ([e-mail])
                    For creating the first  parallel  port  tran-
                    sport implementation for Linux.

     Kenneth D. Merry ([e-mail])
                    for  providing  the  CAM  port  for   FreeBSD
                    together       with       Michael       Smith
                    ([e-mail])


MMMMAAAAIIIILLLLIIIINNNNGGGG LLLLIIIISSSSTTTTSSSS
     If you want to actively take  part  on  the  development  of
     cdrecord, you may join the cdwriting mailing list by sending
     mail to:

          [e-mail]



Joerg Schilling     Last change: Version 1.8                   19






CDRECORD(1)          Schily's USER COMMANDS           CDRECORD(1)



     and include the  word  _s_u_b_s_c_r_i_b_e  in  the  body.   The  mail
     address of the list is:

          [e-mail]


AAAAUUUUTTTTHHHHOOOORRRR
     Joerg Schilling
     Seestr. 110
     D-13353 Berlin
     Germany

     Additional information can be found on:
     http://www.fokus.gmd.de/nthp/employees/schilling/cdrecord.html

     Mail bugs and suggestions to:

     jjjjooooeeeerrrrgggg@@@@sssscccchhhhiiiillllyyyy....iiiissssddddnnnn....ccccssss....ttttuuuu----bbbbeeeerrrrlllliiiinnnn....ddddeeee or  jjjjssss@@@@ccccssss....ttttuuuu----bbbbeeeerrrrlllliiiinnnn....ddddeeee  or
     sssscccchhhhiiiilllllllliiiinnnngggg@@@@ffffooookkkkuuuussss....ggggmmmmdddd....ddddeeee




































Joerg Schilling     Last change: Version 1.8                   20