I asked this question before and got some good advice, but I've hit another stumbling block so I'll explain from the beginning.
My current setup is Priiloader autoboots Wiiflow, which is located on my SD card. My emunand is located on USB.
If my Wii boots with the SD card inserted, but not the USB, it will still load Wiiflow, but Wiiflow will not detect the USB emunand location, and will reconfigure its settings to default: look for an emunand on the SD card, which does not exist. Even if the USB drive is plugged in subsequently, those Wiiflow settings remain pointed at the SD card/defaults.
All this means that, if a user unplugs the USB, they need specific knowledge of which Wiiflow settings to fix in order to reenable emunand support in Wiiflow. I'd like to prevent and child-proof that scenario, so an end user never has to fiddle with the Wiiflow settings.
I first asked if the Wiiflow configuration could be "locked" so this doesn't happen, but I don't believe that is possible. Someone (apologies, I don't recall who) recommended putting Wiiflow on USB as a workaround. This way, Wiiflow can't boot in a way where the emunand USB path isn't also available, so the relevant settings will not get borked. Great!
So here's my next question: can you get Priiloader to autoboot Wiiflow that's located on the USB? It seems to only be able to boot dols on the SD card, so I assume I should point Priiloader to some kind of forwarder (that points to the usb/Wiiflow) rather than the regular apps/wiiflow dol. Can anyone confirm that, and point me to an appropriate dol to use for Priiloader?
My current setup is Priiloader autoboots Wiiflow, which is located on my SD card. My emunand is located on USB.
If my Wii boots with the SD card inserted, but not the USB, it will still load Wiiflow, but Wiiflow will not detect the USB emunand location, and will reconfigure its settings to default: look for an emunand on the SD card, which does not exist. Even if the USB drive is plugged in subsequently, those Wiiflow settings remain pointed at the SD card/defaults.
All this means that, if a user unplugs the USB, they need specific knowledge of which Wiiflow settings to fix in order to reenable emunand support in Wiiflow. I'd like to prevent and child-proof that scenario, so an end user never has to fiddle with the Wiiflow settings.
I first asked if the Wiiflow configuration could be "locked" so this doesn't happen, but I don't believe that is possible. Someone (apologies, I don't recall who) recommended putting Wiiflow on USB as a workaround. This way, Wiiflow can't boot in a way where the emunand USB path isn't also available, so the relevant settings will not get borked. Great!
So here's my next question: can you get Priiloader to autoboot Wiiflow that's located on the USB? It seems to only be able to boot dols on the SD card, so I assume I should point Priiloader to some kind of forwarder (that points to the usb/Wiiflow) rather than the regular apps/wiiflow dol. Can anyone confirm that, and point me to an appropriate dol to use for Priiloader?