[harroway]

i have created the wads, but they are named without the last '2' in the filename...so d2x instead of d2x2. does that mean i did something wrong?

i installed 249/56 and 250/57. in  wiiflow 2.1 the controller syncs immediately but in the 2.2 beta it takes extremely long. is that normal?

thanks!!

[XFlak]

You didn't do anything wrong, I renamed the wads and added a "2" at the end so I know that they are d2x v2 and not v1. This will be the standard naming convention after the next  ModMii update. But the only difference between the two is just the name and nothing else (assuming u correctly replaced the EHCI lag fix module and/or the hashes match the ones I provided earlier)

[harroway]

You didn't do anything wrong, I renamed the wads and added a "2" at the end so I know that they are d2x v2 and not v1. This will be the standard naming convention after the next ModMii update. But the only difference between the two is just the name and nothing else (assuming u correctly replaced the EHCI lag fix module and/or the hashes match the ones I provided earlier)

thanks for your quick answer, i did everything according to the instructions and the files on the first page, so the wads must be the v2 versions then. but how about the long (10 seconds or so) sync with wiiflow 2.2?

[davebaol]

i installed 249/56 and 250/57. in wiiflow 2.1 the controller syncs immediately but in the 2.2 beta it takes extremely long. is that normal?

We have already fixed the wiimote synch delay issue in Wiiflow, I hope.
Try the version r304: http://code.google.com/p/wiiflow/downloads/list

[Yuan]

i installed 249/56 and 250/57. in wiiflow 2.1 the controller syncs immediately but in the 2.2 beta it takes extremely long. is that normal?

We have already fixed the wiimote synch delay issue in Wiiflow, I hope.
Try the version r304: http://code.google.com/p/wiiflow/downloads/list

Most the time it really syncs instantly (starting from a forwarder dol/forwarder channel). Rarely it still syncing at HDD blinking, and when I start wiiflow from HBC it only syncs at HDD blinking.

But I think it is a wiiflow issue.

[harroway]

i installed 249/56 and 250/57. in wiiflow 2.1 the controller syncs immediately but in the 2.2 beta it takes extremely long. is that normal?

We have already fixed the wiimote synch delay issue in Wiiflow, I hope.
Try the version r304: http://code.google.com/p/wiiflow/downloads/list

Most the time it really syncs instantly (starting from a forwarder dol/forwarder channel). Rarely it still syncing at HDD blinking, and when I start wiiflow from HBC it only syncs at HDD blinking.

But I think it is a wiiflow issue.

when i use the 304/249 wiiflow i have the sync issue, when i use the old 2.1 wiiflow it syncs immediately. i start wiiflow through the hbc.

its not a big thing, i just assumed it was fixed

[steve-p]

does  modmii need any crap like .NET or VB runtime etc. ?

[brausm08]

does modmii need any crap like .NET or VB runtime etc. ?

.NET 3.5....

[hong0098]

Maybe... who knows...

have rev21d2x base58?

[davebaol]

No it doesn't exist because cios based on 58 doesn't use the ehci module fixed by d2x.

[Etheboss]

I actually stopped using Wanky's cIOS's.

I honestly dont care about cIOS's. I got all my games legally owned. I hate using discs just for the fact that I will eventually burn out the laser, but I would rather burn out my laser instead of using anything from fail waninkoko. That guy has screwed up more thing irresponsibly than anyone else in the scene.

Hell, bootmii/the hackmii installer has not bricked a single console. How many consoles has wanky bricked from his uneducated carelessness? Quite a lot. I am Anti-Wanky at this point.

not to mention all the ps3s he bricked too

If you are really want to flame Wanin, go to his twitter,blog or IRC, don't do it here, these guys at least trying to improve on Wanins cios...this can only be encouraged...

Edited by Etheboss, 04 February 2011 - 01:33 AM.

[bulletmark]

The procedure given in the OP here does not work for me.

After step 10 I see a couple of "file already exists and has been verified, skipping download" messages quickly wiz by for my cios, 249dx56 and 250dx57. Two wads are listed, cIOS[56]-v21d2x.wad (Valid) and cIOS250[57]-v21d2x.wad (Valid). I do not see the "invalid messages" mentioned in the OP and I see that the final wads produced in my COPY_TO_SD folder still have the name, date+time, and hash of the v21dx2 wads from a few days ago.

[davebaol]

Remove them from that folder.
If  ModMii finds the file and they are valid then it doesn't download them once again.

[bulletmark]

Remove them from that folder.
If ModMii finds the file and they are valid then it doesn't download them once again.

I see you updated your instructions after my post but I suggest you need to clarify that the user MUST delete all files in the COPY_TO_SD folder before doing the download. After doing this, I see the download worked and my new wad files were built.

There will be plenty of people who have followed these instructions exactly, as I did, but have not realised that they have just reinstalled the original v21d2 wads.

Thanks for your work.

Edited by bulletmark, 04 February 2011 - 02:43 AM.

[justmike]

Thanks again guys!!