Hacking USB Loader GX + Nintendont + Auto Load = nanGB drive size

[DiscostewSM]

Not sure what's going on with my setup. It was working a week ago, but now, it stopped working, so I wiped my stuff from the SD card and USB drive that holds config information and updated the programs. Now I'm having an odd scenario regarding loading from my USB HDD.

Here's the thing. Nintendont works fine when loaded from the HBC. USB Loader GX works fine with Wii games, and even works fine if loading a GC game from USB Loader GX to Nintendont while auto load is not enabled (meaning it loads Nintendont, but I still select the game). But, when auto load is enabled, the printout line as it loads a game shows this...

Drive size: nanGB Sector size: -1

Now, "nan" means "not-a-number", so something is going wrong during this sequence, but it's odd because if auto load from USB Loader GX isn't enabled as was said, it works fine (in that this line prints the correct size of my USB drive). Even the other print outs that refer to storage prior to this line say "Done!" The whole thing locks up at the line "Loading config... Done!", forcing me to unplug the power. Non-auto moves past this and the games run.

Here's some other info about my setup.

Nintendont Loader v3.306 (Wii U)
Built : Feb 26 2015 21:36:17
Firmware: 58.25.32

USB Loader GX v3.0+ (r1241+, IOS 250)

I am using UStealth as well. Both, according to the UStealth thread, should work with it no problem. My NA Wii U is also up-to-date, both Wii U and Wii side. Should you need any more info, just let me know.

 

[WiinerMario]

Do you have a usb controller/adapter plugged in as that has been causing issues with the autoboot feature on usbloaderGX with the recent patch for nintendont. The autoboot works for me if I dont have my usb adapter in.

 

[DiscostewSM]

Do you have a usb controller/adapter plugged in as that has been causing issues with the autoboot feature on usbloaderGX with the recent patch for nintendont. The autoboot works for me if I dont have my usb adapter in.

My drive is connected via Y-cable, main plug in the top port on the back with power plug under it (if I switch them around, the drive becomes unrecognizable, so I assume the apps are port-specific), and I have nothing else connected. I did have my "Wii U" drive connected, but in thinking the problem was because of that, I disconnected that, but the problem remains. No other USB-connectable device is plugged in.

 

[DiscostewSM]

Well, I kinda have a solution that works for the moment. I ended up using older versions of both programs from January, which seems to allow me to use USB Loader GX, in Auto mode, to run both Wii and GC games from it (the latter directed to Nintendont). The problem is now, whenever I want to play a GC game, I have to unplug my Wii U drive. Playing Wii games is fine with both drives connected, but Nintendont can't find the "games" path with both connected. So, I got my Wii U drive connected via powered USB hub (plugged with its own Y-cable because it doesn't have it's own port for power), and that plugged into the Wii U, so when I want to play GC games, I unplug the data cable connected from hub to Wii U.

 

[Bu2d85]

Well, I kinda have a solution that works for the moment. I ended up using older versions of both programs from January, which seems to allow me to use USB Loader GX, in Auto mode, to run both Wii and GC games from it (the latter directed to Nintendont). The problem is now, whenever I want to play a GC game, I have to unplug my Wii U drive. Playing Wii games is fine with both drives connected, but Nintendont can't find the "games" path with both connected. So, I got my Wii U drive connected via powered USB hub (plugged with its own Y-cable because it doesn't have it's own port for power), and that plugged into the Wii U, so when I want to play GC games, I unplug the data cable connected from hub to Wii U.

This is normal. Last I checked (about 2 months ago). Nintendon't does not support more than 1 USB hard drive connected at a time. This includes the WiiU drive. The only solution I could find to this was to put all of my GC games on a large SD card. That way I do not have to disconnect anything when I play.

I actually find it very interesting that you had it "working" with the updated versions of Nintendon't and USBLoaderGX. I may update myself just to try it out.

 

[Cyan]

it doesn't support it officially, as in "you can't select the drive".
But it automatically use the drive located on the higher USB port, so if you connect WiiU HDD on a lower port nintendont will not even know there is another HDD connected and will work fine with both HDD connected.
WiiU : Port0
vWii : Port1-3

Drive size: nanGB Sector size: -1

Is that inside nintendont?
I'll update nintendont and test it. I didn't use it for a long time.

 

[DiscostewSM]

it doesn't support it officially, as in "you can't select the drive".
But it automatically use the drive located on the higher USB port, so if you connect WiiU HDD on a lower port nintendont will not even know there is another HDD connected and will work fine with both HDD connected.
WiiU : Port0
vWii : Port1-3


Is that inside nintendont?
I'll update nintendont and test it. I didn't use it for a long time.

Ok, for some reason, I went back this morning and tried some re-ordering, and now it works with both drives plugged in. What I did was plugged my Wii U drive into port 0, my Wii STEALTH drive into port 1, and then plugged the power plugs of both Y-cables into the powered usb hub. Thought I tried that before and it wasn't working. Maybe that's what I did with updated versions but not the older versions. Now that I know that this setup works, I can now test more recent versions of both programs until I reach the last working ones.

Nintendont works if I plug the Wii drive into ports 2-3, but USB Loader GX doesn't work. That program seems to use only recognize port 1. Anyways, time to test newer versions. I'm running Rogue Squadron II, and while it's running, the audio has slight pauses every now and then (kinda like what it sounds like if a program crashes). May be because of an older version, I dunno.

edit:

Just checked more recent versions of both programs using my connection setup. I'm at R1241+, IOS 249 with USB Loader GX, and v2.303 of Nintendont. The next version of Nintendont is v3.304, which begins to print out the "nanGB" message mentioned in the OP when launching Nintendont from USB Loader GX.

 

[DiscostewSM]

Um...now I'm having problems again, but then, I think it was happening even when I thought it was working. However, I have some more information. When it was working with both drives connected, the Wii U menu couldn't find the Wii U drive I had attached (nothing installed on the drive was showing up). My prior tests involved going directly into Wii mode via Quick Start, so I wouldn't have known. When I'd restart and the Wii U drive was recognized, Nintendont couldn't find the stealth drive.

So, back to my initial compromise. Unplug the Wii U drive when wanting to play GC games, and then plug it back in when wanting to play Wii U games (doesn't matter with Wii games via USB Loader GX).

 

[OriginalHamster]

You would like use d2x-v10-vWii-alt with base 58 for Wii games, that way you have your HDD working on bottom rear USB port for both USBLoaders and nintendont, Wii U device goes in upper rear port, HID USB controllers in left front port.

 

[DiscostewSM]

You would like use d2x-v10-vWii-alt with base 58 for Wii games, that way you have your HDD working on bottom rear USB port for both USBLoaders and nintendont, Wii U device goes in upper rear port, HID USB controllers in left front port.

Wouldn't using the alt version mean less compatibility for nand emulation?

Anyways, I think I have been using the non-alt versions, set with 249 base 56, 250 base 57, and 251 base 58. ULGX has been using 249 for both loader and game. Will try the alt version when I get the chance today.

 

[Cyan]

Less compatibility is a real thing?
We started a compatibility list, if you encounter any issue with alt, test with non-alt and report the result here :
http://wiki.gbatemp.net/wiki/Wii_EmuNAND_Channel_Compatibility_List
(there's no Wii game table, but you can add one if it affects a Wii game emuNAND save)

 

[DiscostewSM]

Less compatibility is a real thing?
We started a compatibility list, if you encounter any issue with alt, test with non-alt and report the result here :
http://wiki.gbatemp.net/wiki/Wii_EmuNAND_Channel_Compatibility_List
(there's no Wii game table, but you can add one if it affects a Wii game emuNAND save)

The notion of compatibility came from the Google Code page of cios d2x v10, where the non-alt had higher compatibility for nand emulation, but restricted to 1 USB port was wasn't plug-n-play, whereas the alt version was vice versa (2 USB ports with plug-n-play, but lower compatibility for nand emulation). If that's not actually the case, then I won't worry about it.

 

[DiscostewSM]

Ok, I installed the alt versions cios d2x v10 (beta53) of base 56, 57, and 58 into IOS 249, 250, and 251, but I'm seeing no change to what's going on. ULGX still only accepts the Wii drive in the top-rear port and with loader/game IOS set to 249. If I change which port it uses and/or the loader/game IOS to 251 (that has base 58 in it), it can't initialize the drive.

 

[OriginalHamster]

Ok, I installed the alt versions cios d2x v10 (beta53) of base 56, 57, and 58 into IOS 249, 250, and 251, but I'm seeing no change to what's going on. ULGX still only accepts the Wii drive in the top-rear port and with loader/game IOS set to 249. If I change which port it uses and/or the loader/game IOS to 251 (that has base 58 in it), it can't initialize the drive.

Just use IOS251 for everything (ULGX boot, and games). It should read your drive in bottom rear, remember your Wii U drive MUST be on upper rear port.

 

[DiscostewSM]

Just use IOS251 for everything (ULGX boot, and games). It should read your drive in bottom rear, remember your Wii U drive MUST be on upper rear port.

I tried that (251 for both, with Wii drive on bottom-rear and Wii U drive on top-rear), but it keeps giving me an error when trying to list Wii games

"USB Device not initialized. Switching to channel list mode"

 

[OriginalHamster]

I tried that (251 for both, with Wii drive on bottom-rear and Wii U drive on top-rear), but it keeps giving me an error when trying to list Wii games

"USB Device not initialized. Switching to channel list mode"

Can you post a SysCheck?

 

[DiscostewSM]

Can you post a SysCheck?

SysCheck.csv

Spoiler

SysCheck v2.3.2 HacksDen Edition by JoostinOnline, Double_A, R2-D2199, and Nano
...runs on vIOS58 (rev 6432).

Region: NTSC-U
System Menu 4.3U (v609)

Drive date: 06.28.2011
Homebrew Channel 1.1.2 running on IOS58

Hollywood v0x21
Console ID: 606367471
Console Type: vWii
Shop Channel Country: United States (49)
Boot2 v0
Found 58 titles.
Found 34 IOS on this console. 0 of them are stub.

vIOS9 (rev 1290): No Patches
vIOS12 (rev 782): No Patches
vIOS13 (rev 1288): No Patches
vIOS14 (rev 1288): No Patches
vIOS15 (rev 1288): No Patches
vIOS17 (rev 1288): No Patches
vIOS21 (rev 1295): No Patches
vIOS22 (rev 1550): No Patches
vIOS28 (rev 2063): No Patches
vIOS31 (rev 3864): No Patches
vIOS33 (rev 3864): No Patches
vIOS34 (rev 3864): No Patches
vIOS35 (rev 3864): No Patches
vIOS36 (rev 3864): No Patches
vIOS37 (rev 5919): No Patches
vIOS38 (rev 4380): No Patches
vIOS41 (rev 3863): No Patches
vIOS43 (rev 3863): No Patches
vIOS45 (rev 3863): No Patches
vIOS46 (rev 3863): No Patches
vIOS48 (rev 4380): No Patches
vIOS53 (rev 5919): No Patches
vIOS55 (rev 5919): No Patches
vIOS56 (rev 5918): No Patches
vIOS57 (rev 6175): No Patches
vIOS58 (rev 6432): USB 2.0
vIOS59 (rev 9249): No Patches
vIOS62 (rev 6942): No Patches
vIOS80 (rev 7200): No Patches
vIOS249[56] (rev 21010, Info: d2x-v10beta53-alt-vWii): NAND Access, USB 2.0
vIOS250[57] (rev 21010, Info: d2x-v10beta53-alt-vWii): NAND Access, USB 2.0
vIOS251[58] (rev 21010, Info: d2x-v10beta53-alt-vWii): NAND Access, USB 2.0
vIOS512 (rev 7): No Patches
vIOS513 (rev 1): No Patches
Report generated on 03/01/2015.

IOSsyscheck.log

Spoiler

IOS513 base hash:
55 b9 ca 5e, 37 fc ec fb, 28 46 bd 20, 98 63 70 f6, 8c 13 3a 35

IOS512 base hash:
2a 35 73 f2, f1 b6 a6 4b, ab d5 7c bd, 7f 75 a9 cd, 54 28 1b 52

IOS80 base hash:
17 6c 61 67, 32 21 32 87, 87 95 75 0a, 84 ad 4e 1b, 70 86 7b 3c

IOS62 base hash:
c6 30 ec c3, 24 5e 8c d1, e2 cd 25 a9, 2f 55 28 b4, 3a 9c 0f 01

IOS59 base hash:
20 f8 f6 64, 8a 1c 56 42, 3a 31 77 fa, a8 56 31 a4, 09 5b ae 0f

IOS58 base hash:
ed ce 29 22, 86 d5 40 cf, 1e b0 0f dc, 09 68 7a ae, ca ba 4f 60

IOS57 base hash:
9b cd 04 d5, 4d b1 65 be, f0 7a 09 35, 9a 5e ea 68, c5 6f e2 21

IOS56 base hash:
1a d5 62 38, 10 fd 14 4b, 94 fd 24 a9, 65 5b 16 65, a2 d1 cb 5b

IOS55 base hash:
7b 8e 33 ae, ad e9 79 ca, bf b2 bb d6, 20 ca 08 a7, ea c8 2e ff

IOS53 base hash:
89 bf 1a 35, 2b d8 e1 43, a6 e1 fd 47, 59 69 02 f3, ae 24 86 4d

IOS48 base hash:
c3 a1 ff bc, 6f 2b 26 49, 0a 76 73 30, 95 9f f1 df, ba 8d 01 b2

IOS46 base hash:
ca b6 c4 3f, 4d 4c df 49, 17 86 ee 08, 26 63 b1 6a, d9 3f 8e 0a

IOS45 base hash:
3a 60 8c 3e, c3 5a e2 b1, 70 f5 7b e4, 0c f6 4a 2b, d1 cf 98 6d

IOS43 base hash:
54 f5 9a 45, 91 f8 7a 50, 80 51 db 3f, 1e cf 51 7c, 85 9c 38 a2

IOS41 base hash:
5d 52 4f 58, 21 df 26 e7, 55 7b 6f e7, 60 25 68 d9, b1 79 8e 46

IOS38 base hash:
48 6e 21 de, 40 16 a4 d7, 9d 7e 2b b5, a3 b8 ac 91, 73 91 5a 00

IOS37 base hash:
66 81 b0 ce, d6 3a 69 71, 7f da 96 e4, ac d0 83 65, f7 6a 20 6f

IOS36 base hash:
fc c6 8c f6, 96 46 3d 48, 4b 62 a3 d6, 82 10 ba c0, 56 27 b6 dd

IOS35 base hash:
f6 01 9c d4, 4f 43 5e ca, 0a 7b c8 6e, ae a6 d7 27, 42 1d c7 1f

IOS34 base hash:
cf 9e c3 1e, 5f 1d c9 78, 02 22 63 ef, 73 1c 19 f3, ff 44 17 07

IOS33 base hash:
b2 b3 6a d9, 70 b9 6c 52, 11 50 a3 07, d7 0b 86 4e, 87 11 08 ee

IOS31 base hash:
3f 08 b3 bb, d4 0e ca 36, dd 7c a5 4f, 18 fa 4c b3, f3 af 6b 3d

IOS28 base hash:
18 44 bb a1, 70 1e ec fa, 59 f6 49 b2, 92 2f 17 8f, 8f 37 76 c2

IOS22 base hash:
b6 37 fd 6e, 63 89 d4 56, 3e ea 7f b8, 3a 00 e8 9e, bf 91 b5 c2

IOS21 base hash:
5f 74 e5 99, f6 ff 78 b3, 03 db 1d 9e, 41 de 0e 44, 70 0a 0b be

IOS17 base hash:
51 6a 92 f8, 42 5a 50 2e, 45 16 cd 0c, e1 a4 b1 88, ca 91 16 40

IOS15 base hash:
bf e8 7f c4, 55 6b 69 20, fb 1a b7 be, 99 20 a1 b9, 7d 3f 33 68

IOS14 base hash:
57 8a 2b 74, 4d e6 d6 b3, b7 d1 84 7c, f1 e9 6b 8c, 9a 43 99 29

IOS13 base hash:
b9 f0 5c cb, 5b 0f 6f 50, f1 f6 78 15, 54 50 5f 42, fe 73 46 ae

IOS12 base hash:
1b f4 f9 fc, 04 a7 c0 4d, 14 37 1e bf, a2 2f 89 06, cd 68 7b 37

IOS9 base hash:
5f eb d0 50, e5 1b 4c d7, f3 ac ce e4, b7 7a 66 74, 5a 94 4e 92

 

[shoemaker]

You can follow my posts starting here to see how I was able to set up two drives to work with Wii U, USB Loader GX, and Nintendont all working.

To keep it short, in GX, set the Loader IOS to 251 and the Game IOS to 251, and in Hard Drive Settings, tell it to use Port 1. Then, plug in your Wii U drive to Port 0 (the top one in the back) and your vWii drive to Port 1 (the bottom one in the back). Finally, in GX's meta.xml, add in the following argument:

<arguments>
    <arg>--mountusb=0</arg>
</arguments>

With this setting, when you launch GX, it will try to use IOS 249 as it is the default setting. It also will not mount the USB because of the "mountusb=0" argument we just added. However, it will fail and then go to the setting called in the in-app settings, which we have now set as IOS 251. This time, it will initialize, and you're good to go! Then, Nintendont works because the drive is located in a higher port than the Wii U drive (1 instead of 0), so it can read it. Then, use UStealth obviously, to keep the nag message from coming up. The compatibility isn't perfect with IOS 251 - I can't run Metroid Prime Trilogy on mine - but most games should work. You can use a second USB Loader like Wiiflow and put any games that don't work on SD and they'll work fine; GX doesn't support SD loading but I know Cyan has said that an update will be coming which lets you run a Wii game on SD through another loader in the GX menu.

As for the "nanGB" thing in Nintendont, that also comes up when GX does autoboot on Nintendont 3.304 and up when an HID controller is plugged in. Again, there's been discussion on it here: https://gbatemp.net/threads/usb-loader-gx.149922/page-965. Hopefully it's a glitch that can be patched out without too much trouble.

 

[DiscostewSM]

You can follow my posts starting here to see how I was able to set up two drives to work with Wii U, USB Loader GX, and Nintendont all working.

To keep it short, in GX, set the Loader IOS to 251 and the Game IOS to 251, and in Hard Drive Settings, tell it to use Port 1. Then, plug in your Wii U drive to Port 0 (the top one in the back) and your vWii drive to Port 1 (the bottom one in the back). Finally, in GX's meta.xml, add in the following argument:

<arguments>
    <arg>--mountusb=0</arg>
</arguments>

With this setting, when you launch GX, it will try to use IOS 249 as it is the default setting. It also will not mount the USB because of the "mountusb=0" argument we just added. However, it will fail and then go to the setting called in the in-app settings, which we have now set as IOS 251. This time, it will initialize, and you're good to go! Then, Nintendont works because the drive is located in a higher port than the Wii U drive (1 instead of 0), so it can read it. Then, use UStealth obviously, to keep the nag message from coming up. The compatibility isn't perfect with IOS 251 - I can't run Metroid Prime Trilogy on mine - but most games should work. You can use a second USB Loader like Wiiflow and put any games that don't work on SD and they'll work fine; GX doesn't support SD loading but I know Cyan has said that an update will be coming which lets you run a Wii game on SD through another loader in the GX menu.

As for the "nanGB" thing in Nintendont, that also comes up when GX does autoboot on Nintendont 3.304 and up when an HID controller is plugged in. Again, there's been discussion on it here: https://gbatemp.net/threads/usb-loader-gx.149922/page-965. Hopefully it's a glitch that can be patched out without too much trouble.

I gave that a try, but that gives me the same error as before, and the drive still isn't recognized.

 

[Cyan]

Shoemaker, I'm not sure you understood how the launching process really work.
What you described is not possible.

If you set 251 in the settings, it will not use 249 magically.
It will also no try to mount USB if you tell it to not mount usb at launch.

If you set mountusb=0 and ios=251 and you have anything different, then you have an issue.