The Configurator can update itself now. It's probably safer to do that.hunterm said:I have a suggestion for CFG's updater, can it be able to update the Configurator along with everything else?
The Configurator can update itself now. It's probably safer to do that.hunterm said:I have a suggestion for CFG's updater, can it be able to update the Configurator along with everything else?
Dr. Clipper said:Yes, this problem has been covered several times in the last few pages. You have a corrupted cover, likely coming from Wiiboxart, which we are removing from the default list of URLs again. Take a look at the images in the full subfolder and you'll be able to find the bad ones as they'll look funny. The next version of Cfg will also have a patch that will ignore corrupted covers.MrRochie said:I was just wondering if anyone else has seen a problem with freezing when tring to view the fanned box view (the one where I can turn to the back cover) The USB loader either doesn't load the covers or shows a green bar then freezes then sends me back to the Wii menu... Im on 38 Rev14 Version 52 of the loader.... I have tried several 2gb sd cards same problem..... Any Ideas????![]()
![]()
In your case, you already know that only some of the full covers will be corrupted because only the GUI mode fails. Just go take a look at the covers in the full cover directory and you will likely spot the corrupted ones pretty easily. Alternatively, delete them all and redownload after setting the cover_url options to remove wiiboxart (look at my posts for the last few pages as I only just posted the list of options you need very recently).MrRochie said:Thanks for the info Dr. Clipper ..... I was getting ready to toss all my 2gb Sd cards thinking they were bad... are there specific art files I should be looking for that are corrupt or is it pretty random...
I did use marc_max' code as base, but I modified it so that it uses the time you launch the game as the start time. My version never reads the existing playlog file, it just generates the whole thing and writes it to the specified location. Are you saying I don't need to use the ISFS Init/Deinit on the write access? I left that in there because of marc_max, but I'll try seeing what happens if I remove it. The only real issue with my method is that the write access fails if the file isn't there already, but works fine if it is.tueidj said:@Dr. Clipper: If you copied marc_max's playlog code (like Hermes did), it's not really correct. There's no need to init/deinit ISFS, and it should be writing proper times to the file instead of just overwriting the title name/id and correcting the checksum. Otherwise it will be using the time that HBC was launched from the system menu as the starting time...
And that works for you? gettime() for me was returning the time since the console was turned on. The log would always display 23:59 as played time and the numbers were unpredictable. Perhaps this has something to do with the version of devkitpro/libogc used, or as you suggested, it's libogc blindly reimplementing the gettime() function so that it works...tueidj said:You can call ISFS_CreateFile first to make sure it exists, but make sure ISFS_Initialize has been called first. If you're not going to do that you don't need the ISFS_* functions at all, just use IOS_Open/Write/Close instead. And NEVER call ISFS_Deinitialize until you're about to leave the loader, because you won't be able to reinitialize it properly. Libogc blindly reimplements a lot of functions from the proper wii sdk, several of which are never called by games and contain bugs...
Edit: Not sure what getWiiTime() is doing, I use this:
CODE#include
...
playrec_buf.ticks_boot = playrec_buf.ticks_last = gettime();
settime(secs_to_ticks(time(NULL) - 946684800));
We're using a not so recent libogc - 1.7.1. But we do call the above piece of code before launching games, so i guess all we need to do is change the order so that the above is called before writing the playlog.tueidj said:gettime() should return proper tick values as long as this has been done somewhere earlier:
I thought recent libogc included that in the startup code but I might be wrong.Code:settime(secs_to_ticks(time(NULL) - 946684800));
tueidj said:gettime() should return proper tick values as long as this has been done somewhere earlier:
I thought recent libogc included that in the startup code but I might be wrong.Code:settime(secs_to_ticks(time(NULL) - 946684800));
Ah, that's actually what my getWiiTime function does. It's listed in my spoiler there. So no need to convert to gettime.![]()
And here it is again, just to prove it:
CODEu64 getWiiTime(void) {
ÂÂÂÂtime_t uTime;
ÂÂÂÂuTime = time(NULL);
ÂÂÂÂreturn TICKS_PER_SECOND * (uTime - SECONDS_TO_2000);
}
Dr. Clipper said:@Jabe:
The play log actually works, you say... That's weird. What is the exact error that you get? Perhaps try temporarily disabling your hacks and see if any of them affect it? I doubt it, but I could see region free channels or skipping the warning screen having an affect, maybe.
It states it right in the upgrade notes that 223-mload and 224-mload won't work as startup ios. However, 222-mload should work. You're not the first person it has failed to work for, though. Please post the numbers from only the "Stack Dump" section of the DSI (either write them down or take a picture).Jabe said:Do you have the same bug? Any solution?
I agree with tueidj, it's the ISFS thing. Those calls have been removed, so it should work every time for you in 53b. Thanks, tueidj.
using option ios 222-mload or ios 224-mload results in "wii exception dsi occurred" stack dump, blah, blah etc. ?blopa said:someone have the "full channel" of v52? thx
Nobody bothers making full channels any more as they are essentially useless. If you really want one, you'll have to make your own. Just install Cfg on a FAT partition on your SD card or USB drive and use any of the newer forwarders.
QUOTE(bewitched @ Feb 19 2010, 06:08 AM)
Reverting back to ios 249 and usb loader boots up fine again.
Happened after i installed the latest v53a and Hermes v5 (222, 223, 224 and 202).
nikeymikey said:Does anybody have Splinter Cell : Double Agent working with cfg, Or any usb loader?
no
Or is this one of those games that just doesn't work?
yes
I have tried all cIOS's(222/3/4 Im on FAT32) and all other options in the loader but no go.
and it won't work with any other /current) cIOS
It will load the wiimote strap screen, and get as far as the nintendo logo, but then it just black screens.
that's normal
Is this an IOS Reloading game??
it's at least a not-usb-game
IOS reloading is the issue grounding most of these types of errors, but we can't be 100% sure.nikeymikey said:Thanks mouse!!
Anyone know why it doesnt work??