Hacking ERROR ret = -1

[st0rax]

What can I do? I have System Menu 3.2E with CioS36-rev09. USB Loader 1.0 tells me always: Could not retrieve the games list!, when I plug in my USB HDD... (westernDigital, 640gb)
there is 1 game i added through wbfs_win.exe (Win32).

please help

 

[raulpica]

ERROR Ret=-1 means "USB device not supported".

Try with another HD/Pendrive/something.

My Samsung 2GB Pendrive didn't want to work and gave me that error... Then I tried with my Apacer 4GB Pendrive and it worked fine

 

[kedest]

May be a compatiblity issue with your drive.
Try the 1.1 loader.

 

[dreary79]

I get this error as well. After rebooting my Wii it works, sometimes.

 

[st0rax]

Could not retrieve the games list!
maybe i have to use the "list" cmd after i added the isos...

 

[snikerz]

Your hard drive isn't supported

 

[MizuhoChan]

I guess nobody pays attention to me ;_;

Anyway, find one that will work, put it in, boot the loader and when it tells you to format it, take it out and put your drive in. This may work, as it works for my 4gb flash drive.

 

[st0rax]

hehe... I was able to found ot, HOW to do it right.
USB Loader 1.1 is able to find the games list on WD Elements 640GB! Yes, it works! But not with USB Loader 1.0 ^^
I thought that would be useful for some another gbatempler

Have fun (some games do not work at this moment though)

 

[Wiisel]

if its mains powered switch of the plug boot the wii the switch the drive on

i have a pain in the arse issue with a 750GB seagate freeagent
if i shutdown the wii or swp between pc i get an ERROR: could not initialize USB subsystem! (ret = -1)
so each time i have to switch it off by the mains power on the wii then switch it on after that its good untill the wii shuts down then i have to hard reboot the drive when i power back up

other than that this drive works ok

possible solution wire the other usb 5v to a relay to switch the drive on and off with the wii?

 

[atomike]

Plug the USB cable on your wii first. Then boot HBC. Then turn on the hard drive. It works for me like this.

I don't know why it's picky like this, but could this problem be solved by debugging the usb2 driver????