Hacking USB Loader GX

[deathpie]

I've been attempting to play image files off of an SD card and USB drive using usb loader gx. I have the current version of this program and have installed dios mios lite and have no problem playing gamecube games off of my SD card. However, I am unable to play Wii images off of my USB drive. I've tried formatting it as ntfs and playing iso's by placing them in a wbfs folder in the root of the usb drive. Usb loader is unable to find the iso's. I've also tried formatting the usb drive as FAT32 and using Wii Back Up Manager to format the iso's into wbfs. Usb loader gx is able to recognize the images but when I try to launch them my wii freezes. I've waited up to 30 min for the game to start but no luck. I was wondering if anyone had any advice on how to get this working or if I need to maybe install a specific WAD to play Wii images. I'd really appreciate any advice. I've tried googling around a bit but can't find any definitive answers.

 

[Acidflare]

do you have d2x ios 249/250 installed?

 

[deathpie]

Yeah I have d2x v8final installed for 249 and 250.

 

[Acidflare]

v10 beta 52 249(56) 250(57)

 

[deathpie]

I installed those cIOS and still am encountering the same problem.

 

[Vanth88]

to boot from usb all nintendont files must be on usb make sure the partition is set to primary and active

I have no problem playing games from a FAT32 USB I just can't use memory cards even if I copy them to the USB.

Are you able to use a memory card with Nintedont using the latest revision on a fat32?

 

[Cyan]

Since Nintendont 2.208 if i boot a GC game via USBLGX i always get the flickered video.
If i boot nintendont via HBC i can set force deflicker and the picture is ok.
Any tips?

Don't set the video mode to none, and it shouldn't use deflicker.

Deflicker option has replace the old "none" video mode option. There is a new "none" which I need to add.
That's why I need a proper way to detect versions, nintendont up to 199 use Auto>force>none, since 200 it use Auto>Force>Deflicker>none.

Edit:

Howard changed it in v2.208 :
it's now Auto>Force>none>Deflicker.
so I will not add compatibility with nintendont v2.200 to 2.2007 in USBLoaderGX, I will only add deflicker option for 208+
If you really need to boot these 8 specific version, launch them from HBC.
Thanks Howard


Edit 2:
I did some progress today.
Look my dev status in my signature.

release will probably be tomorrow (after I did lot of tests with different nintendont versions)

I have black screen issue with "auto" since v2.150.
I don't see any changed with Deflicker option (my eyes are bad?)

 

[Troopage]

I have no problem playing games from a FAT32 USB I just can't use memory cards even if I copy them to the USB.

Are you able to use a memory card with Nintedont using the latest revision on a fat32?

Yes, you are able to, in fact, you should be using FAT32 on both your SD card and HDD. I think that in order to fix your issue, you need to delete the nincfg files that could be present on both devices. They are your saved Nintendont settings and if you are loading Nintendont through USBLGX, it leads to problems since USBLGX creates its own Nintendont settings, too. Also, make sure you have the memory cards set 251 blocks or less as it can cause compatibility issues if it is more.

 

[Cyan]

USBGX doesn't create its own nintendont settings (unless you use an old version of nintendont).

USBGX deletes nincfg.bin files from both SD and USB before launching, and doesn't create it anymore. It's now sending settings via argument (directly in memory).

 

[Troopage]

USBGX doesn't create its own nintendont settings (unless you use an old version of nintendont).

USBGX deletes nincfg.bin files from both SD and USB before launching, and doesn't create it anymore. It's now sending settings via argument (directly in memory).

That's odd, as I have had to use WiiXplorer to delete the nincfg.bin every time I switch between running nintendont through USBLGX and the HBC, and I'm using the most recent versions of both nintendont and USBLGX.

 

[Cyan]

you are using autoboot?

if autoboot is enabled it shouldn't create the nincfg.bin file.
if it's disabled, it's creating it.

And in all cases, the loader is deleting nincfg.bin from SD+USB1 before writing a new one (even if unnecessary).


it was (is still?) a limitation from nintendont. Arguments was checked only when autoboot was ON.
If arguments are now working without autoboot, I'll change it.

 

[Acidflare]

""
some progress I did today:
- updated the Nintendont detection function.
- Added /controllers/ folder detection
- Added deflicker option
- Deleted work-in-progress PS3 controller support. (will be for another build)

- currently : add Native control setting.

- wondering if Memory card 2043 blocs should be removed or left with a warning that it's not well supported and shouldn't be used anyway.
opt1: Removed completely (but users will complain)
opt2: Add a warning when launching a game (but the warning will always be there and annoying with each game launch)
opt3: add a warning when selecting 2043 in the options (probably the best option)
opt4: add a description after "2043 blocs - instable" (harder to code)

release will probably be tomorrow (after I did lot of tests with different nintendont versions)

option 3 would be your best option possible I use 2043 and I don't have any issues with it I have requsted on the nintendont thread a list of games that have issues with it after someone had stated it they never replied, do you have any idea's which games have issues?

 

[Cyan]

I don't remember which game was affected.
I don't think it's game related, but Memory card data loss.
The last part of the card is corrupted because the memory where the card is stored is overwritten by other functions. As long as you don't have savedata at the end of the card it works fine.

 

[Troopage]

you are using autoboot?

if autoboot is enabled it shouldn't create the nincfg.bin file.
if it's disabled, it's creating it.

And in all cases, the loader is deleting nincfg.bin from SD+USB1 before writing a new one (even if unnecessary).


it was (is still?) a limitation from nintendont. Arguments was checked only when autoboot was ON.
If arguments are now working without autoboot, I'll change it.

I've always kept autoboot enabled.

 

[Vanth88]

I went ahead and deleted everything except my saves(changed dir name). I'm gonna try to do more testing. My config up to this point:
USB Loader GX Mod / Nintedon't r208 / Autoboot, Memory ON or Ind, 256 Blocks / Fat32 Primary 60GB = Exception

I don't use any other options. As I said before though it boots the games up just fine if I don't use the memory card option even if a memory card file already exists on both USB and SD. I haven't tested SD with the modded GX but before I updated to the latest nintedont revision I had no problem playing from the SD card or accessing the memory card.

I'd like to test Nintedon't further but as I mentioned earlier I haven't found another app that lets me setup nintedon't arguments.

*EDIT* If all else fails Its most likely my fat32 partition. I've had this issue before except with my SD card a few years ago. I kept getting exceptions with priiloader and someone mentioned I format my sd card and voila!

*EDIT 2* It's not my partition. I formatted it again and once more I got an exception.

 

[Acidflare]

any idea how many blocks I should keep free then?

 

[Vanth88]

At this point I'm about to give up until a new nintedont revision appears. I've changed my partition to fat, fat32, switched between 16,32,and 64KB clusters. formatted my entire HDD(which was ok, didn't have much) tried to use another HDD but that failed and I formatted my SD card to different partitions, switched to another SD, switched to a lower revision(r196) and original not modded usb loader gx, not a single thing works.

Well not a single thing works except the SD Card *sighs* that loads up fine and lets me use a memory card just fine. I'm gonna go over to the Nintedon't forum and see if I can get help. It's obviously not USB Loader's fault at this point as it does what its supposed to do. My only guess is that it doesn't work well with my 3tb even if I lower the partition size.

Thanks for the help though.

 

[DragonWK]

I'm new here, so forgive my stupid question but. Why would you load Nintendont from USB Loader? isn't it not enough to load it directly?

 

[Acidflare]

I'm new here, so forgive my stupid question but. Why would you load Nintendont from USB Loader? isn't it not enough to load it directly?

wouldn't you rather everything be one one place? I like not having to use different applications

 

[Acidflare]

At this point I'm about to give up until a new nintedont revision appears. I've changed my partition to fat, fat32, switched between 16,32,and 64KB clusters. formatted my entire HDD(which was ok, didn't have much) tried to use another HDD but that failed and I formatted my SD card to different partitions, switched to another SD, switched to a lower revision(r196) and original not modded usb loader gx, not a single thing works.

Well not a single thing works except the SD Card *sighs* that loads up fine and lets me use a memory card just fine. I'm gonna go over to the Nintedon't forum and see if I can get help. It's obviously not USB Loader's fault at this point as it does what its supposed to do. My only guess is that it doesn't work well with my 3tb even if I lower the partition size.

Thanks for the help though.

could be your hard drive controller some of them don't play nice with gamecube games if you have another portable hard drive you could try that or buy a hdd enclosure case it's the same thing