And the current implementation of neek2o beta is not stable.
it's not meant as a end user full usable interface. only developers should use it.
-So where do I find these files?
read the txt file? use modmii
these files can't be shared because it contains a IOS file.
-Can I still use regular EmuNAND after N2O is fully implemented? If that's the case then awesome, I can use N2O with channels and keep EmuNAND for regular Wii games.
yes.
the emuNAND is EXACTLY the same.
neek2o is not doing anything to your emuNAND.
neek2o is only few files located on /sneek/ folder, they are acting as a loader responsible of loading the NAND.
You just choose which program you want to use to load the NAND dump : the USBloaderGX or the /sneek/ files.
for ALL your channels working with USBLoaderGX as channel, continue using USBLoaderGX as nand loader.
for the channel not working with USBLoaderGX as NAND loader, tell USBGX to load neek, and neek will load the channels.
I have another problem:
Sometimes when launching a GCN game via GX i get the following codedump.
First I see the Nintendont splashscreen, but it´s much longer empty then usual, then the upper text of Nintendont (version etc) and when it normally starts with the steps (1-11) I get the codedump.
If you see nintendont, then USBLoaderGX is not in memory anymore.
it's not a loader issue.
does it happen when launching Nintendont directly from HBC?
if only from the loader, did you try different settings?
Set the Settings>Loader settings>Nintendont>Config file : Create
Then next time it crashes, send me the nincfg.bin file
I need to check if the sent settings are correctly generated and sent.