Why does it make sense to treat half of the major versions of IOS (the monolithic ones) one way, and half the other way? Either you believe that there is value in maintaining the existing minor version number, or you don't.
Hell, why not replace all versions of IOS with one patched version with minor version 7?Forgive my memory, but the lower Ios's have only 1 or 2 Apps were the newer ones contain serveral apps, the Higher IOS's was easier to patch by hand in adding the Dip module with Just replacing the App1.
Were the Lower it was just easier to replace the entire Ios with the CIOSrev7, cause in the higher IOS's they contained more stuff like USB stuff for the Newer Games like Rock band, thats why they got special treatment, See the thing is no coding got used in this Mod, Thats why i called it a Mod not a hack.
cIOSCORP commits two "crimes", neither of which is about warez:
1) It replaces several versions of IOS with a different version, only because it was "easier" to do. I don't fully understand why there are so many different major versions of IOS -- comparing two binaries that large is non-trivial -- but I assume there's a decent reason, most likely that older games do not run reliably on newer versions of IOS. Yes, yes, I assume you tested this out and it seemed to work on all the games you tried, but it's still awful to just overwrite code you don't understand and hope it works.
2) With the modular IOSes, it changes the minor version number ... this is kinda silly (it defeats the purpose of versioning), but I could see the appeal of cranking all of the minor versions up to 0xFFFF so that none of Nintendo's updates would overwrite it. I was shocked to see that you chose the opposite -- 7 -- such that ANY attempt at updating would overwrite these IOSes (but I suppose updates are disabled via other means). If you wanted to label these IOSes in some way so that people knew what they were, you did a poor job at doing so. There are plenty of better ways; Waninkoko modifies the 64-byte "label" content file with his name and the version number. We store the BootMii version number in an unused spot of the TMD. Use your imagination.
9th_Sage said:
wolffangalchemist said:
cioscorp is NOT destructive the creators of bootmii just don't like it hence why they try to make there installer not work with it installed.
I just want to say something, since I think some people are missing the point Bushing was (I believe, so forgive me if I'm wrong) trying to make. The things the HackMii installer does, could probably screw up your Wii pretty bad. This is why Twiizers tests the hell out of things (as well as adds in all sorts of checks to their installer). Now, with cioscorp, the installer doesn't know what the hell they are, so rather than install and possibly screw something up, it refuses to do so. Since they are an unknown, it can't run code on them and expect results to be exactly how it wants them.
This is correct. The HackMii installer has some logic in it to decide what version of IOS to use. If possible, it uses an "old" (minor) version of IOS, one that does not have the strncmp bug patched and /dev/flash blocked -- the way it does this is by checking each major version of IOS's minor version against a list of the last usable versions of each. If it doesn't find an "old" version, it checks to see if it has exploit code for a specific version of a specific IOS (we picked one for 3.4 systems, and one for 4.0 systems), and if this fails, you get the "well then suck it" message -- because it's supposed to mean that we need to go download new versions of IOS and painstakingly find new exploits, and just the thought of that makes us grumpy.
After we released the first beta of the HackMii Installer, we got a bunch of logs of install failures where the installer tried to use an "old" (hacked) version of IOS, which was really a newer version of IOS with a modified version number. Sure, you might patch the hashchecks out, but are you going to re-enable /dev/flash? We can't make any assumptions here, because not everyone uses the same exploits we do -- and trying to use them results in strange error codes that are painful to troubleshoot, or worse yet, silent hangs. We started to notice a pattern of strange version numbers, so we went and added a check to make it skip any patched IOSes.
It turns out that this isn't really a problem for anyone ... except people with cIOSCORP installed.
QUOTE(wolffangalchemist @ Jun 11 2009, 04:13 AM)
@
Xdqwerty:
@
BakerMan:
