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

Arcade version? #1

Open
kuroya2mouse opened this issue May 5, 2024 · 2 comments
Open

Arcade version? #1

kuroya2mouse opened this issue May 5, 2024 · 2 comments

Comments

@kuroya2mouse
Copy link

If it's not difficult, it would be nice if there was arcade version in same codebase

@Nasina7
Copy link
Owner

Nasina7 commented May 6, 2024

I do have plans to add support for the arcade versions, but it'll still be a bit before that happens. It's next up on the list of things to do once I have most of the code documented. I haven't looked into it too deeply yet, but from what I've seen it doesn't seem like it'll be too difficult to add support for it.

@radioshadow
Copy link

It's worth point out that the code in the Arcade is stored on 2 x 128Kb EEPROM chips. Using the Rev B download, the code is stored in these two files:

  • epr-15036b.32 (Part 1)
  • epr-15036b.31 (Part 2)

The issue is the code is stored using high and low bytes, so it's very difficult to view the 68K code. Using a program called romwizard (http://www.wolfgangrobel.de/romwizard.htm), you can merge the files into one, and the 68k code be viewed.

A quick guide:
1 - Load "epr-15036b.32" into ROM1
2 - Load "epr-15036b.31" into ROM2
3 - Tools > ROM Merge
4 - Select: ROM1(H) _ ROM2(L)
5 - Click "Merge" and save file.

To convert back:
1 - Load Merged File into ROM1
2 - Tools > ROM Split
3 - Select: ROM1 H/L
4 - Click "Merge" and save files
5 - Change: epr-15036b.part1 > epr-15036b.32
6 - Change: epr-15036b.part2 > epr-15036b.31

So there is a bit of converting to do, but it would be possible to make a disassembly based on the merged file. The other EEPROM chips I suspect store the audio and graphics, and they may need the same treatment to view correctly. I haven't really looked further into it know.

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

3 participants