Hacking Configurable USB Loader

[Dr. Clipper]

on PAL wii,
using cfg v67 cant see covers for PAL games (considering cover is available in USB:\usb-loader\covers)

is this a known bug?

Are you sure the covers for the PAL versions are there? Use Cfg to download the covers, or manually confirm that the image for the exact game ID is present.

Some people just download those massive .zips from WiiTDB, but they are separated by region and wouldn't give you PAL covers, so I do need to ask.

 

[arjaylight]

on PAL wii,
using cfg v67 cant see covers for PAL games (considering cover is available in USB:\usb-loader\covers)

is this a known bug?

Are you sure the covers for the PAL versions are there? Use Cfg to download the covers, or manually confirm that the image for the exact game ID is present.

Some people just download those massive .zips from WiiTDB, but they are separated by region and wouldn't give you PAL covers, so I do need to ask.

Yes Im sure the covers were there because it is working in NTSC wii. Its just weird that it cant be detected.
The game is RIPEAF - One Piece: Unlimited Adventure to be exact.

Anyway ill try to download covers from cfg options and let you know guys. I believe i have downloaded covers from PC using wii game manager.

 

[Dr. Clipper]

Yes Im sure the covers were there because it is working in NTSC wii. Its just weird that it cant be detected.
The game is RIPEAF - One Piece: Unlimited Adventure to be exact.

Anyway ill try to download covers from cfg options and let you know guys. I believe i have downloaded covers from PC using wii game manager.

No, it is the problem that I mentioned exactly. The PAL version of One Piece is RIPPAF. RIPEAF is the US version. Note the difference on the fourth character.

 

[arjaylight]

Yes Im sure the covers were there because it is working in NTSC wii. Its just weird that it cant be detected.
The game is RIPEAF - One Piece: Unlimited Adventure to be exact.

Anyway ill try to download covers from cfg options and let you know guys. I believe i have downloaded covers from PC using wii game manager.

No, it is the problem that I mentioned exactly. The PAL version of One Piece is RIPPAF. RIPEAF is the US version. Note the difference on the fourth character.

I guess this solves the mystery, but its weird working on ntsc wii. Thank you very much on your time answering this query. Kudos to this great loader. So many features being added. Keep it up guys! I admirn this amazing backup loader

 

[Skeeve]

Hi!

I tried v67c-222 and it's awful slow. When I scroll through my games with v66c-222 covers are most times loaded before the discs scroll through the screen. With v67c-222 the covers stay with the "loading"-cover very very long.

My background music is also stopping several times which did not happen with 66c-222.

Any information I can send you in order to help in debugging?

So No one else noticed a difference in speed?

 

[FIX94]

So No one else noticed a difference in speed?

The first time I started v67 it was a bit slow, but now everything is amazingly fast, the covers are simply loaded, I don't need to wait, the background music works fine, so no, there is no negative difference in the loader speed. Have you tried v68b?

edit: OMG I HAVE 2000 POSTS!!!

 

[pplucky]

So No one else noticed a difference in speed?
The first time I started v67 it was a bit slow, but now everything is amazingly fast, the covers are simply loaded, I don't need to wait, the background music works fine, so no, there is no negative difference in the loader speed. Have you tried v68b? Same here, except for background music (which I don't have)...

QUOTE(FIX94 @ Apr 19 2011, 10:08 AM)

edit: OMG I HAVE 2000 POSTS!!!

 

[Skeeve]

Okay… So I gave 67c a new try. I downloaded it from the homepage, installed and noticed: I didn't downlaod 67c-222 but 249. In the title Screen "[FRAG]" is shown right after the "249". What does this mean?

To com back to my previous topic: 67c is slower - when started the first time. But in the next run, the covers were simply there.

 

[FIX94]

Okay… So I gave 67c a new try. I downloaded it from the homepage, installed and noticed: I didn't downlaod 67c-222 but 249. In the title Screen "[FRAG]" is shown right after the "249". What does this mean?

IOS249 is using fragments, that's faster. IOS222 don't use it, so it's slower.

 

[oggzee]

So No one else noticed a difference in speed?
WTF, so you didn't notice my reply 8 posts above? On the same page even.
This:

QUOTE(Skeeve @ Apr 17 2011, 10:26 PM) Hi!
I tried v67c-222 and it's awful slow. When I scroll through my games with v66c-222 covers are most times loaded before the discs scroll through the screen. With v67c-222 the covers stay with the "loading"-cover very very long.
My background music is also stopping several times which did not happen with 66c-222.
Any information I can send you in order to help in debugging?

Version 67 has a new cover file cache that is built on the fly the first time.
After that the covers should load much faster than before.
So if you run it again is it still slow or does it now work fast?

 

[oggzee]

Okay… So I gave 67c a new try. I downloaded it from the homepage, installed and noticed: I didn't downlaod 67c-222 but 249. In the title Screen "[FRAG]" is shown right after the "249". What does this mean?

IOS249 is using fragments, that's faster. IOS222 don't use it, so it's slower.

[FRAG] or Fragments is the method that allows loading games from FAT, NTFS and EXT2FS
It has nothing to do with covers.
And it is used in both 249 and in 222 cioses.

 

[Skeeve]

WTF, so you didn't notice my reply 8 posts above?

Yes, I ddi not notice. Shame on me. And thanks to you.

But I have to add something to my observations.

Sometimes 67c-222 seems to hang with that new cacheing. But maybe it's because of my special configuration? Just my /apps/ is on the SD card, but /usb-loader/ is on the USB drive.

 

[FIX94]

[FRAG] or Fragments is the method that allows loading games from FAT, NTFS and EXT2FS

OK, thanks for the explaination. I heard that it's only used in waninkoko's v18+ cIOSes. If both waninkoko's and hermes are using it, why are waninkoko's cIOSes are faster in game loading then? And why is [FRAG] only displayed since v18?

 

[oggzee]

Yes, I ddi not notice. Shame on me. And thanks to you.
But I have to add something to my observations.
Sometimes 67c-222 seems to hang with that new cacheing. But maybe it's because of my special configuration? Just my /apps/ is on the SD card, but /usb-loader/ is on the USB drive.

Maybe it pauses on games that you haven't visited in the previous run.
Try scrolling through all games and then restart the loader.
Does it still hang then? If yes, does it happen when using 249 too?

 

[oggzee]

[FRAG] or Fragments is the method that allows loading games from FAT, NTFS and EXT2FS

OK, thanks for the explaination. I heard that it's only used in waninkoko's v18+ cIOSes. If both waninkoko's and hermes are using it, why are waninkoko's cIOSes are faster in game loading then? And why is [FRAG] only displayed since v18?

249 since r18+ supports mload which is required for FRAG.
222 always included mload so it FRAG was available on all 222 versions.
I added that just as an information that it is available on 249 too.
But I will probably remove that tag since it only confuses people.

Game loading speed is unrelated to frag.
I think it's more related to the different ehcmodules and maybe other components inside the cios.

 

[FIX94]

But I will probably remove that tag since it only confuses people.

Thanks for the fast answer, I think it would be better without this tag because it's only confusing and not very helpful (at least for me).

 

[Skeeve]

Maybe it pauses on games that you haven't visited in the previous run.
Exactly. Because I experimented with parental control.

Try scrolling through all games and then restart the loader.
It hung because(?) I was scrolling too fast. I had to switch off the Wii.

In the next run I scrolled slower and it did not hang.

QUOTE(oggzee @ Apr 19 2011, 02:02 PM)

Does it still hang then? If yes, does it happen when using 249 too?

Now everything works fine.

Regarding the "[FRAG]": I think it's good to remove that tag. I'm one of those who were confused. I already wanted to take the disk to a colleague in order to start defragmentation

 

[oggzee]

cfg v68b2 (beta)
cfg68b2.dol
cfg68b2-222.dol
lang68b2.zip
(or online update)
Changes:

cfg v68b2 (beta)
* New theme option:
gui_button_NAME = X, Y, W, H, TextColor, image.png, Type, HoverZoom
NAME can be: main settings quit style view sort filter favorites
TextColor is same format as gui_text_color_menu
(Seting TextColor to 0 will disable text on the button in case icons are used)
Type: button or icon
HoverZoom: 0-50 in %
Paramteres after coordinates are optional. Default values:
gui_button_NAME = X, Y, W, H, white/A0/44444444, button.png, button, 10
* New theme option:
gui_bar = 0, [1], top, bottom
Will disable / enable gui bar or enable only top or bottom.
* Minor fixes to gui admin unlock & left/right dpad with coverflow
* Changed default gui menu color to white/A0/44444444
* Removed [FRAG] note at startup

 

[oggzee]

I have an issue,
first a few details V68b, style: flow 3 rows
I have 9 pages of games(147 games some are wiiware and VC)
which show up as 8 pages of 18 and 3 on the last page.
When I unlock the admin code to get at the games I don't want my kids to play on I add another 10 games, but the loader still shows only 147 game with the last 10 covers missing.
However if I change my style the games reappear, and are still there when I return to 'flow'
Not a major prob, but there it is.

You're right. Will be fixed.

 

[cambric]

Hi Oggzee,

I saw you removed the [frag] note at startup.

In january I gave you some ideas to improve the startup message: the post is here

Maybe it could be useful to you know...

Compliments for the new GUI....