Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CHD CDs are not reproducible between 2048B/2352B sector images that convey the same information #12806

Open
chungy opened this issue Sep 22, 2024 · 0 comments

Comments

@chungy
Copy link
Contributor

chungy commented Sep 22, 2024

MAME version

0.269

System information

n/a

INI configuration details

n/a

Emulated system/software

n/a

Incorrect behaviour

In CD-ROM images, sync, address, EDC, and ECC subchannels are normally constructed from well-known methods and MODE1 discs that do not perform any tricks should be reconstructable to the original physical format image from a 2048B sector ("cooked") image. This is the case for the vast majority of MODE1 discs without physical DRM applied to them.

The bin2ecm utility is an example program that takes advantage of this fact to offer high compressability to 2352B sector ("raw") images: https://github.com/chungy/cmdpack/blob/master/bin2ecm.txt

Expected behaviour

I believe that since CHDs are supposed to represent CD-ROMs, the input of 2048B sector images should end up with the same CHD as a 2352B sector image conveying the same data without any subchannel manipulation.

Steps to reproduce

Here is an image for demonstration purposes:

test.zip

If you create a CHD in the two ways, chdman createcd -i test.toc ... and chdman createcd -i test.iso ..., you get distinct CHDs with different SHA1s. If you mount or burn test.iso and use cdrdao read-cd --device /dev/srN --read-raw --datafile new.dat new.toc, you will notice the new.dat will match with identical data as in the test archive. The subchannel data is not manipulated and can be reproduced exactly, hence proving its identity with the "cooked" image.

Additional details

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant