Discussion about "backups" is prohibited on this forum. Please read the rules here : http://forum.wiibrew.org/read.php?1,6510by Luckii - The Junkyard
If you stick to devel using libogc, you should probably stay away from ES_Add* functions which provide some NAND write functionality.by Luckii - Homebrew General
-101 is ISFS_EINVAL which is returned by ISFS_Open(const char *filepath, u8 mode) if : - filepath is NULL - filepath is too long (>=64 which is obviously not the case here) - ISFS is not initialized (ie. you did not call ISFS_Initialize()) You should download libogc source code ... it helps.by Luckii - Coding
Yeah ! you probably should ... Make a fake "clickable" GuiButton (1x1 with no GuiImage, outside of the screen), bind a GuiTrigger::SetButtonOnlyTrigger on it, add it to your dialog and then test it like any other in the while(1) { } loop. GuiButton::ResetState() will then "re-enable" locked buttons if you need them more than once in the while loop. Don't know if it is the smartest wayby Luckii - Coding
How do you handle your Home/A/etc... wiimote buttons in your while {} loop ?by Luckii - Coding
You'll probably also need to load your 1st dol somewhere else than 0x80000000 or your loader will crash while relocating the 2nd dol.by Luckii - Coding
Any change to a GuiElement (ie. any Gui* object) requires to halt the GUI thread because libwiigui does not use locks. (Accessing an element with the drawing thread while modifing it using the main thread causes a crash.). So, you need to halt before Append() or any method that makes changes to object attributes like SetText or SetPosition ... etc. Now your buttons stop responding after resumby Luckii - Coding
Perhaps you could try to halt the GUI thread before updating the GuiText.by Luckii - Coding
Are you trying to declare char pData[20] inside the loop ? Try declaring char pData[20] outside the while loop then set it inside the loop with sprintf() and do some SetText(pData).by Luckii - Coding
Just keep it ... It can save your ass if you mess up with channel banners hacking, custom IOS installs or SysMenu patching. To uninstall preloader you just have to reinstall SysMenu 3.2U (or any other). Anyway, remember 2 things : - Do not f*** up IOS30 or you're screwed ... Preloader 0.29 needs it to run and will crash if IOS30 is corrupted ... leading to a full briick. - Do not try to reby Luckii - FixMii
QuoteDaisyChan2009 It happened after installing preloader 0.29 and loading IOS 52 which is for Korean Wii to my knowledge. What do you mean by "loading IOS 52" ? AFAIK, loading an IOS is not sufficient to brick a Wii ... Even a corrupted one does not lead to a brick, except if this IOS is used by SysMenu. Anyway, if you can access preloader by holding reset right after powering the Wii on, tryby Luckii - FixMii