Hacking Code Dump / Stack Dump with uLoader while scrolling games.

[devinlsu]

I am a new uLoader user and am running into a problem. I am using:

4.2U
uLoader 5.0C
IOS202[60]-v65535 (v5 of Hermes cIOS)
IOS222[38]-v65535 (v5 of Hermes cIOS)
IOS223[37]-v65535 (v5 of Hermes cIOS)
IOS224[57]-v65535 (v5 of Hermes cIOS)
IOS249[57]-v19 (rev19 of Waninkokos cIOS)
IOS250[38]-v65535 (rev19 of Waninkokos cIOS)

When I scroll my games I get a code dump / stack dump when I get to the letter "G" games. I have deleted the config file off of my wbfs drive and even tried a new drive. I really want to use uLoader to play the Guitar Hero games, but get the code dump / stack dump before getting to the screen with them listed. Can anyone please help? Thanks for all the work!

 

[fridgee]

Same Problem here, code dump on the last page. I'm not sure about the letters the games srtating with. I think it has sth. to do with a broken cover in one of the games. but i don't know how to delete them without getting them displaed in uloader.

 

[devinlsu]

I do not have any covers added to my games in uLoader though. I have looked all over and can't find any information on how to fix this. Mine dumps on the third page when scrolling to the right, or the 5th page when scrolling from the left. It is always the same page though. Hopefully someone can help out.

 

[Juanmatron]

uLoader is THE MOST stable USB Loader! Rarely you will see a Code Dump.

 

[pepxl]

simple, if its code dumping on the same page every time then its down to a corrupt game being read and uLoader starts choking

 

[josete2k]

You should use the integrity check option in wbfs_win.

 

[devinlsu]

Thanks for the help guys. I ran the integrity check and it is still crashing on the same page. Any other ideas?

 

[fridgee]

same for me, all games are verified. It's also the third page where it chrashes. If i Remove every Game from the third page everything is fine.
also wit verify finds no errors. If i put them back -> uloader code dump. All the games are working in cg loader and usbloader gx

 

[devinlsu]

Fridgee, you and I are having the exact same problem. Mine dumps on page 3, regardless of which way I scroll to it. My integrity check with wbfs_win revealed no problems and usbloadergx works. Looks like the next thing is to remove all the games from page 3, then add one by one to see which is causing the code dump / stack dump.

 

[josete2k]

5.1D released, please try it.

 

[Robj1969]

josete2k, do you have a changelog for 5.1 D?

 

[fridgee]

Same Problem with 5.1D. I think it's a problem with the covers included in the game. Is ther any possibility to read/delete/verify thos covers with an external Tool?

 

[pepxl]

try moving/deleting the _CF___ game ID from your HDD, doing this will remove/revert all covers and settings to default

 

[fridgee]

I don't think so. I removed this entry man time. The covers are still there. I read somewhere in the changelogs that the covers are stored in a free part into the game.
I will take a look into the wbfs partition with wwt when i am at home.

 

[devinlsu]

Any luck fridgee? I have deleted the _CF___ game ID and updated to 5.1D and am still getting the dump on page 3.

 

[fridgee]

No luck. wwt verifies all my games. deleting the _CF__ game don't delete the covers, cause thy are strored inside the games.

 

[pepxl]

i just tried all version of uLoader up to 5.1D and i can say i dont have the DSI error on any page, so the only conclusion i can give is as before, its either a game uLoader is struggling to load or the cover is corrupt and uLoader sh*ts bricks when it tries to load, try moving the games from P3 then add one at a time until it DSI's

 

[fridgee]

This would be the solutiion. But for technical reasons, How do I delete such a cover from a game? I took a quick look into the uLoader sources, but i didn't find how the covers are stored into the games.

 

[devinlsu]

After a while of trial and error, turns out that Guitar Hero 5 was the culprit. I removed it and everything is working just fine. Any ideas on how I can check the integrity of the iso to see why it caused the problem? Thanks for all the help ya'll.

 

[fridgee]

try wit --verify name.iso from wiimms tool set.