It's just an option to enable or not to load (or save) files to another location than the original place. Most USBLoaders have that option, because it's included in the cIOS itself. It's wrongly called "emulated NAND", but it's in fact a "redirected NAND access", it's not emulated. You create a copy of your internal Wii memory content (the files and folders in the internal file system) on an SD or USB FAT32 partition, and tell the cIOS to redirect the file access request and provide another file from the external device, instead of the original internal memory, to the asking application. the game trusts the IOS and communicate only with it, it doesn't care where the provided file comes from. the game don't know the file is from another place, it runs as if it was the original file from served by the IOS from the game Disc. when the game request a file, the cIOS take it from USB (instead of CD) and send it to the running application. When you launch a Wii game from USBLoaders, the loader use the cIOS which has access to USB. The cIOS is a patched IOS which redirect the mounted devices.
#Install bootmii as ios or boo2 software#
Instead, it asks the IOS (which acts as bridge between software and hardware, like a driver) the file they want to access, then the IOS mount the drive, locate the file, and give it to the application. The running application don't mount the devices and don't access the file itself. To know how it works, you need to know how the console works to read a disc or the files on the internal memory. You want to learn how it works, or you want a guide to setup and use? if it crash, it's one of the half you kept. If you find the problematic element, restore it (rename it back to original folder) and move half the content to another folder. if it still crash, try with the games folder (if you have gamecube games), etc. If it works without crashing the loader, you'll know it's a wii game issue. But to find the problem you'll have to move or rename some folders.įor example, rename your wbfs folder to wbfs_back, create a new empty wbfs folder, so you don't have any wii games loaded at all when launching the loader. If it's not caused by the audio, it's crashing while trying to load the main menu, so there's something bad (maybe a bad game? or bad cover ?). Immediate solution : reset your settings (delete GXGlobal.cfg file, or even the entire usbloader_gx folder)ĭo you have the official Wii system menu, or did you replaced it when following a hacking guide (for example dark menu ?). or don't use a slow to initialize drive. put all homebrew resources on SD (covers, themes, cheats, settings, etc.) Your USB might have issue initializing fast enough, as a result the sound file can't be played when needed. Maybe you decided to use a theme (in the loader, or a patched non official system menu maybe?), or added new sound files to be played instead of the system menu's official sound, and these files are located on USB (instead of SD, like I always suggest). Line 204 of "C:/Users/davem/projects/devkitpro/libogc/libogc/lwp_threads.c" starts at address 0x80d065f4 and ends at 0x80d065fc. Line 215 of "C:/Users/davem/projects/devkitpro/libogc/libogc/lwp_threads.c" starts at address 0x80d06640 and ends at 0x80d06654. No line number information available for address 0x80b5f990 Line 54 of "f:/Homebrew/Wii/USBLoaderGX/trunk/source/main.cpp" starts at address 0x80b65588 and ends at 0x80b6558c. Line 180 of "f:/Homebrew/Wii/USBLoaderGX/trunk/source/menu.cpp" starts at address 0x80b6598c and ends at 0x80b659ac. Line 85 of "f:/Homebrew/Wii/USBLoaderGX/trunk/source/SoundOperations/SoundDecoder.cpp" starts at address 0x80c3a76c Line 120 of "f:/Homebrew/Wii/USBLoaderGX/trunk/source/FileOperations/File.cpp" starts at address 0x80c358d4 and ends at 0x80c358e0. Reading symbols from F:\Homebrew\Wii\USBLoaderGX\trunk\.
0 kommentar(er)
