AR V3: NO$GBA vs VBA

[Demonic722]

I found this in a post by GM0 at CMP:

On actual hardware (HARDWARE, not upgraded software on old hardware):
V.1/2 can handle a maximum of 1 patch code, depending on master code.
V.3 can handle a maximum of 4 patch codes, depending on master code. Each code must be a different patch type - either z0C, z0D, z0E or z0F. What this means, is that you can only have one patch code encrypted using the z0C type - if you want to have two ROM patch codes, you need to use one of the other types (they're all equivalent in terms of what actually happens).

It is dependant on master code because some (very rarely) also require a patch code component to achieve a 'hook', which takes up one space on the chip.

Codes remain active until they are replaced (another code is entered) or the game is hard reset (i.e., cart physically taken out, not just pressing the reset button).

When I test this on VBA-H, it seems to work as described. However, NO$GBA seems to require that the ROM codes use the same "Patch Type" or else the codes will fail to execute. I do not have the hardware to test whether or not NO$GBA is incorrectly emulating AR V3, so can someone confirm this? This information is crucial since I am in the process of correcting my GBA codes to reflect what Labmaster has stated.

Thanks in advance.

[lee4]

I wish I could help but I have codebreaker only

according to these sites*
z0C = patch rom 0x08000000
z0D = patch rom 0x0A000000
z0E = patch rom 0x0C000000
z0F = patch rom 0x0E000000

*sources:
http://www.codemasters-project.net/p...hp?content.203
http://problemkaputt.de/gbatek.htm#gbamemorymap

[Demonic722]

Ah, alright. Thanks anyway.