tiagosr / cfg-loader

Automatically exported from code.google.com/p/cfg-loader
0 stars 0 forks source link

USB disk recognized only if launched from WiiXplorer #116

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Run WiiXplorer
2. Launch cfg-usbloader DOL from WiiXplorer
3. USB device is found but loads at really slow speed

What is the expected output? What do you see instead?
If cfg-usbloader is started normally, from HBC or its forwarder, it doesn't 
recognize attached USB device.

What version of the loader are you using?
v64 stable

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

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

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

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

Does it work with other loaders?
not tested

Does it work with the latest or an older version?
no

Please provide any additional information below.

I have recently purchased a brand new hdd and still not able to make it working 
properly.
It won't be recognized at all if cfg-usbloader is started from its forwarder 
channel or inside Homebrew Channel... so I've been immediately lead to think 
it's totally incompatible.
BUT... if I try to access this disk with WiiXplorer, I can see the NTFS 
partition and the whole content, and make all file operations from/to this unit 
at full speed with no problem at all.
So, I tried launching cfg-usbloader executable from WiiXplorer and... 
SURPRISE!! The disk is finally recognized but it loads games at USB 1.1 
comparable speed.

Original issue reported on code.google.com by calipend...@gmail.com on 24 Jan 2011 at 5:50

GoogleCodeExporter commented 9 years ago
What base did you use for 249 r21?
Can you try with some other base?
Did you try with hermes 222 and cfg-222.dol?

Original comment by ogg...@gmail.com on 24 Jan 2011 at 5:53

GoogleCodeExporter commented 9 years ago
FYI, I tried cfg64.dol on wii 4.2U with249 r19 & 249 r20b base 57 without an 
issue. 

Original comment by BenzNgu...@gmail.com on 25 Jan 2011 at 1:45

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
UPDATE ON TESTING cfg64.dol on my wii 4.2U for 249 r21 base 57. Confirming that 
cfg64.dol works fine. I played on two games no issue at all.

Thanks Mr OggZee. Keeping iit up :)

Original comment by BenzNgu...@gmail.com on 25 Jan 2011 at 4:23

GoogleCodeExporter commented 9 years ago
I did more testing and here's what I found:

- my cios 249 r21 is using base 57
- tried with hermes 222 and cfg-222.dol and the disk won't be recognized at all
- tried also USB-Loader GX with same bad results
- plugged my old hdd and it works like a charm

The ONLY way to make THIS new hdd being recognized and accessed is to run 
WiiXplorer with IOS202 and then launch usbloader DOL from there.

Well... my hard disk seems to have compatibility issues, and this is OK, but 
the fact it could be initialized and run with some tricks... I hope it could 
lead developers to better understand WHY it works with such tricks and then 
find out a better compatibility strategy for future releases.

So, if you want to ask me for specific tests and reports, I'll be glad to do 
all of my best to help you.

Original comment by calipend...@gmail.com on 1 Feb 2011 at 12:33

GoogleCodeExporter commented 9 years ago
Did further testing and this is the final result:

- loaded WiiXplorer R212, previously set to use IOS202,
- hdd light starts to blink while WiiXplorer initialize,
- immediately quit WiiXplorer, back to Wii main screen
- launched cfg-usbloader from its forwarder channel
- disk is IMMEDIATELY detected, COMPLETELY accessible and works at FULL SPEED.

I can repeatedly run any game, quit to home screen, reload cfg-usbloader and 
then launch any other game until I physically power down my console.

For some strange reason, it seems that WiiXplorer is capable to set a 
particular state in memory through IOS202 that allows commonly unidentified 
hdds to become accessible.

I'm not a coder and I'm not skilled in no way to understand the mechanism 
behind this strange behavior, but hope this would help someone else to sort out 
hdd compatibility issues.

Original comment by calipend...@gmail.com on 26 Feb 2011 at 11:47

GoogleCodeExporter commented 9 years ago
what kind of HDD is it? have you turned off sleep mode?

Original comment by RussianB...@gmail.com on 4 Jun 2011 at 5:06

GoogleCodeExporter commented 9 years ago
I have this same issue with my Canvio Toshiba 500gb usb 3.0 drive

If i run wiiXplorer which finds my drive and both partitions which are ntfs 3.1 
and fat32 perfectly and even lets me view it perfectly and even run cfg from 
the drive even then it is fine if sometimes horribly slow

but if i try and load cfg from a forwarder or HBC it starts to spin up the 
drive and about 3 seconds or less later it stops then it tries again and again 
continually beginning to spin up for a few seconds then aborting

if i unplug the drive and force it to boot against the sd card even though it 
contains no games then plug the drive in and set cfg manually to usb and either 
the fat1 or ntfs1 partitions it will either retry to mount continuously saying 
retry 1...2...3...N... indefinitely every 3 seconds or less seemingly  or it 
will retry a few times then say OK.. and freeze up 

sometimes if i boot cfg from the loader or HBC it will just freeze at the title 
menu if this drive is plugged in on boot

Original comment by andi.ire...@gmail.com on 2 Jul 2011 at 12:00

GoogleCodeExporter commented 9 years ago
Actually i just fixed this by using dx2 v6 base 58 in slot 249 and booting cfg 
against 249 and the games against 249

Original comment by andi.ire...@gmail.com on 2 Jul 2011 at 12:12

GoogleCodeExporter commented 9 years ago
maybe i'm just a noob but how do i do this? for me everytime i try the usb 
loader, it exits to the system menu.

Original comment by louc...@gmail.com on 12 Nov 2011 at 5:04