Detect ISO9660 filesystem in BIN file without corresponding CUE file #208

New Issue

claunia · 2026-01-29T15:13:13Z

claunia commented

2026-01-29 15:13:13 +00:00

Originally created by @dcoshea on GitHub (Jun 11, 2018).

It would be nice if the BIN image format, as in the first half of the usual BIN/CUE pair without the corresponding CUE, could be detected. It isn't detected, at least not with version 4.0.1.0.

iat (GitHub repo which might not be canonical, if there is any canonical repo anymore; sparse SourceForge project page) is able to do this, at least when the BIN file contains an ISO9660 filesystem. It can also generate a CUE file, but it doesn't actually detect when there are multiple tracks in the BIN file (I'm not sure if that is even possible to determine from the BIN file alone), so it's not a particularly interesting feature but might be nice for DiscImageChef to do this for completeness, so long as it is accompanied by a warning that the tool is assuming that there is only a single, data track.

Presumably if DiscImageChef could detect this format, it could convert it to a plain ISO9660 .iso file.

Workaround:

I was able to work around the lack of this support by manually creating a simple CUE file:

FILE "myfile.bin" BINARY
  TRACK 01 MODE1/2352
    INDEX 01 00:00:00

DiscImageChef was then able to analyze the BIN/CUE pair when invoked as DiscImageChef.exe analyze -i myfile.cue.

I'm not familiar enough with BIN/CUE files to know off the top of my head what alternatives to MODE1/2352 exist, that's just the format I'm familiar with from the two such images I've ever dealt with.

Originally created by @dcoshea on GitHub (Jun 11, 2018). It would be nice if the BIN image format, as in the first half of the usual BIN/CUE pair without the corresponding CUE, could be detected. It isn't detected, at least not with version 4.0.1.0. `iat` ([GitHub repo which might not be canonical, if there is any canonical repo anymore](https://github.com/lolilolicon/iat); [sparse SourceForge project page](https://sourceforge.net/projects/iat.berlios/)) is able to do this, at least when the BIN file contains an ISO9660 filesystem. It can also generate a CUE file, but it doesn't actually detect when there are multiple tracks in the BIN file (I'm not sure if that is even possible to determine from the BIN file alone), so it's not a particularly interesting feature but might be nice for DiscImageChef to do this for completeness, so long as it is accompanied by a warning that the tool is assuming that there is only a single, data track. Presumably if DiscImageChef could detect this format, it could convert it to a plain ISO9660 .iso file. **Workaround:** I was able to work around the lack of this support by manually creating a simple CUE file: FILE "myfile.bin" BINARY TRACK 01 MODE1/2352 INDEX 01 00:00:00 DiscImageChef was then able to analyze the BIN/CUE pair when invoked as `DiscImageChef.exe analyze -i myfile.cue`. I'm not familiar enough with BIN/CUE files to know off the top of my head what alternatives to `MODE1/2352` exist, that's just the format I'm familiar with from the two such images I've ever dealt with.

claunia referenced this issue

2026-01-29 15:40:22 +00:00

[PR #208] [CLOSED] Set up CI with Azure Pipelines #1063

claunia referenced this issue

2026-01-29 15:40:29 +00:00

[PR #208] Set up CI with Azure Pipelines #1067

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: aaru-dps/Aaru-aaru-dps#208