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

Incorrect rom allocation on alt64/altra64 on ed64 #22

Open
ariahiro64 opened this issue Jul 31, 2022 · 3 comments
Open

Incorrect rom allocation on alt64/altra64 on ed64 #22

ariahiro64 opened this issue Jul 31, 2022 · 3 comments

Comments

@ariahiro64
Copy link

some larger roms like the legend of zelda 1 don't read the last couple bytes and crash on alt64 and altra64. I have a getto solution (adding padding to the end of the rom). most users wont expect to do that tho. gb64 doesn't have that issue.

@hcs64
Copy link
Owner

hcs64 commented Jul 31, 2022

Unfortunately this isn't something I can fix on the Neon64 side, it's a bug with the loader (64drive's USB loader also has this issue). iNES ROMs have a 16 byte header which means that the ROM is a multiple of 8k plus 16 bytes, a lot of loaders just can't handle ROMs with that odd size. You don't see this with GB64 because Gameboy ROMs don't have an emulation header, so they're a reasonable round ROM chip size.

@hcs64 hcs64 closed this as completed Jul 31, 2022
@hcs64
Copy link
Owner

hcs64 commented Jul 31, 2022

I might as well leave this issue open to add it to the Readme. Thanks for the reminder.

@hcs64 hcs64 reopened this Jul 31, 2022
@ariahiro64 ariahiro64 changed the title Incorrect rom allocation on alt64/altra64 Incorrect rom allocation on alt64/altra64 on ed64 Apr 22, 2024
@ariahiro64
Copy link
Author

may have a solution but it may have to wait until i get a ed64p again. daisy drive 64 added code that fixes this

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

2 participants