WiredWorm said:
Thanks carbonyle - that worked a treat.
I've got two modded Wii's - one of which will load a particular title with no issues and the other reports an 002 error. I'm therefore assuming that the Wii which won't load the game possibly has an outdated IOS and hence the game won't launch.
I've taken the version numbers from the CSV and i've found a few of them which are lower than the version specified in the update.inf file which I extracted from the ISO using WiiScrubber. The affected ISO's are: 11, 13, 15, 20 and 22.
What I don't understand is what versions of file the various cIOS installers provide. There seems to be multiple revisions of the same cIOS - do these just provide the same IOS with different patches applied or do they give totally different IOS's?
I'm trying to identify what I would need to install to get my IOS's up to the correct version AND in a patched state.
Any clues anyone can give would be appreciated.
Cheers
Wired
cIOS's always generally install over IOS249 and have nothing to do with any of the official IOS's on your system in particular. Different revisions are based off of different base IOS's though. Really old ones from Waninkoko were based off of IOS37, more recent ones than that were off of IOS36, and the last couple of revisions are based off of IOS38. Whichever one you installed last will be the only one you have and will just write over any previous cIOS revision in IOS249. It doesn't really matter which one you use, but it would be better to have some relatively up to date stable one such as rev10, rev13a, or rev14.
Normal official IOS's don't really need to be patched aside from like IOS60 on 4.0/4.1 so you can play vc wad's from the sd card menu, and maybe IOS36 with the trucha bug and ES_Identify so you can install preloader. You can use dop-IOS v7 to run through all of your IOS's and check if there is a more recent version than it out and have it install the newer version of it as well. You can also use it to patch the trucha bug into any of these IOS's after updating them, but it isn't really necessary outside of IOS60, and IOS36 with the ES_Identify patch as well. Also don't bother updating IOS's that will update to stub IOS's like IOS 30/50/51 and such (ESPECIALLY if you aren't on 4.0/4.1 already.) You also may want to skip updating the IOS that the HBC is running off of to be safe or at least save it until after you update the others and see if it fixed anything. It may make the HBC stop working and you would have to reinstall it, but I'm not positive on that.
Also what are you loading the games through to get the 002 error? Do you have a modchip in them and are running them through the disc channel or are you using CIOSCORP or something? (If you have CIOSCORP don't do the above).
Edit: Ok so you're using CIOSCORP now. Just to explain what it is, CIOSCORP isn't anything official. Someone basically just took every official IOS on the system and modified it with the dip module from different cIOS revisions and has you install them over every normal IOS on your system. I believe this recent CIOSCORP made the version numbers of all of the IOS's maxed out to make sure it works on boot2v4 Wii's. As a result an official update will not remove CIOSCORP as before and so the only way to remove it is to physically install normal IOS's over every one of them. The only purpose of CIOSCORP is to be able to launch backup games from the disc channel without needing a mod chip. It isn't something necessary to update to by any means and having the most up to date official IOS's and a recent cIOS revision (such as that rev14 installer you have) should be enough to play most games through good backup loaders like NeoGamma R7 or most USB loaders.
The most important thing to know with CIOSCORP is to NEVER UNINSTALL ANY OF IT'S WAD FILES. If you want to get rid of it you install normal IOS's OVER all of your IOS's.
