Launch System Menu when BootMii launch fails.

[GoogleCodeExporter]

It would be nice if Priiloader could simply launch the System Menu when 
fat:/bootmii/armboot.bin is not found. This would preserve a function of 
BootMii which is broken by the use of Priiloader, since BootMii would usually 
boot the System Menu in this scenario.

The usage case for this change may seem opaque, but it's a useful change for 
SNEEK users. Included below are some examples of BootMii/boot2 vs. BootMii/IOS 
boot processes for SNEEK users, which hopefully demonstrates the utility of 
this change.

*BootMii/boot2 with SNEEK*
BootMii: Launch SNEEK -> Emulated NAND System Menu

*BootMii/boot2 without SNEEK (/bootmii renamed)*
BootMii: No /bootmii, launch System Menu -> Priiloader: Launch System Menu -> 
Real NAND System Menu

*BootMii/IOS with SNEEK*
Priiloader: Launch BootMii -> BootMii: Launch SNEEK -> Emulated NAND System Menu

*BootMii/IOS without SNEEK (/bootmii renamed)*
Priiloader: Launch BootMii -> Failed, no armboot.bin.

And lastly, this is how the process would look were this change to be made.

*Desired behavior for BootMii/IOS without SNEEK (/bootmii renamed)*
Priiloader: Launch BootMii -> No /bootmii, launch System Menu -> Real NAND 
System Menu

This way, users get behavior more in line with what's expected from BootMii/IOS 
without Priiloader (roughly transparent to users--it'll "just work"), and as a 
bonus, greatly improve interactions between Priiloader and SNEEK, since 
Priiloader can be set to autoboot BootMii, and users will never encounter the 
armboot.bin error on startup. Instead, it will work (cosmetically) identically 
to BootMii/boot2 and SNEEK.

While I feel this would be an improvement globally, if it is undesirable for 
this change to be hardcoded (e.g. users not understanding why launching BootMii 
makes the System Menu appear), perhaps it could be made available as a setting, 
allowing only those who understand what they're doing to achieve feature parity.

Thanks for any consideration.

Original issue reported on code.google.com by vaguerant on 3 Aug 2011 at 12:47

[GoogleCodeExporter]

euh, you *can* use the bootmii option in priiloader to boot Sneek without 
bootmii booting...

i do know bootmii uses 2 files (the armboot.bin for starlet and ppcboot(or 
something similar) for the ppc code, and that priiloader used to check for both 
which fucked sneek. this was changed in the past to make it work just fine.

so basically, all you need to do is set autoboot to bootmii and replace the 
bootmii files with the sneek files

Original comment by dac...@gmail.com on 3 Aug 2011 at 2:02

• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

that is what you wanted right?

Original comment by dac...@gmail.com on 3 Aug 2011 at 2:03

[GoogleCodeExporter]

SNEEK works just fine, the problem is when I /don't/ want to use SNEEK. There 
are various tools that rename /bootmii so that SNEEK isn't launched, since 
BootMii just launches the System Menu in that scenario. If you have priiloader 
set to autoboot BootMii, however, then renaming /bootmii to turn off SNEEK just 
gets you a Priiloader error. This change would mean SNEEK booting continues to 
work fine, while disabling SNEEK by renaming /bootmii also works.

Original comment by vaguerant on 3 Aug 2011 at 2:08

[GoogleCodeExporter]

i have a better idea, try and contact a dev of one of the renaming tools to 
force priiloader to launch SM using the magic word. if that doesn't work come 
and contact me so i can think of something. priiloader is very flexible like 
that ^^;

Original comment by dac...@gmail.com on 11 Dec 2012 at 11:44