Looking for Explianation: Can't Load Mario Party 8 or Wario Ware:SM BoomBlox
this is just bugging the s.. out of me..
I have a Wii from early 2008 with a D2Pro9 installed (soldered by myself) and I have some backups. I am on HW v2.0 and FW v1.7 on my chip and my Wii system is 3.3U
The problem is with Mario Party 8 and Wario Ware Smooth Moves, they both load in the disc channel and look fine then when clicking start to play they go to black screen the wii remote powers off and the system hangs indefinitely. I have to hold power button for about 10 seconds to power it off. Power back on and it will boot any other disc original, backup ect..
I thought maybe they were problem discs because they were from the PAL region.. So I patched them with WIU v1.1 to NTSCu reburned and still exact same symptoms.. load in Disc Channel and then to blank black screen when I click start, wii remote powers off.
I am thinking maybe it's the fact I have 3.3u Wii update but SSBB on a DVD5 goes straight to ''an error has occurred blah blah blah'' message (i am aware that it won't work on 3.3u) At this time I can't downgrade as I don't have Zelda anymore and I don't have a internet connection for my wii I am stuck on dial up (because of where I live). I also do not have the homebrew channel or any homebrew or wads installed.
Lastly I have BoomBlox NTSCu region and it won't load at all or error it just goes in and does nothing.. It sounds like it is reading it (you hear the laser make the um zirp sound) and then just spins indefinitely with no errors or display in the disc channel. I does however seem to make the Wii itself act funny for example it makes it hang when you attempt to go to data management or wii settings and has to be powered off. WIU confirms the ISO (which I made from disc) is indeed BoomBlox, is indeed NTSCu and is valid size. I am just writing this one off as a bad ISO.. but maybe not?
At this point I just want to understand, I have learned alot from reading but can't find anything like this..
not sure if this should be here but thought hey it might be chip specific prob?