[dagger2b]

OK I also used the same format utility as you did but I used the command line version. The only other thing that I can think of is if you have more that one partition on the drive make sure that the FAT32 is the first or primary and it is set to active. I am sure you already no this. Was this drive recognized by the older HBC V1.0.6? Very strange it seems that anything using ios58 does not like your drive. Not sure what version of ios58 you are running but the latest is v6176. If you are running v6175 I would update it but I am not sure it will help you any. Sorry I wish I had some more advice for you…

[dagger2b]

OK so if I understand you correctly, the changes Rodries made simply allowed you to run Wiimc from your SD card and then the app would mount your USB drive and allow you to access it. The same is true for your other apps in that you would run from SD and then access the USB? The fact that Priiloader or HBC will not see the drive is very unusual. Might I ask how did you format the drive? In my case XP will not let you format large drives larger that 32GB. So I had to use a third party utility. Also how many partitions and what are they? Please let me know…

[dagger2b]

fasttest I am confused I thought that Rodries and you had a debug session and he got your drive to be recognized. Now you are saying that nothing will see it? Please explain…

[dagger2b]

Thanks for your input fasttest. I only wish that NTFS was my problem with his drive. His drive is formatted FAT32.
Anyway really glad to here that you and Rodries were able to get your drive recognized. Looks like from your post you are running a portable stick flash drive is that correct?

[dagger2b]

Rodries,

My buddy had to leave so I could not summarize my findings in my last post. It is still a mystery to me why removing from meta.xml allows the USB drive to be recognized from HBC. I really do no see why this is even being used anyway. If HBC is running ios 58 and the channel forwarder runs under ios 58 the what does accomplish? Secondly it seems that running from SD with or without allows the USB drive to be detected by both HBC and the forwarder. In the case of the forwarder, who is doing the mounting, is it the forwarder code or the app? If it is the forwarder then perhaps that is were the code change needs to be made.

OK I would like to have the drive detected without having to remove from meta.xml. This would have to be done manually for each new release. However it is possible if we can not get that to work. But I really need to get the forwarder to work with or without . Thanks again for your patience reguarding this issue…

[dagger2b]

Rodries here are my results with beta6 and channel forwarder V.1.5…

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

1. Running from USB with no SD

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”.

2. Running from SD with USB connected

a. Launching app from HBC – Successfully runs and mounts both SD and USB.
b. Launching app from CF – Successfully runs and mounts both SD and USB.

3. Running from USB with SD inserted with app removed from SD

a. Launching app from HBC – Not Possible since app is removed from SD.
b. Launching app from CF – Crashes back to the system menu.

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

1. Running from USB with no SD

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”.

2. Running from SD with USB connected

a. Launching app from HBC – Successfully runs and mounts both SD and USB.
b. Launching app from CF – Successfully runs and mounts both SD and USB.

3. Running from USB with SD inserted with app removed from SD

a. Launching app from HBC – Not Possible since app is removed from SD.
b. Launching app from CF – Crashes back to the system menu.

[dagger2b]

Thanks Rodries,

I will head over to his place this afternoon and test out beta 6. I will bring an SD card this time for even more extensive testing. I will let you know…

[dagger2b]

Yes if I launch Wiimc from the forwarder using the SD card the USB drive is found. I believe I ran this test with removed from meta.xml. Do I need to try this test with put back in to meta.xml? Perhaps another test would be to have an SD card inserted without the Wiimc app on it. I wonder if the USB drive would then be detected and the app would be run from the USB. What do you think?

[dagger2b]

Hi Rodries,

OK I have tested Beta4 first and second release and also Beta5 on my buddies Wii. He is running HBC ios58. All tests were done with no SD inserted only USB drive. The results are the same for all 3 releases. Here they are…

Wiimc from HBC with in meta.xml – Fails with “Could not find a valid SD or USB device”.
Wiimc from HBC without in meta.xml – Success mounts USB drive.
Wiimc from CF V1.5 with in meta.xml – Fails with “Could not find a valid SD or USB device”.
Wiimc from CF V1.5 without in meta.xml – Fails with “Could not find a valid SD or USB device”.

It is a mystery to me why removing from meta.xml allows the USB device to be detected when launching from HBC. It is even a bigger mystery to me why launching the app from the channel forwarder fails to detect the device with or without in meta.xml.

I have to leave my buddies now but I will check back tonight. I look forward to your reply and hope we can figure this one out. Thanks for all your hard work and support…

[dagger2b]

Thanks Rodries,

I will go over to my buddies and test beta4 tomorrow morning…

[dagger2b]

This problem is still occurring on my buddies wii with 1.1.0 and the latest beta2 release. If I remove then these versions work fine from HBC. However the 1.1 forwarder that I had to use with 1.0.9 no longer works. It just freezes the wii. The V1.5 forwarder does not crash back to the system menu like V1.4. It launches the app but fails with “Could not find a valid SD or USB device”. It is the same symptom I get when running from HBC with . However if I run the app from an SD card with the USB also connected, the app will launch fine. In this case the app is run from the SD card and both the SD and USB devices are mounted and available. I am not sure why running from SD allows the USB device to be found and mounted but it does. Tantric, I realize that this problem is HBC fault. However who knows when they will correct it. Is there anything you can do to make the next forwarder release detect his drive without having an SD card in? Thanks for your support…

[dagger2b]

Thanks for the explanation Tantric. He does not use his DVD as it is a D3 drive. However removing does get his HDD to be recognized by Wiimc. Not sure why but just glad it works for now. By the way his drive is a green drive which I think is part of the problem. I bet other folks having problems have a green drive as well. Anyway thanks for all your hard work…

[dagger2b]

After extensive testing there seems to be no ill effects of removing from meta.xml. When launched from HBC Wiimc runs under ios 58 as it should. Running the older forwarder 1.1 also seems to have no problems and runs Wiimc under ios 58. With this being said I am unsure what the point of is. As for the newer forwarders not working, I have no clue. Tantric I sure wish you would comment on this. Thanks.

[dagger2b]

Hi everyone,

My buddies Wii was having the problem of his drive not being recognized when launched from HBC and CF 1.4 crashing back to the system menu. For those having problems running from HBC try removing from meta.xml. For those of you that are having problems with the CF try an older version of the forwarder. Version 1.1 works for my buddies wii. You can find the older copies of the CF here…
http://code.google.com/p/wiimc/downloads/list?can=1

Also see my thread for further explanation of how I figured this stuff out…
http://www.wiimc.org/forum/viewtopic.php?f=4&t=818

[dagger2b]

This problem has been corrected with version 1.0.9. I am not sure which version corrected this issue because I skipped 1.0.7 and 1.0.8. Thanks Tantric. This topic can be closed.

[Author]

Posts