Hacking cIOSX rev21d2x: Yet Another Hot Fix!!!!

[digdug3]

There's only one relevant difference between v3beta6 and v3final.
v3beta6 has logging on while v3final has logging off.
And that's weird, but it makes really the difference.
In fact v3beta6 can create the save file for games like FFCC My Life as a Darklord, but if I recompile v3beta6 without logging then that game shows the error message "Can't create the save file" or something like that.

Maybe initialisation or timing problems? Because the beta6 is initializing the fat module before the game to create a log?

 

[Bulloch]

Woohoo, I finally got my old usb hdd enclosure working with Configurable USB Loader using 249d2x58! Thanks a lot for increasing compatibility with this cIOS, I almost bought a new external hdd.

 

[Lacius]

Woohoo, I finally got my old usb hdd enclosure working with Configurable USB Loader using 249d2x58! Thanks a lot for increasing compatibility with this cIOS, I almost bought a new external hdd.

Is there a reason to use 249d2x58 instead of 249d2x56?

 

[Bulloch]

Woohoo, I finally got my old usb hdd enclosure working with Configurable USB Loader using 249d2x58! Thanks a lot for increasing compatibility with this cIOS, I almost bought a new external hdd.

Is there a reason to use 249d2x58 instead of 249d2x56?

To be honest: I picked it at random, I don't know what the advantages of the different bases are. I'm still a bit new at this...

 

[x4mer]

Base 58 cios doesn't use the cios USB 2.0 code, it uses the Nintendo USB code in base 58. It's the only base that doesn't end up using the cios USB2 code, so I would bet that your HDD is working now because of the base, not because of d2x. If you had used Wanin rev21 with base 58, you would likely find that to work too.

Problem is base 58 doesn't work (well) for many things.

 

[XFlak]

One question though, why didn't you change the version numbers of the cIOSes in the 250 slots to 21, because it is already known that the version number can give problems with Mighty Channels..

For anyone who wants to change ModMii's default d2x cIOS250's to be rev21 instead of rev65535 they can copy and paste the following text into a DBUPDATE.bat and save it to the following directory:
{directory where ModMii.exe is saved}\temp\DBUPDATE.bat

Spoiler

CODEif /i "%wadname%" NEQ "cIOS250[37]-v21d2x3" goto:skip
set ciosversion=21
set md5=2660064ddd223b360d5987f1c13b1627
set md5alt=%md5%
:skip

if /i "%wadname%" NEQ "cIOS250[38]-v21d2x3" goto:skip
set ciosversion=21
set md5=ee5f927ad2de6016f199da570f172195
set md5alt=%md5%
:skip

if /i "%wadname%" NEQ "cIOS250[56]-v21d2x3" goto:skip
set ciosversion=21
set md5=93bd371c6052e7f9841fda5e2e7eebdf
set md5alt=%md5%
:skip

if /i "%wadname%" NEQ "cIOS250[57]-v21d2x3" goto:skip
set ciosversion=21
set md5=0cf62ae35b1e09d7644a2aa8577e6155
set md5alt=%md5%
:skip

if /i "%wadname%" NEQ "cIOS250[58]-v21d2x3" goto:skip
set ciosversion=21
set md5=81f8decece261ce6a0367d8d3a37e232
set md5alt=%md5%
:skip

I can have ModMii build this file when checking for updates if there is a general consensus that this is what should be done.

So whats the verdict? Should I have modmii do this for everyone? Has anyone tried it yet?
???

 

[Lacius]

To be honest: I picked it at random, I don't know what the advantages of the different bases are. I'm still a bit new at this...Yes, 249d2x56 has the best compatibility; it works with roughly 99% of games. 250d2x57 is usually installed to cover the remaining 1% (the ones that can be fixed with a different cIOS, anyway).

Base 58 cios doesn't use the cios USB 2.0 code, it uses the Nintendo USB code in base 58. It's the only base that doesn't end up using the cios USB2 code, so I would bet that your HDD is working now because of the base, not because of d2x. If you had used Wanin rev21 with base 58, you would likely find that to work too.

Problem is base 58 doesn't work (well) for many things.This is what I thought. I just wanted to be sure I didn't miss something with the introduction of 249d2x58 v3. Thank you.

QUOTE(XFlak @ Mar 7 2011, 06:43 PM)

So whats the verdict? Should I have modmii do this for everyone? Has anyone tried it yet?
???

Lacius votes yes. I could also see the rev21 label being very beneficial when looking at sysCheck reports. Too bad there isn't an easy way to convey the fact that it's d2x v3 in the version number.

 

[troy512]

Lacius votes yes. I could also see the rev21 label being very beneficial when looking at sysCheck reports. Too bad there isn't an easy way to convey the fact that it's d2x v3 in the version number.

how about something like this:

2263
say d 2 X and the numbers 2 2 6 with v3 at the end

or

42243
d=4 2 x=24 v3

or

something similar anyone can think of, just change the last number to the version number

only problem i can see is that nintendo can overwrite an IOS which is not maxed out.

edit/

or release an entirely new cIOS which installs to different slots say cIOS246[56]-v1 (rev226) and cIOS247[57]-v1 (rev226). eventually the loaders can/will update to default to the new cIOS slots, besides they already have manual selection.

 

[davebaol]

I vote yes.
There's no reason why slot 250 should be maxed out IMHO.

 

[jesquinas]

One question for well understanding.Use v21 against v65535 is for making a difference between "official" wanin'cios and the modified cios of this thread?

Thx.

 

[pplucky]

One question for well understanding.Use v21 against v65535 is for making a difference between "official" wanin'cios and the modified cios of this thread?

Thx.

No, it's for Mighty Channels beta5 mod davebaol to be able to use the cIOS. Check here.

 

[Bulloch]

Base 58 cios doesn't use the cios USB 2.0 code, it uses the Nintendo USB code in base 58. It's the only base that doesn't end up using the cios USB2 code, so I would bet that your HDD is working now because of the base, not because of d2x. If you had used Wanin rev21 with base 58, you would likely find that to work too.

Problem is base 58 doesn't work (well) for many things.

Right, thanks for the explanation. I hope I don't encounter too many problems using this base then.
Will this cIOS with base 58 support other partitions than WBFS, since it uses Nintendo's USB code? (I'm going to try a few different partitions anyway, but I was wondering if it's possible in the first place).

-edit- FAT32 also seems to work.

 

[jesquinas]

One question for well understanding.Use v21 against v65535 is for making a difference between "official" wanin'cios and the modified cios of this thread?

Thx.

No, it's for Mighty Channels beta5 mod davebaol to be able to use the cIOS. Check here.

But mighty_channels_beta5_MOD_d2x_v3beta5.rar is written by davebaol?

Thx.

 

[davebaol]

I've just modified MC beta5 to support the new meta.xml arguments --partition and --path.
See http://gbatemp.net/t271798-mighty-channels...p;#entry3460986

 

[terryforever]

hi.
b4 tis i was using r19,

so, i thinking to install tis r21d2x
so, i follow all instruction,

after download n try install,
i follow wat u say, choose ios236, but i didnt have one,
then i try ios36, but it cant install the 2 wads,
so, i try ios 249,
then it install.

so, if i use ios249 to install,
will it got any problem??

 

[davebaol]

If installation succeeded why should you encounter any problem?
Any fake signed ios is good to install wads.
And all cios are always fake signed.

 

[XFlak]

I vote yes.
There's no reason why slot 250 should be maxed out IMHO.

So would you like me to change the version numbers of both 249 and 250 d2x v3 cIOSs to "42243", and v4 would be "42244" and so on?

 

[davebaol]

@XFlak
I was referring to this:

Spoiler

One question though, why didn't you change the version numbers of the cIOSes in the 250 slots to 21, because it is already known that the version number can give problems with Mighty Channels..

For anyone who wants to change ModMii's default d2x cIOS250's to be rev21 instead of rev65535 they can copy and paste the following text into a DBUPDATE.bat and save it to the following directory:
{directory where ModMii.exe is saved}\temp\DBUPDATE.bat

CODEif /i "%wadname%" NEQ "cIOS250[37]-v21d2x3" goto:skip
set ciosversion=21
set md5=2660064ddd223b360d5987f1c13b1627
set md5alt=%md5%
:skip

if /i "%wadname%" NEQ "cIOS250[38]-v21d2x3" goto:skip
set ciosversion=21
set md5=ee5f927ad2de6016f199da570f172195
set md5alt=%md5%
:skip

if /i "%wadname%" NEQ "cIOS250[56]-v21d2x3" goto:skip
set ciosversion=21
set md5=93bd371c6052e7f9841fda5e2e7eebdf
set md5alt=%md5%
:skip

if /i "%wadname%" NEQ "cIOS250[57]-v21d2x3" goto:skip
set ciosversion=21
set md5=0cf62ae35b1e09d7644a2aa8577e6155
set md5alt=%md5%
:skip

if /i "%wadname%" NEQ "cIOS250[58]-v21d2x3" goto:skip
set ciosversion=21
set md5=81f8decece261ce6a0367d8d3a37e232
set md5alt=%md5%
:skip

I can have ModMii build this file when checking for updates if there is a general consensus that this is what should be done.

So whats the verdict? Should I have modmii do this for everyone? Has anyone tried it yet?
???

And no, I've not tried it yet.

 

[troy512]

I vote yes.
There's no reason why slot 250 should be maxed out IMHO.

So would you like me to change the version numbers of both 249 and 250 d2x v3 cIOSs to "42243", and v4 would be "42244" and so on?

something which would be recognizable as a d2x cIOS and not a maxed out number or the standard 21.

edit/

even something as simple as 213 for v3 and 214 for v4 would be sufficient.

well considering the testing proofs successful.

 

[cambric]

I vote yes.
There's no reason why slot 250 should be maxed out IMHO.

So would you like me to change the version numbers of both 249 and 250 d2x v3 cIOSs to "42243", and v4 would be "42244" and so on?

something which would be recognizable as a d2x cIOS and not a maxed out number or the standard 21.
even something as simple as 213 for v3 and 214 for v4 would be sufficient.
well considering the testing proofs successful.

better be something like 21003 for r21 d2x v3, 21004 for r21 d2x v4, 23015 for next year r23 d2x v15....