Hi @XFlak great work as always. Wanted to provide my feedback using 6.6.3.
Nits:
(1) in the (W)izard the text in the select new System Menu version is:
"Modmii recommends unnecessarily changing system menus if already on 4.1 or higher."
From context, it's clear such a change is unnecessary, but the sentence still reads as a recommendation of that unnecessary change. Recommend editing to:
"Modmii recommends against unnecessarily changing system menus if already on 4.1 or higher"
(2) In the most vanilla hacking I could do in the (W)izard, (saying no on most prompts, saying no to setting up a USB loader) the WADs to be installed still include the usb loader forwarder (USBLoader(s)-ahbprot58-SD-USB-v12-IDCL-alt.wad), which I've safely skipped before, but it should be omitted from the download queue if the user elects to not set up a USB loader, right?
(3) The basic (S)neek installation does not include the Sneek/neek2o channel (to switch between emunand and realnand from the system menu). No apps folder at all, in the SD copy folder. Presumably you would want to include a wad manager as well to facilitate its installation. The last page of the (S)neek installation with the details alludes to the channel.
Other notes:
(4) On the 4.3J virgin I was modding today, I noticed that wilbrand (bannerbomb) actually wasn't working with a FAT formatted SD card. Worked fine with FAT32. I know ModMii includes the format-to-FAT32 step but I'm just surprised FAT doesn't work.
(5) in (RC) Region change the default configuration appears to download and use mmm, while for the (W)izard you've switched to YAAAMM. Wondering if you wanted to universalize that switch.
(6) while doing the actual region change I hilariously messed up and selected the first Priiloader option "System Menu" after installing the RC wads and Priiloader (I was supposed to select "System Menu Hacks") and Modmii is covered in warnings not to leave HBC until the region change is complete. The JP system menu loaded and I was worried I semi bricked. But I was able to relaunch HBC and continue without issue.
(7) Not to be partisan, but that last (S)neek page also pushes USB Loader GX rather than explaining what to do in its absence. One big issue I didn't know about until I did today's non-boot2 Bootmii Wii is that you keep the bootmii folder with Modmii's bootmiineek armboot.bin put in the real bootmii folder, which stays on the SD card in order to facilitate neek2o. I had been taking it off on previous setups that had boot2 bootmii (because otherwise the Wii always boots to bootmii).
(2) Well, it’s already indirectly mentioned in a few places. Anytime an exploit is referenced in a modmii guide, there’s a spoiler telling you how to launch the hackmii installer using 1) the HBC if already installed, 2) bootmii boot2 if already installed, and 3) you guessed it, a forwarder channel. I don’t think I actually refer to ModMii’s forwarder specifically, it’s a general comment that applies to any forwarder as users will often customize these.(2) That's cool, I like your idea to future proof modded Wiis in such scenarios. You may want to mention some of that in ModMii, just that the forwarder channel is included by default as an additional redundancy to run custom code.
(3)/(7) I think you might be the victim of your own success here. ModMii is great for building an emunand. Which I did once. Now I deploy that emunand build to a subsequent Wii (literally just copying the files to the next HDD), but it's not immediately apparent how to configure ModMii to get the realnand and SD neek2o items needed installed on that subsequent build. The core SNEEK items go on SD/USB (which ModMii does in basic (S)neek), but I was without a channel or an app to actually boot emunand, and simultaneously had no guidance on what edits needed to be done manually for emunand to be bootable (which I think is: rename SD:/bootmiineek/armboot.bin to SD:/bootmii/armboot.bin IFF bootmii installed only as IOS).
This forum is littered with threads asking about neek2o hanging on loading bootmii IOS. You're best positioned to demystify this on the front end.
Yes. Well, my recommendation is that the basic neek installation includes them (Modmii No. 1, rather than No. 2). Nswitch or equivalent should go in apps/ and you can optionally include a WAD. The software to access emunand doesn't strike me as part of the 'build an emunand' option, it strikes me as core neek functionality and thus should be part of option 1.“-consider adding neek switching apps\wads to neek installation in addition to emunand construction”?
Nice @XFlak! But when you will add to your downloads section the Not64 Second Edition (v20200609) emulator? https://www.gc-forever.com/forums/viewtopic.php?f=9&t=2723So I think there have been enough developments to justify another small modmii update. Not sure when I'll get to it, but within 1-4 weeks I'm sure I'll find time.
There's a new usbloader gx mod by @blackb0x that has some sweet new features, new priiloader hack to disable the system menu's deflicker... and I'll investigate the drive setting issues a couple ppl have reported when setting it to E: or similar
My take is that Not64 (generally, and currently) had wider compatibility, but Wii64 rice has better performance (and completeness in terms of rendering elements) for certain games.I thought with the latest wii64 update, it was on par with not64?