Skip to content
This repository was archived by the owner on Jun 4, 2026. It is now read-only.

SNES: Add support for ExLoRom mapping#74

Open
yuriks wants to merge 1 commit into
SourMesen:masterfrom
yuriks:exlorom
Open

SNES: Add support for ExLoRom mapping#74
yuriks wants to merge 1 commit into
SourMesen:masterfrom
yuriks:exlorom

Conversation

@yuriks

@yuriks yuriks commented May 13, 2025

Copy link
Copy Markdown
Contributor

(This is a slightly improved version of the patch I mentioned a while back on the snesdev discord.)

This format is used by ROM hacks, and is supported by at least Snes9x and bsnes. It's indicated by having a copy of the header at 0x400000 with a LoRom map mode.

The removed check for map mode 0x22 triggered in S-DD1 games, but their memory layout is very different from ExLoRom. Their mapping is handled by MapBsxMemoryPack instead of the regular RegisterHandlers code anyway, so the setting of that flag had no effect other than what's reported in the log window, but it was removed to prevent future confusion.

This format is used by ROM hacks, and is supported by at least Snes9x
and bsnes. It's indicated by having a copy of the header at 0x400000
with a LoRom map mode.

The removed check for map mode 0x22 triggered in S-DD1 games, but their
memory layout is very different from ExLoRom. Their mapping is handled
by `MapBsxMemoryPack` instead of the regular `RegisterHandlers` code
anyway, so the setting of that flag had no effect other than what's
reported in the log window, but it was removed to prevent future
confusion.
@yuriks

yuriks commented May 15, 2025

Copy link
Copy Markdown
Contributor Author

As brought up on Discord: I'm additionally licensing this code under the terms of BSD-0, and explicitly allow it to be relicensed in any way if desired in the future, and without any need of attribution.

Yave-Yu pushed a commit to Yave-Yu/MesenYY that referenced this pull request May 2, 2026
Otherwise, when pushing a new update via the auto-update, all users will be shown the configuration wizard and "lose" their settings, save data, save states, etc. because the new version will create a new MesenCE folder.
This instead allows the application to continue using the Mesen2 folder as-is. If a new installation is done, it'll go inside the MesenCE folder.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant