Menu

iso image burning

A Zajac
2003-07-18
2003-07-24
  • A Zajac

    A Zajac - 2003-07-18

    The latest version of Eroaster is looking pretty good!  Thanks to the developpers for such good software!

    When I burn an iso image to cd with eroaster, I would like to be able to burn in in DAO (SAO, really) since cdrecord does funny things with my burner in TAO.  For example, when I try to make an on-the-fly copy of the cd I just burned from an iso image, I get and read error and Eroaster just lets the burn go on forever...  In GCDMaster, it stops (ends, actually) and warns me of a L-EC error.
    The problem with DAO from cdrecord is that you are required to feed it the size or something (with mkisofs) beforehand.  I learned this by reading the cdrecord man pages.
    To make a copy in DOA I had to (gasp!) install K3B.  I can't wait to free up 60 megs of disk space and remove k3b.  Any chance of including DAO for data cds?
    Also, is there a way to avoid the neverending burn that happens when there is a read-error during on-the-fly burning?

    Thank!

    AZ.

     
    • Martin Preishuber

      The next version will include the possibility to burn cue/bin images with cdrdao. However it will not include burning data CDs with cdrdao yet ... that includes on the fly copying with cdrdao unfortunately :(

       
    • A Zajac

      A Zajac - 2003-07-24

      Reading from the cdrecord man pages: 
        -isosize is needed to prevent cdrecord from reading the two run out blocks that are appended by each CD-recorder in Track-At-Once mode.  These two run out blocks cannot be read and would cause a buffer under run that would cause a defective copy.

      also:  -dao ... cdrecord needs to know the size of each track in advance for this mode (see the mkisofs -print-size option and the Examples section...

      mkisofs -R -q -print-size /master/tree

      mkisofs -R /master/tree | cdrecord speed=2 dev=2,0 tsize=XXXs -

      As it is, eroaster can only burn defective copies of iso images for me.  So I am stuck with K3B.
      If I were able to include a command line argument to include the tsize, I would be able to avoid this problem...  Any chance of including that in the next version?  Or even checking the iso image size and including that in the command line?  It shouldn't affect those whose burners do not add thtose annoying run out blocks at the end of a track...

      Also, any way for readcd to hot get hung up foreverandever if there is a buffer-underrun?

      AZ

       
    • Martin Preishuber

      I never heard of those run out blocks before ... Looks like my recorders (2 SCSI on ISA) don't do that ... I'll look at that soon.

       

Log in to post a comment.

MongoDB Logo MongoDB