Feature request: Install IOS to any slot

[GoogleCodeExporter]

For people who would like to gain the benefits of patched IOSes without
modifying existing ones.

Original issue reported on code.google.com by Flamesha...@gmail.com on 9 Feb 2010 at 11:57

[GoogleCodeExporter]

I'm not sure if I would even want to consider it and here is the reason why. 
1. You can always reinstall an IOS without patches.
2. You can use other patched IOSes that are not really in use anymore. Example 
being
IOS60 if you are running System Menu 4.2. This is why we ask you which IOS do 
you
want to use for DOP.
3. You can use a Custom IOS which is basically the same as a patched IOS in a 
way.
4. I just don't see the benefit.

Pretty much what I'm saying is that I have just about every IOS on my Wii 
patched and
I haven't run into issues. And if I do I can always roll an IOS back to the 
original
state.

Original comment by Lunatik.CN@gmail.com on 9 Feb 2010 at 12:56

• Added labels: Type-Enhancement, Priority-Low
• Removed labels: Type-Defect, Priority-Medium

[GoogleCodeExporter]

Original comment by Lunatik.CN@gmail.com on 9 Feb 2010 at 12:56

• Changed state: Questionable

[GoogleCodeExporter]

Here's 2 reasons for this feature:
- It can be used to install a "secret" IOS, so Nintendo can't screw people over 
with
stubs anymore.

- I'm on system menu 4.1U, so I'm staying away from IOS60, but I'm using 
Priiloader
to make my system menu run on a fakesigned-enabled IOS.  Any IOS 36 or below, 
when
used as system menu IOS, gives ear-splitting highs when the system menu intro 
sound
comes on.  I can use Priiloader's silent system menu memory patch, but that 
would be
too quiet.  I'm having trouble finding an IOS that's not 60, and can be
ES_Diverify/ES_Identify patched so it can be used with Priiloader (IOS249 breaks
gamecube).

Original comment by lpq...@gmail.com on 10 Feb 2010 at 8:12

[GoogleCodeExporter]

To #1 - Nintendo can always screw people with Stubs. This is why we ALWAYS 
recommend
to NEVER upgrade from the System Menu. Also adding something like slot 
selection will
require a lot of changes to support it as the new DOP is all database driven 
and how
the IOS menu works all works off the database file. Installing into non slots 
will
not give you the option to uninstall unless I do a combo of IOS Scanning and 
Database
matching like I have in the new SysCheck code. But like I said it will require 
more
changes to support this as well.

To #2 - Few things here. You can run System Menu 4.2, it is safe to use and all 
that
is required is having IOS70 installed. Also Priiloader does not need the 
ES_Identify
patch. Daco actually uses the real signatures to make things work. He 
eliminated that
requirement in v0.30. However, you do need an IOS with ES_Identify patched for 
the
installer, but not for the actual priiloader. Like stated before, v12 is 
database
driven so it now knows what patches can be applied to the various IOS Versions.
Meaning it will tell you on screen what IOSes can be ES_Identify patched. 

All in all, I will think about this more, but I'm not going to promise it will 
happen
right away or at all.

Original comment by Lunatik.CN@gmail.com on 10 Feb 2010 at 12:05

[GoogleCodeExporter]

Ok I've been rearranging some code and it shouldn't be a big deal to implement. 
Just
take note that the way I'm going to implement is that you can only install to an
available slot. If a slot is not available you will have to go to the IOS menu,
delete it, then run the installer. I'll get this into Beta 7 to maybe tomorrow 
if you
would like to help me test it.

Original comment by Lunatik.CN@gmail.com on 20 Feb 2010 at 10:33

• Changed state: Accepted
• Added labels: v12

[GoogleCodeExporter]

Original comment by Lunatik.CN@gmail.com on 20 Feb 2010 at 10:33

[GoogleCodeExporter]

Now Available in v12 Beta7

Original comment by Lunatik.CN@gmail.com on 21 Feb 2010 at 3:49

• Changed state: NeedsTesting

[GoogleCodeExporter]

Original comment by Lunatik.CN@gmail.com on 4 Mar 2010 at 4:19

• Changed state: Done