Maikel Steneker:
When I used your batch files to produce the files for an R4 in EN as the default boot menu, for some reason r4patch.dat still refered to ttreset.dat as being in the folder /TTMENU/ttreset.dat, hex edited it (offset 0x1AF5B) to point to /YSMENU/ttreset.dat and it worked like a charm after that.
Wow, cory1492 actually used my program
This actually explains a lot of problems! Thanks for this extremely useful info! I'll look into it to find if I can make some kind of simple patcher that doesn't cause any problems (with, for example, future versions).
Huh. It's 0x1AFB5 actually. And I just tried editting it and it doesn't work. YSMenu will still stop, not being able to find the file if it's not in /TTMENU/, and I looked at r4patch.dat afterwards and YSMenu had "fixed" the file, making it point to /TTMENU/ttreset.dat again. Either way, ttreset.dat just locks up the R4 anyway.
QUOTE said:
QUOTE(phnord @ Sep 25 2008, 06:28 PM)
I've had a couple of problems with this so far.
The first is that I originally built it to load after the R4 firmware (aka calling it "Default.nds"). The problem with this seemed to be that YSmenu *also* tried to load "Default.nds" upon starting up, meaning it went into an infinite loop of loading the ROM. How did other people avoid this? I ended up renaming it to the name of the moonshell and starting it up from there instead.