Hacking Configurable USB Loader

[HemiSync]

Sorry if this was answered already but I´ve searched around and couldn´t find an answer yet. I've got Resident Evil Archives: Zero (Wii version) a few days ago and just can't load it with Configurable USB Loader.

Already tried 002 fix, blocking IOS reload, cIOS 249, 222, 223 and all the combination in betweeen, nothing works.

The games loads fine, the safety strap screen from NIntendo shows up and then it loads that screen with the Mansion background and the message "This game contains scenes of explicit violence and gore" and then just freezes.

If I don't plugin the classic controller or the nunchuck, after the safety strap screen a black screen with a message to attach either one is shown. When I attach the nunchuck (or the classic controller) it loads the Mansion screen with the message about violence/gore and freezes.

Already tried 2 different ISO dumps so I dont think they are the problem.

I have my Wii softmodded with Wanin's 249 rev 14, Hermes' 202, 222 and 223 v4, and Config. USB Loader v49.

Any ideas? Does this game need some alt.dol tricks to work or requires a special cIOS ?

Not sure if anyone replied, but I can verify that the game works on CFG 49-fat with no settings set and using hermes 222-mload R4 due to me using fat32.

update:
Just tried it on 50a as well and still working.

 

[Fat D]

Concerning the above poster's sig:

I disagree with you so stop trolling my sig.

would that help you two get along?

 

[HemiSync]

oggzee,

Is there serious slowdowns on some fat32 partitions with the hdd info turned on? I only ask because I have been using both the -fat and non -fat versions of your loader on my fat32 Seagate Freeagent Go with .wbfs files and when I do use the non fat version it only takes a max of 3 seconds to calculate the free space on a 320GB with 54GB available. I really didn't see an issue with it on my setup.

 

[Blue-K]

Ok, since it's now out that it's NTFS-Support, I can ask more freely...I tried to gather some Informations, but didn't found any Read-Me, and the first post also didn't got updated...maybe I'm too stupid, or it's to early to give Instructions, I don't know...

Anyways:
It still launches .wbfs-Files, right? Full ISOs wouldn't be clever, because you'll loose to much space, this is clear. But, .wbfs-Files still only support up to 4GB, so you would still have to chunk some games. Now, is there a new version of the WBFS File Utility coming, or are you thinking to support Wiimms .wdf-Files? As far as I can tell, there isn't any difference between them, though, I may be wrong...

It would just be nice to have one File for each game, you know

? I see this hasn't high priority, still, would be nice

 

[George Dawes]

Yes it does. I guess it was too cryptic though...

Not too cryptic - you just fail at spelling. Try AGSF.

 

[oggzee]

Ok, since it's now out that it's NTFS-Support, I can ask more freely...I tried to gather some Informations, but didn't found any Read-Me, and the first post also didn't got updated...maybe I'm too stupid, or it's to early to give Instructions, I don't know...

Anyways:
It still launches .wbfs-Files, right? Full ISOs wouldn't be clever, because you'll loose to much space, this is clear. But, .wbfs-Files still only support up to 4GB, so you would still have to chunk some games. Now, is there a new version of the WBFS File Utility coming, or are you thinking to support Wiimms .wdf-Files? As far as I can tell, there isn't any difference between them, though, I may be wrong...

It would just be nice to have one File for each game, you know

? I see this hasn't high priority, still, would be nice

.wbfs files are not limited to 4GB.
You can use the -0 flag in wbfs_file to avoid splitting.
.iso files will be added too, but i agree i don't consider them practical.

 

[George Dawes]

.iso files will be added too, but i agree i don't consider them practical.

I'm glad iso files will be supported - sometimes you just want to try a game. Being able to just copy *.iso is useful, if the game is worth playing I'll convert it to wbfs later - if it isn't good I'll just delete it.

At least in theory, if I were ever to use ntfs - outside of windows pcs it has little use imo, I'll stick with wbfs/fat32, the former is well established and the latter is universal.

If you ever add ExtFS support however... =]

 

[Sacohen9665]

Having problems with Jump Start Pet Rescue USA.
It will load, get into the game, but when I get to the screen that asks me to choose Player1, player2, player3 or credits and I choose any of the player options then choose either explore or story, the system re-starts.

Any ideas.

It's and NTSC game and I've tried Game default, system default and Force NTSC and nothing is different.

PS; That new feature is a nice option, but I thinks it's going to turn out to be user choice again. All the better, like someone else said, it just gives people more options

Thanks;

it is probably one of those multiple dol games. you can try opening it with wiiscrrubber and extracting the dols, and using the alt dol method.

As has been repeated over and over in multiple threads, none of the loaders these days require you to extract dols with wiiscrubber. They can load them directly from the game. FFS...

PS oggzee; you keep surprising us and making the product even better, too bad you can't do anything about Sacohen9665.

Thanks

Nice one Skizzo, it would have been nicer if you contributed and possibly gave me an answer to my problem with Jump Start Pet Rescue USA.

 

[Sacohen9665]

Alright, as always, I love this loader, but before I get excited and reformat my hard drive, does the new #50 feature work with all games and such or is it incomplete at this point? I mean I don't want to go through all the fun of reformatting my hard drive if the new feature isn't on par with FAT32 at this point,

Either way though I love the awesome work that has been put into this loader.

NTFS support is read-only for now, so installing from inside the loader will not work.
Also, I've got reports that not all games work, but this should be fixable, the problem seems to be depending on the layout of the file not the type of game...
So i wouldn't just move to ntfs yet.
If you want, try it out with a handful of games...

Just a note in general, not really relate to this comment, but I thought it was agood place to bring it up.

MAC will only read NTFS, they will not write to it so this feature would not be much use to anyone using a MAC.

 

[George Dawes]

MAC will only read NTFS, they will not write to it so this feature would not be much use to anyone using a MAC.

"out of the box" the mac will mount ntfs read-only.

NTFS-3G is free and open source, tuxera also offer commercial ntfs and exFat drivers for mac, as do paragon. All enable writing to ntfs under osx. All are stable too.

I do agree that FAT32 is the better choice for most non windows users though (and even for windows users).

 

[Sacohen9665]

MAC will only read NTFS, they will not write to it so this feature would not be much use to anyone using a MAC.

"out of the box" the mac will mount ntfs read-only.

NTFS-3G is free and open source, tuxera also offer commercial ntfs and exFat drivers for mac, as do paragon. All enable writing to ntfs under osx. All are stable too.

I do agree that FAT32 is the better choice for most non windows users though (and even for windows users).

Thanks; that is nice to know, since I work on a MAC and PC every day, side, by side.

 

[George Dawes]

Thanks; that is nice to know, since I work on a MAC and PC every day, side, by side.

No worries - there are apps to do things the other way too : Macdrive & Transmac both allow a windows pc to read/write HFS+ discs.

 

[nikeymikey]

Thanks for the quick fix for Peppa Pig, my 2 y.o. can finally play it now. Even tho she cant work the wiimote properly. lol

 

[GolfDude]

what dol do you need to use in order to use NTFS? the fat dol or plain dol? and just the games will read off ntfs correct? it wont read other hoembrew programs and such for the homebrew channel to laod so youd still need a fat partition for everything else?

 

[Dr. Clipper]

hiya, just wondering, how do you get game covers on? im noob, n search function is kinda funny, cant find it, thanks for any replies
Go to the global options page (push 1 twice), select "Download Missing Covers" and push D-pad right. You can also download covers for individual games by using the options menu.

QUOTE(GolfDude @ Dec 13 2009, 10:05 PM) what dol do you need to use in order to use NTFS? the fat dol or plain dol? and just the games will read off ntfs correct? it wont read other hoembrew programs and such for the homebrew channel to laod so youd still need a fat partition for everything else?

Either .dol will work, but you still need to use IOS222 to launch the games, so the fat version is slightly more suitable.

 

[fig2k4]

.iso files will be added too, but i agree i don't consider them practical.

I don't know how advanced the NTFS modules are, but would there be any chance of being able to use sparse files? That would make ISOs ideal for use on NTFS, since they'd really only take up the same space as .wbfs or CISO.

 

[mousex]

Just a note in general, not really relate to this comment, but I thought it was agood place to bring it up.

MAC will only read NTFS, they will not write to it so this feature would not be much use to anyone using a MAC.

10.6 Snow Leopard has write support out of the box, you hast have to mount with -o rw

 

[Elfish]

.iso files will be added too, but i agree i don't consider them practical.

I don't know how advanced the NTFS modules are, but would there be any chance of being able to use sparse files? That would make ISOs ideal for use on NTFS, since they'd really only take up the same space as .wbfs or CISO.

that'd be pretty cool if u could use isos on ntfs straight away (and even smaller in size).

 

[oggzee]

I don't know how advanced the NTFS modules are, but would there be any chance of being able to use sparse files? That would make ISOs ideal for use on NTFS, since they'd really only take up the same space as .wbfs or CISO.

It's already coded so that it takes advantage of that, but not tested yet.
Few notes:
wbfs_file does create a sparse file when creating .iso files.
Copying files using windows explorer will loose the sparse properties.
There's a 50t1.dol that might contain some fixes related to sparse files

 

[fig2k4]

Is there any specific naming and file layout for ISOs? eg. \ISO\ID_Title.iso

I'll give it a try tonight.