Showing results 1 to 10 of 16

Thread: Support for isobuster CUE format

Hybrid View

Previous Post Previous Post   Next Post Next Post
  1. #1
    New User
    Join Date

    Default Support for isobuster CUE format

    it would be nice to add support for new directives in isobuster CUE files like SESSION directive.
    currently there is no way to mount multisession images that dumped by isobuster.


  2. #2

    Default CUE/BIN format

    Is there some sort of formal specification or documentation for the CUE/BIN format, or just the CUE format?

    Why is ISOBuster doing this? Is it a custom modification to the format?
    the modern world:
    net helpmsg 4006

  3. #3
    New User
    Join Date

    Default CUE format

    isobuster creates a standard CUE file for every image that it dumps. isobuster adds some extra directives to the CUE file when it dumps multisession disks, Here is an example of CUE file contents that created for a multisession disk with 2 sessions :

    FILE "CD.bin" BINARY


    REM SESSION 01 ; Not supported by other applications (*)
    TRACK 01 MODE2/2352
    INDEX 01 00:00:00
    REM MSF: 00:00:00 = LBA: 0
    TRACK 02 MODE2/2352
    INDEX 00 00:04:00
    REM MSF: 00:04:00 = LBA: 300
    INDEX 01 00:06:02
    REM MSF: 00:06:02 = LBA: 300

    REM RUN-OUT 00:10:02 ; Not supported by other applications (*)
    REM LEAD-OUT 00:10:04 ; Not supported by other applications (*)
    REM SESSION 02 ; Not supported by other applications (*)
    TRACK 03 MODE1/2352
    INDEX 01 02:42:04
    REM MSF: 02:42:04 = LBA: 12154

    REM (*) SESSION directives are unfortunately not properly supported
    REM 'out there'. IsoBuster however supports them !

  4. #4


    IOW, yeah, ISOBuster *IS* creating a custom modification of the format. I wonder if it is to make the .CUEs proprietary, or if it actually contains legitimate info that other programs do not actually find?

    Oh, and Happy Helloween all!!!

  5. #5


    what i remember, word REM was used in a *.bat for marking comments/notes of author....REM=REMARK and what is behind this word is only information for isobuster. So u can delete these lines. But its only my opinion.

  6. #6
    New User
    Join Date


    ISOBuster puts REM to keep its *.CUE files compatible with other applications but ISOBuster use the keywords behind REMs.
    other applications like DT already can use ISOBuster *.CUE files but ignore the words behind REM and just can see tracks contained in the coresponding image nor sessions, ISOBuster can see and use sessions also (with the help of these new directives) .


Posting Rules

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