HBC+Apps = Jumpy Cursor/Unresponsive: Updates Fail! Maybe IOS222 at fault? HELP!
So some background first....
I have a 3.4E Wii with HBC 0.6. I put IOS222 (Hermes) onto it to bring it right up to date as indicated here:
Everything was running fine and then for no reason I'm aware of, one day I noticed the cursor was jumping around rather than scrolling smoothly. It was doing this in my Configurable USB Loader (release 60 - 222mload) and NOT in the main Wii System menu or in any games. I tried a few different versions of Configurable USB Loader, older and new Beta's, but they were all the same as regards the pointer operation.
I tired a different Wii remote and recalibrated the sensor bar / cleaned it etc. but this made no difference.
I cleaned the sensor bar too and checked that all the infrareds were working using a digital camera phone to see them - all looks good and seems to be working, and anyway, it is fine in the Wii System menu and games.
I then noticed that this strange behaviour was happening in all HBC apps, so USB Loader GX, main HBC, Loadmii etc. Anything that sits on top of the HBC has this problem. Bootmii does not, I guess because it runs at a lower level and does not sit on top of HBC. Correct me if I'm wrong on this please.
Loadmii v0.3 is particularly sluggish, which is nuts considering there is nothing more than some text on screen!
So I tried to update HBC from 0.6 to 0.8, and I tried this via two methods, the auto internet update and the Hackmii installer from an SD card. Both of these failed giving the following screen dump errors:
I read somewhere that this error happens because there are USB devices in the back...so I removed them all and tried again but got the same memory dump page. :(
Can anyone explain what is going on here. I want to be able to update everything and get rid of this annoying jumpy cursor problem and unresponsive HBC apps. It is basically unusable in its current form.
Now I'm no expert, but could this be because I have replaced standard IOS36 with Hermes IOS222/223? But then this does not explain why it has worked fine for months on IOS222/223.
Is there any way I can go back to a standard unhacked Wii and start over?? Although I'd rather not do this unless I absolutely have to.
Help please! :(