Showing results 1 to 7 of 7

Thread: iso bin blindwrite

  1. #1

    Default iso bin blindwrite

    I used blindwrite to make some CD backup and tried several options (such as bin and iso formats)
    what sorted out of these tries is that bin format don't keep tracks of protection and ISO does
    the problem is that the ISO format don't seems to be a ISO one : I use linux too and It can't mount those iso.... so I wonder If somoene could give me information about this format? it seems to be some special iso9660 mode...

    daemon loads those image perfectly : can you give me some information (do you use special handlers?)


  2. #2


    I believe iso files can have both 2048 and 2352 block sizes. Maybe linux will only mount 2048 (or vice versa)? If you look at first few bytes of your iso, you will see a bunch of FF's if it is 2352.

  3. #3


    after looking in the file using a hex editor I noticed that BWI/ISO file generated by blindwrite got a APPLE PARTITION TABLE :shock: and an apple partition in HPFS.....
    Is it normal? don't know really about ISO9660 format but I try to find why loopback devices (equivalent of daemon-tools under linux) fail to load the image correctly while CDrtools can burn such image and mount them afterwards....
    loopbacks devices only mount partitions, not raw disks image (ie with a partition inside)

  4. #4


    sorry HFS (not hpfs)

  5. #5


    how does daemon deals with this?
    can a seek to corresponding HFS partition can do the thing?

  6. #6


    Windows is responsible for parsing various partitions. Cdroms (and dtools) only send raw data to windows.

  7. #7


    ok thanks.....
    this don't solve my problem but it helped me a bit


Posting Rules

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts