EDIT: I think I done fucked up something and this is probably totally unnecessary. Please disregard unless this has other applications.
So, as I recently discovered, it's impossible to play games such as Super Smash Bros. or MH4U on an EmuNAND, because the system has to reboot into extended memory mode - which means it kicks you out of EmuNAND, and gives a "The SD card was removed." error because SysNAND is on 4.5 (in my case, at least) and doesn't know what to do with the "boot in extended memory mode" command.
SO! My idea is thus. We already have launcher.dats that can patch all sorts of checks (Pasta, Palantine, PBT...). Is it possible to create one that instructs the EmuNAND to boot in extended memory mode? As I recall, the games LEAVE the 3DS in that mode, which is why someone made a program specifically for the sake of getting out of that. I'm very interested in finding out whether or not the games still reboot the 3DS if they detect that it's *already* in that mode.
Thoughts? Ideas? (Hell, I REALLY need to learn how to code this stuff.)
So, as I recently discovered, it's impossible to play games such as Super Smash Bros. or MH4U on an EmuNAND, because the system has to reboot into extended memory mode - which means it kicks you out of EmuNAND, and gives a "The SD card was removed." error because SysNAND is on 4.5 (in my case, at least) and doesn't know what to do with the "boot in extended memory mode" command.
SO! My idea is thus. We already have launcher.dats that can patch all sorts of checks (Pasta, Palantine, PBT...). Is it possible to create one that instructs the EmuNAND to boot in extended memory mode? As I recall, the games LEAVE the 3DS in that mode, which is why someone made a program specifically for the sake of getting out of that. I'm very interested in finding out whether or not the games still reboot the 3DS if they detect that it's *already* in that mode.
Thoughts? Ideas? (Hell, I REALLY need to learn how to code this stuff.)
Last edited by Jaitsu,