TASEmulators / TASEmulators/BizHawk
Detect Genesis/Mega Drive ROMs based on Headers in ROM Data
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 2.8k
- Forks
- 468
- PR merge metrics
- No merged PRs in 30d
Description
I checked and all Good/Proper Genesis/Mega Drive ROMs have at Offset 0x100, have the Hexademical values:
"53 45 47 41 20 47 45 4E 45 53 49 53 20 20 20 20"
Or
"53 45 47 41 20 4D 45 47 41 20 44 52 49 56 45 20"
This signifies that it's a Sega Genesis/Mega Drive ROM. My question is, can we read in the ROM at that offset, for 16 bytes, and look for those values? If we see those values, load up the ROM into the Genesis Core.
BizHawk would probably need to verify that the ROM itself has enough bytes to actually reach Offset 100 and has at least 16 bytes beyond that.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing BizHawk's ROM-loading and core-selection entry point, since the issue names no specific file or test. Check for the 16-byte Genesis/Mega Drive header at offset 0x100 only when the ROM is long enough, then verify that matching ROMs are sent to the Genesis core.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- game-dev
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100