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

Format and read/write GAP#3 values are different, but we only get one #18

Open
pelrun opened this issue Apr 25, 2022 · 0 comments
Open

Comments

@pelrun
Copy link
Owner

pelrun commented Apr 25, 2022

Looks like we get the format GAP#3 in the disk image. I'm setting both to this value, but the read/write value appears to normally be about half the format one. (42 for a format GAP#3 of 80/82).

That means there's probably a risk of overwriting the ID of a following sector. Easiest fix is just to set the default write GAP#3 value when we get an expected format one; the trick is figuring out what behaviour to use in the other cases. Pinball Dreams, which triggered this in the first place, seems to use 42 for the format gap!

Need to find some weird formats (Bigbonzo's worth a look) to test against.

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