DS's only have 4mb of ram. The old 3DS has 128 mb of ram and 6mb of VRAM
--------------------- MERGED ---------------------------
N3DS has 2 GB RAM: 128 MB FCRAM, 4 MB VRAM
New 3DS has 256 mb of FCRAM and 10 MB of VRAM
DS's only have 4mb of ram. The old 3DS has 128 mb of ram and 6mb of VRAM
--------------------- MERGED ---------------------------
N3DS has 2 GB RAM: 128 MB FCRAM, 4 MB VRAM
DS's only have 4mb of ram. The old 3DS has 128 mb of ram and 6mb of VRAM
--------------------- MERGED ---------------------------
N3DS has 2 GB RAM: 128 MB FCRAM, 4 MB VRAM
hum... no. That ~2gb thing is the nand's space, not the ram.N3DS has 2 GB RAM: 128 MB FCRAM, 4 MB VRAM
Plus the games only need ~ 4mb of ram
GBA virtual console works by loading the entire game into RAM and emulating a SLOT-2 using that. A similar method would require us to load the entire DS game into RAM and emulate a SLOT-1, which won't work for a lot of games, even on the n3ds, simply because there's not enough RAM. Even so, we didn't get GBA virtual console until Nintendo released it, in which case we figured out simply how to get it to load other roms. Unless Nintendo releases something it's unlikely to happen.Plus the games only need ~ 4mb of ram
Unfortunately, I know very little about Wii hacking.How works the MIOS on Wii y comparation of the TWL on 3DS?
If I'm not wrong, the MIOS tries to read from the DVD lector like TWL (NTR exactly) tries to read from the Slot-1, right?
As I stated, a fundamental problem with this is that DS games are programmed to load games from Slot-1, not from the SD. It is nearly impossible to change how they load files without the source code to the rom. No amount of mods to the HBMenu can change that.Apache Thunder said we should start from there because he was able to get a similar result with another operation. He thought we could MOD the HBMenu
This is precisely the problem. The n3ds doesn't have enough ram to even hold some nds games. Even so, we have no method to emulate TWL Slot-1 without Nintendo releasing something.It does not only require 4 MB of RAM to load NDS ROM into memory. We need a little bit more than the size of the ROM. Why? Because TWLfirm doesn't know what the heck is sdcard so it will be simplest to redirect all request to read slot1 by twlfirm to some region of memory on the 3ds firmware syscall that interact with twlfirm. Assuming there is any, from the way the 3ds have to reboot to play nds games, there doesnt seem to be anything left of 3ds firmware once twlfirm starts.
Easier said than done. WAY easier said than done. How do you plan on redirecting all the calls to Slot-1, without the source of the NDS rom?How about this?:
We would need to ADD a CIA that brings you to a menu and you can select which game you want- then reboots into a different partition on the SD card (like EmuNAND) that is a virtual copy of TWL_Firm that redirects all saves and access to the extra partition and has the game loading
Maybe the extra partition COULD be slot-1
By the way, here's that NDS menu working:
The DSi had an SD card slot though. We've been able to get DSiWare running fine. DS never had an SD card slot though which is why we've made almost no progress."3ds have native ds emulation" How can something be native and emulated cause you cant have both, the problem is ds is running natively and we have almost little control with it, this year it's of progress been don't to control it and use it, it's even possible to run the dsi homebrew channel now from the 3ds homemenu
All my previous complaints still stand.