see title, just wanted to know if this was okay to do, because i don't want to mess anything up while setting up emuNAND
Probably not ok since launcher.dat is in the microSD. Also you do know that the emuNAND is created on that microSD right? It needs to read the NAND.bin, you hopefully will copy to your computer, to create an emuNAND.
No, because it'll crash, as emunand is a modified copy of your sysnand but running from your Micro-SD Card.
Oh okay. I've already dumped my sysNAND, and am currently dumping some of my retail games. So from here, I guess i'd turn it off, backup my game/sysNand/Nintendo3DS folder, delete the game from the microSD, and then format emuNAND?
I was just worried if having NAND.bin or the Nintendo3DS folder on the card would mess up emuNAND setup/if you needed the Nintendo3DS folder to launched the CN exploit
Yes, backup up everything from the internal microSD. You only need to have the launcher.dat and the NAND.bin in the microSD to create an emuNAND. Then format emuNAND and then copy everything back.
Nothing major but you do not need NAND.bin on the mSD to format/"create" emunand. I always copy it off immediatly after dumping my sysnand. I did this three times last night with 3 different n3ds.Yes, backup up everything from the internal microSD. You only need to have the launcher.dat and the NAND.bin in the microSD to create an emuNAND. Then format emuNAND and then copy everything back.
So what does it do? Does it redump the NAND or just read it straight off and create one?Nothing major but you do not need NAND.bin on the mSD to format/"create" emunand. I always copy it off immediatly after dumping my sysnand. I did this three times last night with 3 different n3ds.
Honestly I don't know how GW implements the function. Although it is often said emunand is a 1:1 copy of sysnand for it to behave differently it has to have additional/modified code. It does take approximately the same amount of time to backup sysnand as it does to format emunand so my guess is it reads it again and does its patching in the process.So what does it do? Does it redump the NAND or just read it straight off and create one?