[dagger2b]

For anyone wanting to install via a Wad here you go. This is the stock forwarder channel extracted using BlueDump.

[dagger2b]

mccooeye,

What error did you receive when installing the first one. Did you try the second one? If so did it also generated and error?

[dagger2b]

jhb50, I have been trying to PM you but my messages keep getting stuck in the outbox. So I sent you a email. Please check your email account that you use to send out your wiimc+ kit.

[dagger2b]

OK I can do that. What is the root for Wiimc+? Is is wiimc_plus or wiimc-plus? It will be a simple forwarder with no music or animation. This is because it needs to be different than the stock forwarder so users can distinguish between the two if both are installed.

[dagger2b]

OK but this is still easy to do. The code for the stock forwarder installer is private. However once the forwarder is installed you can dump it to a wad using BlueDump. Once you have the wad you can use CustomizeMii to inject your recompiled forwarder dol. You should also change the title id because if you don’t your new forwarder will overwrite the stock one. You can also use CustomizeMii to change the graphics files if you wish. I realize that this is not as good of a solution as having an installer and will require the end users to have a wad manager installed. However it will get the job done. I have the 1.9 forwarder already dumped to a wad. Let me know if you want it. Or if you wish I will make the changes and send you a wad. Let me know…

[dagger2b]

jhb50,

I was just browsing the forum and came across this old post. The forwarder source is available under libs within the trunk. The code is here…

http://code.google.com/p/wiimc/source/browse/#svn%2Ftrunk%2Flibs%2Fforwarder%253Fstate%253Dclosed

You would just have to change the path in main.c. Of course the forwarder channels would look identical on the system menu unless you changed the graphics. It might be confusing so better to change the graphics.

[dagger2b]

Hi gtfunding,

I am not sure if you are aware of this but the stock forwarder runs under IOS58. So you will still need 58 installed to use the stock forwarder even if you install it as a wad. The app also wants to use IOS58 for USB 2.0 support. I am not sure what happens if 58 is not installed when the app is run. I think that it falls back to using another IOS but then you do not get USB 2.0 support. IOS58 is a stock IOS provided by Nintendo. So I can not imagine that installing IOS58 on your customized system would cause you any problems. If you think it will then can please explain what problems you will have if you install 58?

[dagger2b]

Just tried it again and waited 5 minutes. Same result just black screen until I power down the drive or pull the cable.

[dagger2b]

I just tried this new version with my buddies drive. The test is run from HBC with no_ios_reload included in meta.xml. The result is the same as before. It just goes to black screen and does not display the error message. Pulling the usb cable or powering down the drive brings the message up immediately.

[dagger2b]

Rodries thanks for uploading the new beta for me. Well I have good news and bad. Here are my results…

The following tests were run with in meta.xml…
________________________________________________________

1. Running from USB

a. Launching app from HBC – Fails with black screen never displays “Could not find a valid SD or USB device”. 😮
b. Launching app from CF – Success the USB drive is found and mounted. 😀

The following tests were run without in meta.xml…
________________________________________________________

1. Running from USB

a. Launching app from HBC – Successfully runs and mounts USB. 😀
b. Launching app from CF – Success the USB drive is found and mounted. 😀

The wait loop has succeeded in allowing the device to be found and mounted when running from the forwarder. This is great news now he can run the forwarder. Thanks guys.

I am confused with the results of 1a running from HBC with no_ios_reload/> in meta.xml. This should now work because as Tantric stated “when you add no_ios_reload it makes HBC act just like the channel forwarder.” Since the forwarder now works so should running from HBC. Any idea why?

I allowed the wii to sit on the black screen for about 15 minutes when running test 1a. The app is not locked up because when I unplug the usb cable from the wii, I instantly get the failure message “Could not find a valid SD or USB device”. It is as if the error message was there all along but not brought to the foreground.

Now that the forwarder is working I can live with removing no_ios_reload from meta.xml. However can we fix the error message and bring it to the foreground? Then possibly post one more beta with this fixed? Thanks again guys for all you do…

[dagger2b]

Tantric and Rodries,

I just noticed that Tantric made a change to fileopp.cpp in r665 that will try and mount the USB device for up to 5 seconds. Is there any chance you could release a beta7 so I can test my friends drive again? It would be greatly appreciated…

[dagger2b]

Tantric,

Thanks for your explanation. Makes perfect sense now. When running from HBC without no_ios_reload, HBC does an automatic ios reload allowing the drive to be detected. The forwarder ignores meta.xml and never does an ios reload which causes the drive to not be detected. The forwarder is able to find the USB drive and launch the app without doing an ios reload so why can’t the app find the USB drive without an ios reload? Also why does running from HBC or the forwarder using the SD card allow the USB drive to be detected with or without no_ios_reload? Is there anyway I can force the forwarder to do an ios reload perhaps through code using ios_reload(). Thanks for your support…

[dagger2b]

Hi Rodries,

OK I grabbed his hard drive a brought it home with me. Two reasons for this. First I do not have to keep running back and forth to test this. Secondly it is a good test to see if his wii is causing the problem. I tested his drive on my Wii with the latest that you sent me on mediafire. I did not bother with SD card tests. The results are the same as before…

The following tests were run with in meta.xml…
________________________________________________________

1. Running from USB

a. Launching app from HBC – Fails with “Could not find a valid SD or USB device”.
b. Launching app from CF – Fails with “Could not find a valid SD or USB device”.

The following tests were run without in meta.xml…
________________________________________________________

1. Running from USB

a. Launching app from HBC – Successfully runs and mounts USB.
b. Launching app from CF – Fails with “Could not find a valid SD or USB device”.

So once again his drive just does not like the because removing it allows success from HBC. However again it fails when run from the forwarder. Again I will ask if meta.xml is referenced when running from a channel forwarder? In this case does does an ios reload occur? I have to run out for a while but will be back this evening. I will check for a reply from you then…

[dagger2b]

Thanks Rodries,

I will try and make it over to his place this evening and test out the new beta. I think you are correct in your assumption about a timing issue. This might explain why removing allows his drive to be detected from HBC because that must take time to reload the ios. However when running from the forwarder do you think that this also is the problem? When the app is run from the forwarder, is meta.xml even used? In this case will an iso reload occur? Thanks…

[dagger2b]

Sorry about that must be getting tired. I will remove that old link. Can you do the same in your reply…

[Author]

Posts