IOS Version patched 002 games(hopefully soon)

Note: This is only relevant to disc loading, on usb loading you have additional problems! The point of all this is to get these games to work from disc without overwriting regular IOS.

With NeoGamma R8 beta 17/RC1 i did my best to fix 002 error even if the game was IOS version patched and there's an IOS Reload. As you still get 002 error on starting one of the Metroid games with an IOS Version patched Metroid Prime Triology disc, i think we reached the point where it is safe to say there there isn't an easy solution for this from the loader side.

Let's gather the info we have about this problem:
- The 002 error is a check if the IOS version stored at 0x80003140 is higher than the IOS version at 0x80003188. The value 0x80003140 is written by the IOS reload and the value at 0x80003188 is written by the apploader.
- If an IOS Reload is done, the value at 0x80003140 is updated with the version & revision of the loaded IOS
- The value at 0x80003188 has no connection to the IOS to use value inside the tmd. The value inside the tmd is the one that is used by the disc channel and patched with the IOS Version patcher. This explains the 002 errors on IOS Version patched discs on disc channel.

NeoGamma now writes this to fix 002 error if the value at 0x80003188 and inside the tmd do not match:
*(u8 *)0x80003141 = ios;
*(u8 *)0x80003189 = ios;
*(u16 *)0x80003142 = 0xffff;
*(u16 *)0x8000318A = 0x0001;
ios == ios requested inside the tmd. Basically it says that the IOS to expect is the IOS that is specified in the tmd with revision 1. When the IOS Reload happens, exactly that IOS is loaded and it should be safe to assume it's revision is >= 1.

But we still get 002 error, this leads to one of the following conclusions:
- The memory at 0x80003140 gets overwritten with other info as expected(very unlikely)
- The memory at 0x80003188 gets overwritten with the "correct" info(very likely and bad)
- The 002 error works differently as expected(hopefully not)



Long story short:
Somewhere on the disc there's the info stored which IOS to expect and we need to patch that along with the tmd. It's IOS Version and IOS Revision, it should look like this(in theory as that's what gets written to 0x8003188):
0x004D1E61 for IOS77 revision 7777
If we patch that to 0x00F90001, the disc patched to use IOS249 shouldn't throw any 002 errors anymore.

New softmod compatibility list/thread?

Now with all compatibility lists(i know...) completely outdated, in my eyes it would be a good idea to write a new one. Since most games just work from disc and usb without any problems, i would say concentrating on the problem games and descriptions on how to get them to work should be the way to go.

I don't want to update my old thread with it. I'm lazy, and i think i have a way of expressing things in a way many people don't understand. But i want to contribute. In my eyes the best would be if one of the guys who write guides do it, and everybody else writing guides, helping people and just knowing stuff contribute to it.

Hmm, maybe a combination of compatibility list and additional info in a thread would be good. I'm thinking of something like putting games in categories, like 002b games, IOS Reloading games with .dols(working with alternative .dol loading), IOS Reloading games without .dols, updated 001 error(won't find pattern with Generic Wii Patcher) ...

I think building that list would be hell, as it would require lots of infos that need to be gathered especially for the list, but in my eyes it would be worth it.

Maybe the edit access should be restricted to people who know what they are doing to avoid missinformation in the list. And if a thread should be the way to go, i think we should do a poll to decide who creates it.


Sorry for the confusing layout of my text, i'm just writing my thoughts down.

Open PS2 Loader mod

I don't know how many of you know about it, but there's an open source loader for Playstation 2 that loads from usb and network now:
http://bitbucket.org/ifcaro/open-ps2-loader/overview/

It's impossible for me to contribute to the original project for reasons i don't want to discuss here, so i have to create a mod with my changes. Until now i only changed network code, but i think it didn't went too bad and usb will always be awfully slow.

V1:
http://www.mediafire.com/?tzhnfzmnjzv
V2:
http://www.mediafire.com/?1jm0zn1wozj
V3:
http://www.mediafire.com/?hi0zqgdzge1
V4:
http://www.megaupload.com/?d=STMN09ZO
http://rapidshare.com/files/325344806/open...rmodv4.zip.html

Readme of V4:


All in all, this mod loads games faster(but not much) via network than the official version does, while using slightly less memory which could increase compatility. If anybody is really interested in details about the changes, ask.

Update: This version is totally outdated. The original project got internal HDD support and network loading on ps3s(among other cool stuff) in the meantime. But there's a bug in the "latest" revisions related to network loading which reduces my interest in improving the mod. On my ps2 i can hardly get a game list when loading from network, and then in most cases the game loading freezes on a white screen. When that bug is fixed, i will continue my tuning attempts.
Update2: I fixed my white screen problem. Somehow my games got corrupted and i needed to reinstall them. But i still have the network freezing issue. I think i can continue my attemps by adding delays to the network init function or undo the change from r144 to r145.

@Brawl+ players

Are there any bugs in Brawl+, any minor or major glitches? I'm asking because Gecko OS 1.9.3 may have fixed some bugs:
http://wiird.l0nk.org/forum/index.php/topic,3228.0.html

cIOSrev15 released and it's broken yay

I told Waninkoko about the bug like 100 times, last time yesterday with the latest beta version i got.

The bug i mean is the following:
If a loader writes the correct value to address 0x80003184, the 001 check fails.

The result of this is:
001 error on disc channel (this means, among other things, most likely no cioscorp possible with rev15)
001 error on discs in NeoGamma and SoftChip
green screen freeze on usb(and most likely sd too) with NeoGamma

I will not release a "fixed" version of NeoGamma for rev15!

With this issue i don't care about possible still broken wifi and low sdhc compatibility.


Ok, since Waninkoko seems to have left the scene, let's try to get an overview of what we have got:

cIOSrev7:
Plays only discs, no dual layer, does not work on new Wiis. (LU64+ issue) But nothing else to complain

cIOSrev8:
Does not play new 001 games, does not play 002b games, only discs, does not work on new Wiis, maybe not disc channel compatible*

cIOSrev9&10:
Does not play new 001 games, does not play 002b games, does not work on new Wiis

cIOSrev11:
Does not play new 001 games, does not play 002b games, maybe not disc channel compatible*

cIOSrev12:
Does not play new 001 games, does not play 002b games, not disc channel compatible*

cIOSrev13a:
Does not play new 001 games

cIOSrev13b:
Does not play new 001 games, does not play 002b games

cIOSrev14:
does not read the end of the 1st layer causing trouble for all DL games and maybe very big SL games

cIOSrev15:
not disc channel compatible*


*Also means not NeoGamma and SoftChip compatible see rev15 bug.