- Joined
- Oct 27, 2002
- Messages
- 23,749
- Trophies
- 4
- Age
- 46
- Location
- Engine room, learning
- XP
- 15,662
- Country
the r52 you installed are good. it works with emuNAND, and only USB Port 0.Another question after reading some posts, I have installed cios 249-251 with the d2x r52 with a base of 56-58. Then installed the alt53 over 252/253/255. Was this a blunder using 255?
the r53 you installed are beta, and useful only if you need USB Port1 support in Wii games. (plug HDD with Wii iso on port1). r53 doesn't work well with emuNAND.
there is a r52 mod which can be used with emuNAND+Ustealth HDD.
installing a cIOS in slot 255 is not (or shouldn't) affect the fw.img (also using the same slot number).
the WiiVC slot255 is virtual, it doesn't really load what's installed in the slot255 of your vwii. that WiiVC cIOS255 is loaded from the WiiVC Wiiu NAND, inside the channel's content, and it's the "fw.img" patched file.
that virtual slot can't be changed, the fw.img is always the one used, even if an app requests an IOS_reload, it's still fw.img which is reloaded and faking the slot number to the requested one.
I don't know about your issue, maybe JacobM found your problem?
JacobM, you fixed that issue by unplugging USB?
I think it's a bug in recent version of nintendont + USB HID plugged + Argument launching method.
Fix94 recently talked about it in USBGX thread, someone (you?) made some changes to nintendont to test that bug.
I don't remember if I made a test version to not pass the settings using arguments and only rely on SD's nincfg.bin file.