Slow FAT32 USB cfg-loader goes to waiting screen too fast.

[GoogleCodeExporter]

What steps will reproduce the problem?
1. My Passport Essential SE 1TB FAT32 drive too slow for booting into cfg-loader
2.
3.

What is the expected output? What do you see instead?
I set cfg-loader as installed file in priiloader. Similar smaller drive works 
fine, but the 1TB MyPassport Essential SE is just a bit too slow for cfg, so it 
goes to the screen waiting for USB, also it does not find the partition 
automatically, I must select it manual. A copy of the contents of the drive to 
a 320 gig MyPassport does not have the problem.

What version of the loader are you using?
60a

What is your System Menu version (e.g. 4.2u)?
4.1u

What is your media type (HDD, USB Flash, SD/SDHC)?
Above

How is your media formatted (wbfs, fat32, ntfs)?
Fat32

Which cios are you using and which version (222, 249v??)?
249

Please provide any additional information below.
I was hoping you might include a feature/setting to force wait for a slow usb 
and allow for a time limit to be set by user. Thanks for an amazing product!

Original issue reported on code.google.com by Jason.G....@gmail.com on 7 Sep 2010 at 4:25

[GoogleCodeExporter]

v63 does not help any better than v62.When booting from a cold start, CFG will 
not recognize my WD Passport 1 TB and will go to the waiting screen first, 
bypassing all covers and configurations, I then must select the USB drive 
before it is recognized. This does not happen with my WD Passport 500 GB drive 
(it is known to be a bit faster).

I am able to boot when a SLOW SD card is used (faster SD or booting from HDD 
does not work).

I think it would be nice if there were a setting available to users for an HDD 
delay. This problem was present in every version (but in recent versions before 
v62, I could not implement the slow SD workaround).

Original comment by Jason.G....@gmail.com on 12 Jan 2011 at 12:52

[GoogleCodeExporter]

v63 has these changes:

 * Improved device init timeout handling:
   If the device doesn't respond in 3 seconds one can
   try reloading IOS or exiting to HBC or sys menu
   timeout has been increased from 30 to 90 seconds

Do you get that prompt?
Does it help if you try to reload IOS? (pressing button 2)
Have you tried to use cfg63-222.dol?
Can you try also ciosx 249 rev21 base 58?

Original comment by ogg...@gmail.com on 12 Jan 2011 at 3:40

[GoogleCodeExporter]

Original comment by ogg...@gmail.com on 14 Jan 2011 at 6:50

• Changed state: Waiting

[GoogleCodeExporter]

Hi,

I hope I can be of some help since I am having the same problem but let me try 
to answer your questions first:
Q: Does it help if you try to reload IOS? (pressing button 2)
A: I pressed 2 but nothing happens

Q: Have you tried to use cfg63-222.dol?
A: Yes, no good

Here is the test environment:
- Priiloader 0.3 configured to boot to installed file (I use the dol's below)
- WD 1.5TB (2 partitions: 2.50GB FAT32 + 1394,76GB FAT32)
- dol test files: cfg64b4.dol / cfg64b4-222.dol
- cIOS rev21 base IOS58 v6175

I powered on the Wii and few seconds later I see the CfgUSB loader menu with:
[+] Select WBFS Device:

I can also see:
CFG base: sd:/usb-loader

It looks like my WD does not spin up fast enough for CfgUSB Loader to detect it 
in time...

of course, if I press [A] I can then select manually my 2nd FAT partition with 
the games but I see no covers and the configuration is the default one.

I think that the loader should wait more than 3 seconds for the device... these 
big disks may take an eternity to spin up :(

Please, let me know how I can help more.

Original comment by edson.ro...@gmail.com on 15 Jan 2011 at 2:51

[GoogleCodeExporter]

Thanks! What you report is exactly the issue as I see it. Your tests saves me 
the time, thanks again. Thought I might suggest a user configurable wait time.

Original comment by Jason.G....@gmail.com on 15 Jan 2011 at 3:07

[GoogleCodeExporter]

edson: sounds like you have the entire setup on the hdd?
Because you're right, the timeout handling is only done for the device where 
games are expected, not for the configuration and config is loaded first.
I think if you had the configuration (/usb-loader/...) on SD it would work fine 
for you.
But I think I will add the timeout handling for config too to cover this issue.

Original comment by ogg...@gmail.com on 15 Jan 2011 at 10:08

[GoogleCodeExporter]

Hi oggzee,

True, all the setup is in the HDD, it is much faster to load the covers 
(specially HQ) than the SD.

As HDD's size is increasing I imagine that people are upgrading their HDD and 
we will have more "complains".

Thank you for planning to add the timeout handling I look forward to test it.

Regards,
Edson

Original comment by edson.ro...@gmail.com on 15 Jan 2011 at 12:17

[GoogleCodeExporter]

I have the setup but load the configuration and covers from SD and the same 
issue is happening unless I use a very old and slow SD card.

Original comment by Jason.G....@gmail.com on 15 Jan 2011 at 2:18

[GoogleCodeExporter]

Ok, try this:

cfg v64b5 (beta)
 * Improved USB timeout handling also when searching for config.txt on USB

And let me know if it's any better or not.

Original comment by ogg...@gmail.com on 15 Jan 2011 at 3:39

[GoogleCodeExporter]

cfg v64b5 is much better. It still goes to the searching for config.txt screen 
at about 3 seconds after power button on wii is pressed or about 1 second after 
the cfg-loader splash screen, it then indicates retry and searches for 3 
seconds, reports an error on usb and then below the error (stating your 
options) it indicates retry and it counts to about 5 seconds and then finds the 
USB drive (I guess this is a continuation of the original retry).

So this is great now, it finds the HDD without user intervention, which was 
important for the many under five year olds that play the wii in my house. 
Thanks so much!

Original comment by Jason.G....@gmail.com on 15 Jan 2011 at 5:09

[GoogleCodeExporter]

Great, thanks for the confirmation, i guess this can be considered fixed now.

Original comment by ogg...@gmail.com on 15 Jan 2011 at 5:49

• Changed state: Fixed