Fivemagics said:
Can't be bothered re-hacking it. I'm not familiar with ModMii yet, so it could possibly not work on the first time. And like I said I have plenty of games working, so I don't think it's something related to a cios. Besides, I got the Pal version to work now.
I think it was related to a bad iso, or language/video setting.
My confusion comes from the the ios and cios terms. People online seem to confuse them or don't specify it correctly. For example the installer I used is cios38 rev14. Also installed IOS236 following a guide on wikidot(at least that's what they called it). From what Wever says, it doesn't seem to make any sense. Besides I haven't been able to find any decent information on what's a ios and a cios and how they work.
Either way it's working fine now.
The problem with the wii hacking scene is, it moves quickly so a lot of info out there is redundant hence why people keep directing you to mod mii as it is complete and current as of now.
Best thing for you to do is read up on wiibrew how the wii actually works from the moment you press power, then you can understand it a bit easier.
An IOS is a slot containing code that is essentially the wii's operating system, there are 256 of them in total, and each one if completely independant. Everything that is ran on the wii is done through IOS. When you are in the system menu, that is running in an ios, when you then click on a game, it closes the system menu IOS and opens the IOS that game wants it to.
Now obviously nintendo never intended on piracy being possible, so any code which has not been signed with nintendo's signature or any dvd-r's going in are handled by the IOS to not run.
This is where custom IOS' come in. A custom IOS is a nintendo official IOS that has been rewritten by a hacker or group of hackers to have their own custom versions (obviously to get rid of checks that stop the system booting stuff WE want it to).
When you first hack a wii, the very first step is running an exploit. Being a closed system, for all intents and purposes, the wii should not ever get in the state where custom code can be ran. This is where the exploit comes in, which would be your indiana jones, smash stack, bannerbomb etc...
Once the exploit has been ran and the homebrew channel is installed, we then have somewhere we can boot custom code. But, we are still running in IOS and so there is no custom code telling the wii how to run and so it will still continue to not boot dvd-rs. Now you run a custom ios installer, here's where it gets a little tricky to understand as there are many different custom ios' out there and all have different functions.
The first one you installed, 236. The only reason this one is installed is to allow you to install the main one in 249. 236 will not boot dvd-r's, it is a basic custom ios designed just to be able to allow stuff to be installed.
Whatever guide you are following is VERY old as cios38 rev14 came out in 2009!