Closed GoogleCodeExporter closed 8 years ago
Forgot to mention that I am running R23.
Original comment by gsoud...@cox.net
on 14 Jun 2010 at 12:42
Stupid error there. Not getting the device menu if an automount fails will be
fixed next release, but hopefully so will the usb issue. About the power down
issue, does it always do that, or only when stuck in this loop? Also does it
happen if you use the power button on the Wiimote? Unfortunately I can't
recreate that issue so fixing that might have to wait.
Original comment by cwstjden...@gmail.com
on 16 Jun 2010 at 4:49
cwstjdenobs thanks for your reply. Yes I agree that the device menu should be
displayed if the automount fails. As for the USB 2.0 issue, there is nothing
to be done here. If I choose IOS36 then only USB Mass Storage Device will
mount because IOS 36 does not have USB 2.0 support. So the Error! (ret = -1)
is correct. This is to be expected. It looks like FatDevice=usb is not being
executed when using the wm_config.txt file. I strongly suspect that the app is
actually executing FatDevice=usb2 instead. As for the code dump, it occurs
with both the power button on the Wii and the power button on the Wiimote.
With my config file I should think that this should be reproducible. Hope this
helps.
Original comment by gsoud...@cox.net
on 16 Jun 2010 at 10:54
Just tested the new release. Thanks for fixing this problem. One thing I
would suggest is that you add some informational messages while loading the IOS
and mounting the device. It seems to take about 6 seconds to load on my wii
with external usb. During this time the screen is blank and users may wonder
what is going on. Certainly not a requirement just a suggestion. Thanks...
Original comment by gsoud...@cox.net
on 23 Jun 2010 at 2:09
TBH I wasn't certain I'd fixed it, I just left what I'd done in there as I
committed the new info for SM4.3 as I was certain you'd at least get the device
menu. Just added output for the IOS and Nand emu (not that that's any good
here). It's already got output for the fat device, but it flickers past quickly.
Original comment by cwstjden...@gmail.com
on 23 Jun 2010 at 9:51
OK I do see output when mounting the device but it happens so fast that you
would never know it was there. In fact I can not even catch what it says. So
the delay must be in loading the IOS. The message there should help out allot.
I look forward to the next release with the loading IOS message and also the
allowance of wm_config in the folder that app was launched from. Thanks...
Original comment by gsoud...@cox.net
on 24 Jun 2010 at 1:04
OK I do see output when mounting the device but it happens so fast that you
would never know it was there. In fact I can not even catch what it says. So
the delay must be in loading the IOS. The message there should help out allot.
I look forward to the next release with the loading IOS message and also the
allowance of wm_config in the folder that app was launched from. Thanks...
Original comment by gsoud...@cox.net
on 24 Jun 2010 at 1:08
Original comment by cwstjden...@gmail.com
on 24 Jun 2010 at 11:35
Original issue reported on code.google.com by
gsoud...@cox.net
on 14 Jun 2010 at 12:40Attachments: