Please post the content of the cue sheet (should be a plain textfile).

I have the same problem, also using IsoBuster 2.5, and getting the same error messages.

This is the generated cue-sheet:

1FILE "CD.bin" BINARY
2
3REM ORIGINAL MEDIA-TYPE: CD
4
5  REM SESSION 01        ; Not supported by other applications (*)
6    TRACK 01 MODE2/2352
7      INDEX 01 00:00:00
8      REM MSF: 00:00:00 = LBA: 0
9
10REM (*) SESSION directives are unfortunately not properly supported
11REM     'out there'.  IsoBuster however supports them !

I did try to remove all the REM garbage but that made no difference.

I don't like ISOBuster. Usually creates more problems than it solves.

You could try to remove all "non-standard info" from the CUE. MiniMax' example would then look like this:

1FILE "CD.bin" BINARY
2    TRACK 01 MODE2/2352
3      INDEX 01 00:00:00

The "MODE2" entry is odd, too. I think it should say "MODE1".

In general, i'd recommend creating BIN/CUE images with CDRWin or CloneCD. CDRWin is kind of the de-facto standard for creating BIN/CUE images, and works very well for me. CloneCD creates "normal" BIN images, and can optionally create a CUE, too. The CCD file is not needed in most cases.

Indeed - changing it to MODE1 allowed me to imgmount the CUE-file and execute the installer from the BIN-image.

So who is it blame? DOSBox or IsoBuster?

Edit: Hmmm.... Did I choose the wrong option when extracting? Should I have gone for this User Data thingy??

http://www.isobuster.com/help.php?popup=1&help=590
http://www.isobuster.com/help.php?popup=1&help=610

try changing the mode2 to mode1

Old thread here - same problem, same cure:

Mechwarrior 2 and DosBox 0.70

according to our code the CD001 marker is at a different place when in MODE2.
however isobuster sets it at the same place as it is in MODE1.
I don't know who is right though

Minimax could you try a different program (one that generates a MODE1 version of it) and see if the bin files are the same ?
Might shine some light on whether it is really a mode1 or a mode2 image

according to our code the CD001 marker is at a different place when in MODE2

You mean because we have some offsets in CDROM_Interface_Image::ReadSector() ?
Maybe the offset correction should be disabled if reading the start of the cd,
as that part seems to be identical over mode1/mode2.

I was referring to the canreadPVD function, which is used to autodetect isos. Didn't check other functions which might be used with isos

CanReadPVD uses (should use, didn't check exactly) the same code as
ReadSector, just simplified. Anyways i didn't see that the offsets are byte
offsets for seek rather than sector offsets.

Supposedly ImgBurn can create .CUE files.

Good thing about ImgBurn is that it's easy to use and it works in 9x and NT4 and it's updated often.

> Minimax could you try a different program

Will try. Any recommendations? ImgBurn?

Thanks for the replies, I'll try that out also when I get home from work and report back.

Is this problem reproducable with other cds, like audio-only ones or data-only? If so, how exactly?

Qbix wrote:

according to our code the CD001 marker is at a different place when in MODE2. however isobuster sets it at the same place as it […]
Show full quote

according to our code the CD001 marker is at a different place when in MODE2.
however isobuster sets it at the same place as it is in MODE1.
I don't know who is right though

Minimax could you try a different program (one that generates a MODE1 version of it) and see if the bin files are the same ?
Might shine some light on whether it is really a mode1 or a mode2 image

I might need some hand-holding here. I downloaded and installed ImgBurn. I have no problem creating images (tried both my Magic Carpet CD - nice and small, and the Apocalypse CD), but I am not able to create a CUE-file with ImgBurn. I can get into the CUE-screen, but the OK button is always greyed out. All I can do is hit Cancel.

Please see my question, if i can reproduce it with IsoBuster i can set up some test samples.

Okay... I am not able to create a CUE-file with ImgBurn if I use the physical CD as the source, but if I select the ISO-image I just created from the Apoc CD, then I can do it:

1FILE "XCOM APOC.ISO" BINARY
2  TRACK 01 MODE1/2048
3    INDEX 01 00:00:00

wd wrote:

Is this problem reproducable with other cds, like audio-only ones or data-only? If so, how exactly?

I don't know. I am not even sure what the problem is.

Here are the results from creating CUE-files from an audio-CD using IsoBuster and ImgBurn:

IsoBuster:

1FILE "CD.bin" BINARY
2
3REM ORIGINAL MEDIA-TYPE: CD
4
5  REM SESSION 01        ; Not supported by other applications (*)
6    TRACK 01 AUDIO
7      INDEX 01 00:00:00
8      REM MSF: 00:00:00 = LBA: 0
9    TRACK 02 AUDIO
10      INDEX 01 03:47:62
11      REM MSF: 03:47:62 = LBA: 17087
12    TRACK 03 AUDIO
13      INDEX 01 06:49:67
14      REM MSF: 06:49:67 = LBA: 30742
15    TRACK 04 AUDIO
16      INDEX 01 10:26:40
17      REM MSF: 10:26:40 = LBA: 46990
18    TRACK 05 AUDIO
19      INDEX 01 11:18:52
20      REM MSF: 11:18:52 = LBA: 50902
21    TRACK 06 AUDIO
22      INDEX 01 14:41:52
23      REM MSF: 14:41:52 = LBA: 66127
24    TRACK 07 AUDIO
25      INDEX 01 16:46:47
26      REM MSF: 16:46:47 = LBA: 75497
27    TRACK 08 AUDIO
28      INDEX 01 19:57:50
29      REM MSF: 19:57:50 = LBA: 89825
30    TRACK 09 AUDIO
31      INDEX 01 23:04:07
32      REM MSF: 23:04:07 = LBA: 103807
33    TRACK 10 AUDIO
34      INDEX 01 27:01:55
35      REM MSF: 27:01:55 = LBA: 121630
36    TRACK 11 AUDIO
37      INDEX 01 30:45:62
38      REM MSF: 30:45:62 = LBA: 138437
39
40REM (*) SESSION directives are unfortunately not properly supported
41REM     'out there'.  IsoBuster however supports them !

ImgBurn:

1FILE "Image.bin" BINARY
2  TRACK 01 AUDIO
3    INDEX 01 00:00:00
4  TRACK 02 AUDIO
5    INDEX 00 03:46:47
6    INDEX 01 03:47:62
7  TRACK 03 AUDIO
8    INDEX 00 06:48:27
9    INDEX 01 06:49:67
10  TRACK 04 AUDIO
11    INDEX 00 10:25:22
12    INDEX 01 10:26:40
13  TRACK 05 AUDIO
14    INDEX 01 11:18:52
15  TRACK 06 AUDIO
16    INDEX 00 14:39:52
17    INDEX 01 14:41:52
18  TRACK 07 AUDIO
19    INDEX 00 16:45:37
20    INDEX 01 16:46:47
21  TRACK 08 AUDIO
22    INDEX 00 19:56:50
23    INDEX 01 19:57:50
24  TRACK 09 AUDIO
25    INDEX 01 23:04:07
26  TRACK 10 AUDIO
27    INDEX 01 27:01:55
28  TRACK 11 AUDIO
29    INDEX 01 30:45:62

Don't know if this is significant or not, but ImgBurn reports this about the Apoc CD:

TOC Information:
Session 1... (LBA: 0 - 257168)
-> Track 01 (Mode 1, LBA: 0 - 257167)
-> LeadOut (LBA: 257168)

Track Information:
Session 1...
-> Track 01 (LTSA: 0, TS: 257168)