Hacking WAD Manager freezes remotes BEFORE IOS249

[Roads1]

People seem to say that their remotes often stop working upon selecting IOS249. Well, I can't even get there! The remote lights start blinking and never stop, and the remote doesn't work, right from loading it. This happens to me very often with different programs, and nobody seems to have provided a solution for any.

What's wrong with it?

 

[JoostinOnline]

If it's a motion+ remote that's not working, I suggest you try YAWMM EN.

 

[Roads1]

If it's a motion+ remote that's not working, I suggest you try YAWMM EN.

Tried it, and it actually works with my remote (it is Motion+), but when I select IOS249, it doesn't do anything. I don't mean it freezes, I mean it doesn't do anything. The lights blink (then stop, as if I were turning it on), then nothing happens.

 

[JoostinOnline]

If the remote lights turn off and on, that means it has loaded IOS249. It's over a whole month since I worked on that (which sadly is a long time when my memory is concerned), and I don't remember how everything is designed.

 

[Roads1]

But... then what? This is a WAD Manager, not a program to load IOSes and not do anything. The tutorial for installing USBLoader GX (what I need it for) mentions selecting a WAD, something that this doesn't do.

The lights turn off and on, and further attempts to do anything make the lights blink like that. I didn't notice it the first time. What I don't get is why there's no indication that anything happened other than that, and why it gives me nothing to "Continue" to.

 

[JoostinOnline]

Try pressing A.

 

[Roads1]

That's what I did. I should've mentioned it. I know that some people can't even realize that their PC won't turn on because it's not plugged in...

 

[JoostinOnline]

Well try loading another IOS and see what happens.

I wish I could test this on Dolphin, but it won't run properly there. More than that, I wish I had access to my Wii these days.

 

[Roads1]

Okay... I tried doing IOS250, and upon pressing A, it selects IOS249, and similarly does nothing else. Then I tried 222, but it had the same reaction. What other IOSes will work with USBLoader GX?

EDIT: Is IOS249 something that needs to be installed? I'm not sure if I have it or not.

 

[JoostinOnline]

This is about a wad (probably a GX forwarder channel), not GX. It doesn't matter what IOS that GX uses.

I have no idea why it's not working. I'm looking at the source code now and it should continue. Post a SysCheck following the guide in my signature.

 

[Roads1]

The original, and the extra "solution" to this problem I'm about to mention, give me "Unable to initialize FAT file system."

EDIT: On the off-chance that it would work, I tried installing 249 with the cIOS installer. It shut off my remote and didn't do anything. How long have Motion+ built-in remotes been out now? Two years, at least? How long does it take to make these things compatible?

 

[JoostinOnline]

Well not all motion+ remotes are incompatible. It's just a later set of them. About a year ago a fix was released. All you had to do is recompile the app with the latest libogc (assuming it was compatible with some of the other changes), but by then support for most apps had been dropped. The Wii scene is dying, and most devs have just quit.

So you don't have any regular remotes? How did you install the cIOS before?

 

[Roads1]

I got the Wii on Christmas 2011. All my remotes are Motion+. I might not have even installed it before; all my homebrew is emulators so far.

And now... about the "FAT system" error? What causes it?

 

[JoostinOnline]

1. Then those IOS you keep trying to load are likely all stubs. I'd still like to see that SysCheck.
2. Do you have an SD card inserted?

 

[Roads1]

No, I'm using an external USB HDD. No SD card.

 

[JoostinOnline]

SD is always better for homebrew. Did you select USB2.0 as your storage device?

Still waiting on that SysCheck.

 

[Roads1]

I said, I get an error that I can't seem to find a way around. Pushing A to view the report doesn't work, and no file is generated that I can find in the HDD.

And it's also USB 3.0. Is this bad?

 

[JoostinOnline]

I said, I get an error that I can't seem to find a way around. Pushing A to view the report doesn't work, and no file is generated that I can find in the HDD.

And it's also USB 3.0. Is this bad?

Wait, the FAT error you were talking about is in SysCheck?

Your HDD might not be compatible with some homebrew. This is why SD is always better.

 

[Roads1]

Well, the HDD is mostly for storing game backups for the USB loader. I have a 2.0 USB memory stick that hasn't failed; can that be used simultaneously for running the actual homebrew, with the HDD for storing the backups?

And yeah, that FAT error was in the SysCheck. Should've been clearer.

 

[JoostinOnline]

Well, the HDD is mostly for storing game backups for the USB loader. I have a 2.0 USB memory stick that hasn't failed; can that be used simultaneously for running the actual homebrew, with the HDD for storing the backups?

And yeah, that FAT error was in the SysCheck. Should've been clearer.

Why don't you use the SD card you used for your original softmod?