- Joined
- Jun 23, 2005
- Messages
- 1,497
- Reaction score
- 25
- Trophies
- 2
- Location
- Home, WhereElse?
- XP
- 366
- Country

Well, that's a bit of a trade-off, I have a 3in1 here as well - I guess that means ez4 will never have PSRAM support here then despite EZ3 and EZ4(dlx) operating nearly identical to 3in1.... unless - why not check gba header 0xa0 for the string "EZPDA" (the EZ5 multi loader for 3in1 is "EZLoader" so there should be no conflict there) before executing the code that seems to be mixing up the ez4, getting rid of that global variable? Should be effective for EZ3 as well, and would constitute only 2 reads off the bus which shouldn't slow the thing down any.Smiths said:cory1492 said:Smiths/Normatt: Ran across another issue, just so you know I did get the drunken beta that was posted and that is what I am using today. Have either of you worked on/fixed the slot2 "passme" code at all? I can't get it to boot my EZ4 in DS mode, if you like I can supply some code that I know works for it and works well for some problematic old ds.gba that exist (but has never worked on M3 perfect for an unknown reason.) Lust LMK and I'll point you at it.
I had to add a manual command line for EZ4 fixing actually. It's been a long time since it's come up so unfortunately it isn't documented. Some day i'll document the random things and usage guides to the firmware... there's just so much.
EZ4 DESPISES the 3in1 check at startup. so much so that even the act of checking the slot 2 card (if an EZ4 is in it) will make the EZ4 not recognized. It doesn't do anything to the data, but it pisses off the NDS so much it doesn't load it right.
Lemme dig up the globalsettings.ini variable you have to set:
CODEEZ3in1startupcheck = 0
set that.
I've confirmed, setting romPage(0x8000) is all that is required to get back to EZ4's OS mode (where the menu and it's loader is at GBAROM offset just like at power on) - the 4MiB dump I just did with AK2 matches what I dumped previously, but all of my methods of loading EZ4 OS results in a white screen on AK4 while working fine on multiple other slot1 cards. Bloody odd, a definite first for me - AIO seems to be doing something funky, even getting SD access on EZ4 works fine - just not start/loading that menu. I insist, there is a bug... somewhere xD
The apps and source I was just testing with. Hope my time has helped, in some strange fashion, in some way that isn't just creating more work.
Is there anything else I might be missing here? Something else that happens when that setting isn't set that would affect the EZ4's menu loading? Some variable/register that gets set by your checks in the DS itself that isn't reset by the launchers? The white screens I'm getting from my own apps really shouldn't be occurring (fat lot of good me insisting that will do though, of course.)
Worst comes to worse though, one can always rename it from AKAIO (Ace Kard all in one) to AKAIO-ETAT (Ace Kard all in one - except this and that)
Has anyone tried exploader (or whichever was compatible) with an ez4 from AIO?
btw: is there even a globalsettings.ini? I don't see one in the packages I've gotten from AIO, might be useful to have one with all (or at least the common) globalsetting variables in it... I deleted the "ZELDA" theme off my card and the bloody thing is staying on the list and changing/adding to the default in a non-existant ini file seems... odd.
edit:/ oh, there it is, guess it created it at some point - confirming again that the global setting works out just fine.











