I use NEEK for testing but it takes so long to boot to the system menu I don't bother with it for daily use. :/
I use NEEK for testing but it takes so long to boot to the system menu I don't bother with it for daily use. :/
II can understand that, EmuNANDs are just so simple and intuitive. The fact they act as part of the ULGX ecosystem is nice, as you have it all in once place.
- Joined
- Oct 27, 2002
- Messages
- 23,749
- Trophies
- 4
- Age
- 46
- Location
- Engine room, learning
- XP
- 15,662
- Country
The emuNAND option in the loader is a virtual place where you install channels.
Description
for example, you make a dump of your files located on your Wii internal memory (NAND chipset) to SD card.
NAND -> SD:/nand/
That path is called "emulated NAND", it's either dump of your NAND or a newly created from scratch NAND, it contains all the files and folders that a real NAND usually have for the Wii to function properly.
But it's a wrong name that hackers invented as it's not emulating the NAND at all, it's only redirecting access from NAND to SD or from NAND to USB. it's more a RedirectedNAND than EmulatedNAND.
Some Wad Managers let you choose where you want to install WAD files. NAND (to system menu) or EmuNAND (to SD or USB nand folder)
How it works
in USBLoaderGX you can list the Titles installed either on NAND or on EmuNAND.
When you launch a game from NAND, it use a NAND loader to boot the channel.
When you launch a game from EmuNAND, it tells the cIOS to redirect all access from NAND to your emuNAND path and use a NAND loader to boot the channel.
in both cases, the Wii kernel (the IOS, cIOS, etc.) are still running from NAND, but all file access (to access game's data from the channel, wiiware, VC, etc.) are redirected.
The advantage of emuNAND :
1. space : You can install more games, and store more savegame than your Wii can hold. Wii has 528MB space, most of which is already used by the system files.
2. portability : You can use different EmuNAND to store different savegames, for example multiple users playing the same game, or bringing your SD card to your family and continue your own game progress instead of bringing your console.
3. brick protection : if you install a corrupted channel to EmuNAND, you will not brick your Wii. only the EmuNAND will be affected.
This is what users call "EmuNAND".
but there's another method to "emulate the NAND", and this is were sneek is used.
Sneek is a "more complete" Emulated NAND, the way it works is different than NANDloader explained abobe. instead of running the console then loading homebrew which load cIOS to redirect NAND access, sneek is fully redirected and replacing ALL the NAND data by a different one at console's (re)boot.
not only for the game's channel files, but everything is loaded from SD or USB : IOS, system menu, etc.
when you launch sneek, it reboots the console and disconnects the NAND access entirely.
The SD or USB device interface becomes the Wii Internal Memory. SD/USB is used as if it was the real internal memory present inside the console, it's just that the console is not aware of it. The console access it and boot to System menu as if it was the real one. But you are not accessing your internal Wii memory anymore.
Everything you see and do is actually located on SD card.
Advantage of sneek:
1. same as emuNAND advantage listed above : space, portability, brick protection.
2. even more brick protection : you can try anything, any homebrew, uninstalling System menu if you want, everything is done on SD card, it will NEVER affect the NAND.
3. compatibility : Some games works only in full emulated mode. EmuNAND from USBloaders is only cIOS redirection for few files but not everything and some games crash. Using sneek, no cIOS are even used, everything is working as if the Wii wasn't hacked. Everything running on the console think it's running on a legit NAND. It doesn't even know it's redirected to external path.
EmuNAND type
Sneek : Neek is redirecting NAND to SD path
Uneek : Neek is redirecting NAND to USB path
*neek : Neek in general (sneek or uneek), sometime named u/sneek or s/uneek or just neek.
neek+di : Indicate that the Drive access is also emulated. in addition to NAND being redirected to SD or USB, DISC access is also redirected to the other device.
sneek+di : NAND redirected to SD (SD Card becomes the Wii memory, SD card is locked and can't be accessed anymore by homebrew), di redirected to USB.
uneek+di : NAND redirected to USB (USB becomes the Wii memory, USB is locked and can't be accessed anymore by homebrew), di redirected to SD.
neek2o : A modified version of neek. Neek2o allowed autobooting games at launch and can boot Wii games in wbfs format too.
What users are expecting
Since neek2o release, USBLoaders integrated a way to boot into neek2o and autoboot games resulting in 100% compatibility. Even Wii games with Antipiracy protection are working in neek environment (tintin, driver SF, we dare, etc.)
instead of only redirecting file access to SD, it's fully rebooting the console and autoboot the game for you. you don't see the system menu from neek. when you exit the game, it also exits neek and you are back to your RealNAND interface.
only USBLoaderGX is not compatible yet, and I will add it soon (probably this month).
Description
for example, you make a dump of your files located on your Wii internal memory (NAND chipset) to SD card.
NAND -> SD:/nand/
That path is called "emulated NAND", it's either dump of your NAND or a newly created from scratch NAND, it contains all the files and folders that a real NAND usually have for the Wii to function properly.
But it's a wrong name that hackers invented as it's not emulating the NAND at all, it's only redirecting access from NAND to SD or from NAND to USB. it's more a RedirectedNAND than EmulatedNAND.
Some Wad Managers let you choose where you want to install WAD files. NAND (to system menu) or EmuNAND (to SD or USB nand folder)
How it works
in USBLoaderGX you can list the Titles installed either on NAND or on EmuNAND.
When you launch a game from NAND, it use a NAND loader to boot the channel.
When you launch a game from EmuNAND, it tells the cIOS to redirect all access from NAND to your emuNAND path and use a NAND loader to boot the channel.
in both cases, the Wii kernel (the IOS, cIOS, etc.) are still running from NAND, but all file access (to access game's data from the channel, wiiware, VC, etc.) are redirected.
The advantage of emuNAND :
1. space : You can install more games, and store more savegame than your Wii can hold. Wii has 528MB space, most of which is already used by the system files.
2. portability : You can use different EmuNAND to store different savegames, for example multiple users playing the same game, or bringing your SD card to your family and continue your own game progress instead of bringing your console.
3. brick protection : if you install a corrupted channel to EmuNAND, you will not brick your Wii. only the EmuNAND will be affected.
This is what users call "EmuNAND".
but there's another method to "emulate the NAND", and this is were sneek is used.
Sneek is a "more complete" Emulated NAND, the way it works is different than NANDloader explained abobe. instead of running the console then loading homebrew which load cIOS to redirect NAND access, sneek is fully redirected and replacing ALL the NAND data by a different one at console's (re)boot.
not only for the game's channel files, but everything is loaded from SD or USB : IOS, system menu, etc.
when you launch sneek, it reboots the console and disconnects the NAND access entirely.
The SD or USB device interface becomes the Wii Internal Memory. SD/USB is used as if it was the real internal memory present inside the console, it's just that the console is not aware of it. The console access it and boot to System menu as if it was the real one. But you are not accessing your internal Wii memory anymore.
Everything you see and do is actually located on SD card.
Advantage of sneek:
1. same as emuNAND advantage listed above : space, portability, brick protection.
2. even more brick protection : you can try anything, any homebrew, uninstalling System menu if you want, everything is done on SD card, it will NEVER affect the NAND.
3. compatibility : Some games works only in full emulated mode. EmuNAND from USBloaders is only cIOS redirection for few files but not everything and some games crash. Using sneek, no cIOS are even used, everything is working as if the Wii wasn't hacked. Everything running on the console think it's running on a legit NAND. It doesn't even know it's redirected to external path.
EmuNAND type
Sneek : Neek is redirecting NAND to SD path
Uneek : Neek is redirecting NAND to USB path
*neek : Neek in general (sneek or uneek), sometime named u/sneek or s/uneek or just neek.
neek+di : Indicate that the Drive access is also emulated. in addition to NAND being redirected to SD or USB, DISC access is also redirected to the other device.
sneek+di : NAND redirected to SD (SD Card becomes the Wii memory, SD card is locked and can't be accessed anymore by homebrew), di redirected to USB.
uneek+di : NAND redirected to USB (USB becomes the Wii memory, USB is locked and can't be accessed anymore by homebrew), di redirected to SD.
neek2o : A modified version of neek. Neek2o allowed autobooting games at launch and can boot Wii games in wbfs format too.
What users are expecting
Since neek2o release, USBLoaders integrated a way to boot into neek2o and autoboot games resulting in 100% compatibility. Even Wii games with Antipiracy protection are working in neek environment (tintin, driver SF, we dare, etc.)
instead of only redirecting file access to SD, it's fully rebooting the console and autoboot the game for you. you don't see the system menu from neek. when you exit the game, it also exits neek and you are back to your RealNAND interface.
only USBLoaderGX is not compatible yet, and I will add it soon (probably this month).
^I'll cry of joy if neek2o was finally implemented in my favorite loader, btw do I need to reinstall all the games from my EmuNAND again? Not that it's a big issue since I always keep a backup for the wad files but just to be prepared!
- Joined
- Oct 27, 2002
- Messages
- 23,749
- Trophies
- 4
- Age
- 46
- Location
- Engine room, learning
- XP
- 15,662
- Country
No, you won't need to reinstall games.
The dumped or clean emuNAND from modmii should be both compatible with neek/neek2o.
You can already try to launch neek with your current dump to see if it will work.
Well, sneek requires the path to be on the root of your drive, but neek2o can use subfolders.
/nands/nand1/
/nands/nand2/
etc.
it's also compatible with multi-nands on the fly (one per region).
I'm not sure why it's even needed, I thought neek had region free.
Maybe with neek2o it's required because the game is launched without editing the region in the hidden menu?
But USBLoaderGX is not compatible with multi-NAND paths, unless you install all your games on the main NAND and set the correct path in individual settings of the game.
Well, I'll advise when I'll see how it works.
I'm in holiday now for 15 days.
The dumped or clean emuNAND from modmii should be both compatible with neek/neek2o.
You can already try to launch neek with your current dump to see if it will work.
Well, sneek requires the path to be on the root of your drive, but neek2o can use subfolders.
/nands/nand1/
/nands/nand2/
etc.
it's also compatible with multi-nands on the fly (one per region).
I'm not sure why it's even needed, I thought neek had region free.
Maybe with neek2o it's required because the game is launched without editing the region in the hidden menu?
But USBLoaderGX is not compatible with multi-NAND paths, unless you install all your games on the main NAND and set the correct path in individual settings of the game.
Well, I'll advise when I'll see how it works.
I'm in holiday now for 15 days.
- Joined
- Oct 2, 2006
- Messages
- 1,072
- Trophies
- 1
- Age
- 46
- Location
- France
- Website
- www.ouahouah.eu
- XP
- 764
- Country
So... Which is the best ? Is there a real benefit to prefer sneak nand instead of traditional one ?
why are GameCube save games show as corrupted when loaded through USB loader GX but when I load Nintendont through the actual app the saves are fine.
- Joined
- Oct 27, 2002
- Messages
- 23,749
- Trophies
- 4
- Age
- 46
- Location
- Engine room, learning
- XP
- 15,662
- Country
the cIOS redirected emuNAND is easy to setup and is created/managed inside USBloader.
But it has 80-90% game compatibility.
Sneek emuNAND has 99% compatibility (only one game is not working, I don't remember which one)
As long as you don't need to play the 10-20% incompatible games, you don't need to worry about setting up a sneek mode emuNAND.
Just know that the emuNAND folder itself is compatible with both cIOS or Sneek.
You create it the same way (by dumping your NAND to SD).
If you want to use cIOS method, nothing else is required.
If you want to use neek method, you need additional files on SD or USB and a way to reboot the console in neek mode.
you can use both method conjointly, cIOS for all compatible games and rebooting to neek with the same setup only when needed.
This is what I'll add soon, an per-game option to choose which method to use to boot game. cIOS or neek.
Creating cIOS redirected EmuNAND :
- Be sure you are using d2x cIOS in USBLoaderGX, not IOS58. (1)
- Settings>user path>EmuNAND path : set to SD:/nand/ or anywhere else
- Settings>user path>EmuNAND channel path : for the moment, keep the same path as above. don't worry about these two different options.
- Settings>features>NAND Dump>All.
- Main screen > 4th icon in the top menu : Enable emuNAND
- done !
you now see and can launch the channels installed on emuNAND.
If you want to add more games/wiiware/titles/etc., go to Settings>Features>Install Wad.
1 : cIOS has special character escaping code for FAT32. Some files located on NAND have characters incompatible with FAT32 or NTFS, such as ":" or ">". cIOS is replacing these letters with different letters on your EmuNAND. if you use IOS58 to dump the NAND, you will have issues when dumping NAND if you encounter these characters.
inside:
I don't know.
USBLoaderGX is NOT touching save data.
it only tells nintendont if you want to enable MCEmu, the size and if you want to use single or Multi.
It doesn't edit the path or the file's content.
But it has 80-90% game compatibility.
Sneek emuNAND has 99% compatibility (only one game is not working, I don't remember which one)
As long as you don't need to play the 10-20% incompatible games, you don't need to worry about setting up a sneek mode emuNAND.
Just know that the emuNAND folder itself is compatible with both cIOS or Sneek.
You create it the same way (by dumping your NAND to SD).
If you want to use cIOS method, nothing else is required.
If you want to use neek method, you need additional files on SD or USB and a way to reboot the console in neek mode.
you can use both method conjointly, cIOS for all compatible games and rebooting to neek with the same setup only when needed.
This is what I'll add soon, an per-game option to choose which method to use to boot game. cIOS or neek.
Creating cIOS redirected EmuNAND :
- Be sure you are using d2x cIOS in USBLoaderGX, not IOS58. (1)
- Settings>user path>EmuNAND path : set to SD:/nand/ or anywhere else
- Settings>user path>EmuNAND channel path : for the moment, keep the same path as above. don't worry about these two different options.
- Settings>features>NAND Dump>All.
- Main screen > 4th icon in the top menu : Enable emuNAND
- done !
you now see and can launch the channels installed on emuNAND.
If you want to add more games/wiiware/titles/etc., go to Settings>Features>Install Wad.
1 : cIOS has special character escaping code for FAT32. Some files located on NAND have characters incompatible with FAT32 or NTFS, such as ":" or ">". cIOS is replacing these letters with different letters on your EmuNAND. if you use IOS58 to dump the NAND, you will have issues when dumping NAND if you encounter these characters.
inside:
I don't know.
USBLoaderGX is NOT touching save data.
it only tells nintendont if you want to enable MCEmu, the size and if you want to use single or Multi.
It doesn't edit the path or the file's content.
- Joined
- Oct 2, 2006
- Messages
- 1,072
- Trophies
- 1
- Age
- 46
- Location
- France
- Website
- www.ouahouah.eu
- XP
- 764
- Country
- Joined
- Oct 27, 2002
- Messages
- 23,749
- Trophies
- 4
- Age
- 46
- Location
- Engine room, learning
- XP
- 15,662
- Country
EmuNAND is created when you choose "dump NAND".
it will dump (copy, extract content) of the NAND to your SD.
you will then have a folder on your SD card with a copy of what was on your NAND.
"EmuNAND" is the name of the dumped NAND created on SD.
That folder present on your SD has no conflict with all your other homebrew or program.
this path is used only if you choose to display the content in the loader's option.
When you launch a game located on EmuNAND, the savegame will also be saved on EmuNAND.
Your Wii's data management menu will not see the savegame.
it will dump (copy, extract content) of the NAND to your SD.
you will then have a folder on your SD card with a copy of what was on your NAND.
"EmuNAND" is the name of the dumped NAND created on SD.
That folder present on your SD has no conflict with all your other homebrew or program.
this path is used only if you choose to display the content in the loader's option.
When you launch a game located on EmuNAND, the savegame will also be saved on EmuNAND.
Your Wii's data management menu will not see the savegame.
- Joined
- Oct 2, 2006
- Messages
- 1,072
- Trophies
- 1
- Age
- 46
- Location
- France
- Website
- www.ouahouah.eu
- XP
- 764
- Country
- Joined
- Oct 27, 2002
- Messages
- 23,749
- Trophies
- 4
- Age
- 46
- Location
- Engine room, learning
- XP
- 15,662
- Country
That's EXACTLY the same kind.
except that Gateway EmuNAND is using a full encrypted binary dump (nand.bin), and the Wii version is using the unecrypted extracted content of the nand.bin (files and folder).
But the advantage, purpose and how it works are exactly the same.
You can compare Sneek to Gateway -> reboot the console in EmuNAND.
cIOS just doesn't reboot the console to use it, it's a bridge between both NANDs. (application launched from NAND accessing data from EmuNAND).
If you didn't understand that it was exactly the same thing, then I may have incorrectly explained it, I'm sorry.
If you already know and understand what Gateway EmuNAND is, I don't understand why you asked what EmuNAND is.
EmuNAND is EmuNAND... whatever the console you use.
EmuNAND is the NAND copy loaded from external device to not use the internal chipset memory. that's all.
it has the purpose you want to give to it. (playing games, updating firmware, prevent bricking, whatever else you do, etc.)
except that Gateway EmuNAND is using a full encrypted binary dump (nand.bin), and the Wii version is using the unecrypted extracted content of the nand.bin (files and folder).
But the advantage, purpose and how it works are exactly the same.
You can compare Sneek to Gateway -> reboot the console in EmuNAND.
cIOS just doesn't reboot the console to use it, it's a bridge between both NANDs. (application launched from NAND accessing data from EmuNAND).
If you didn't understand that it was exactly the same thing, then I may have incorrectly explained it, I'm sorry.
If you already know and understand what Gateway EmuNAND is, I don't understand why you asked what EmuNAND is.
EmuNAND is EmuNAND... whatever the console you use.
EmuNAND is the NAND copy loaded from external device to not use the internal chipset memory. that's all.
it has the purpose you want to give to it. (playing games, updating firmware, prevent bricking, whatever else you do, etc.)
- Joined
- Oct 2, 2006
- Messages
- 1,072
- Trophies
- 1
- Age
- 46
- Location
- France
- Website
- www.ouahouah.eu
- XP
- 764
- Country
I have a question regarding video mode patching (USBLoader GX rev1244).
My Wii's system settings resolution is set to 480i (not 480p), and I'm using official component cables. All hardware and software is NTSC. I have my Nintendont (v3.327) settings on "Force NTSC480p", and so when I start a Gamecube game from HDD, the Wii successfully changes to 480p (and correctly displays it on my TV). Then when I return to the USBLoader GX browser, it's back in 480i since that's what the system's set at. All of this is expected operation.
However, when I choose a Wii game (on HDD), say Smash Bros. Brawl, edit the game's loader settings to "Force NTSC480p" and set DOL video patch: All, then boot it from USBLoader, the Wii game displays in 480i. Not the 480p I'm trying to get. This happens with all the Wii titles I've tried.
You may wonder why don't I just keep my Wii's system settings at 480p, and avoid the need for video patching at boot time? If I do set the system settings to 480p, the Wii games do display in 480p, with or without the patching settings. However, this is not my desired solution, because it introduces a different problem: when my system is set to 480p, virtual console titles no longer display in 240p (and the A+Z+1 button combo thing doesn't fix that for them), and I prefer to retain 240p output on those for use with the upscaler I'm using.
The inverse situation is a problem as well: If I have my system set to 480p, then patch with "Force NTSC" for a virtual console game, it does not boot the virtual console game in 480i (=240p) as desired. Rather it boots the VC game in 480p.
TL;DR: For Wii and VC games, forcing a display mode that differs from the current system settings mode doesn't seem to work.
Thanks for any help!
My Wii's system settings resolution is set to 480i (not 480p), and I'm using official component cables. All hardware and software is NTSC. I have my Nintendont (v3.327) settings on "Force NTSC480p", and so when I start a Gamecube game from HDD, the Wii successfully changes to 480p (and correctly displays it on my TV). Then when I return to the USBLoader GX browser, it's back in 480i since that's what the system's set at. All of this is expected operation.
However, when I choose a Wii game (on HDD), say Smash Bros. Brawl, edit the game's loader settings to "Force NTSC480p" and set DOL video patch: All, then boot it from USBLoader, the Wii game displays in 480i. Not the 480p I'm trying to get. This happens with all the Wii titles I've tried.
You may wonder why don't I just keep my Wii's system settings at 480p, and avoid the need for video patching at boot time? If I do set the system settings to 480p, the Wii games do display in 480p, with or without the patching settings. However, this is not my desired solution, because it introduces a different problem: when my system is set to 480p, virtual console titles no longer display in 240p (and the A+Z+1 button combo thing doesn't fix that for them), and I prefer to retain 240p output on those for use with the upscaler I'm using.
The inverse situation is a problem as well: If I have my system set to 480p, then patch with "Force NTSC" for a virtual console game, it does not boot the virtual console game in 480i (=240p) as desired. Rather it boots the VC game in 480p.
TL;DR: For Wii and VC games, forcing a display mode that differs from the current system settings mode doesn't seem to work.
Thanks for any help!
Code:
SysCheck v2.3.0 HacksDen Edition by JoostinOnline, Double_A, R2-D2199, and Nano
...runs on IOS58 (rev 6176).
Region: NTSC-U
System Menu 4.3U (v513)
Priiloader installed
Drive date: 12.18.200812
Homebrew Channel 1.1.2 running on IOS58
Hollywood v0x21
Console ID: 147842083
Console Type: Wii
Shop Channel Country: United States (49)
Boot2 v4
Found 92 titles.
Found 51 IOS on this console. 5 of them are stub.
IOS3 (rev 65280): Stub
IOS4 (rev 65280): Stub
IOS9 (rev 1034): No Patches
IOS10 (rev 768): Stub
IOS11 (rev 16174): Trucha Bug, NAND Access
IOS12 (rev 526): No Patches
IOS13 (rev 1032): No Patches
IOS14 (rev 1032): No Patches
IOS15 (rev 1032): No Patches
IOS16 (rev 512): Stub
IOS17 (rev 1032): No Patches
IOS20 (rev 16174): Trucha Bug, NAND Access
IOS21 (rev 1039): No Patches
IOS22 (rev 1294): No Patches
IOS28 (rev 1807): No Patches
IOS30 (rev 16174): Trucha Bug, NAND Access
IOS31 (rev 3608): No Patches
IOS33 (rev 3608): No Patches
IOS34 (rev 3608): No Patches
IOS35 (rev 3608): No Patches
IOS36 (rev 3608): No Patches
IOS37 (rev 5663): No Patches
IOS38 (rev 4124): No Patches
IOS40 (rev 16174): Trucha Bug, NAND Access
IOS41 (rev 3607): No Patches
IOS43 (rev 3607): No Patches
IOS45 (rev 3607): No Patches
IOS46 (rev 3607): No Patches
IOS48 (rev 4124): No Patches
IOS50 (rev 16174): Trucha Bug, NAND Access
IOS51 (rev 4864): Stub
IOS52 (rev 16174): Trucha Bug, NAND Access
IOS53 (rev 5663): No Patches
IOS55 (rev 5663): No Patches
IOS56 (rev 5662): No Patches
IOS57 (rev 5919): No Patches
IOS58 (rev 6176): USB 2.0
IOS60 (rev 16174): Trucha Bug, NAND Access
IOS61 (rev 5662): No Patches
IOS62 (rev 6430): No Patches
IOS70 (rev 16174): Trucha Bug, NAND Access
IOS80 (rev 16174): Trucha Bug, NAND Access
IOS202[60] (rev 65535, Info: hermesrodries-v6): Trucha Bug, NAND Access, USB 2.0
IOS222[38] (rev 4, Info: hermes-v4): Trucha Bug, ES Identify, NAND Access, USB 2.0
IOS223[38+37] (rev 4, Info: hermes-v4): Trucha Bug, ES Identify, NAND Access, USB 2.0
IOS224[57] (rev 65535, Info: hermesrodries-v6): Trucha Bug, NAND Access, USB 2.0
IOS236[36] (rev 65535, Info: rev 3351): Trucha Bug, ES Identify, NAND Access
IOS248 (rev 1938): Trucha Bug, ES Identify, NAND Access, USB 2.0
IOS249[56] (rev 21010, Info: d2x-v10beta52): Trucha Bug, NAND Access, USB 2.0
IOS250[57] (rev 21010, Info: d2x-v10beta52): Trucha Bug, NAND Access, USB 2.0
IOS254 (rev 65281): BootMii
BC v6
MIOS v10 (DIOS MIOS Lite 2.11+)
Report generated on 05/02/2015.
Have you tried with "Force NTSC480p" only? (Don't mess around with DOL Video patch option)
Thanks for the suggestion---just tried it with DOL video patch set to "OFF"... same result: it's still failing to force 480p in Wii games when the Wii's system setting is 480i, and vice versa.
But again, for Gamecube games, Nintendont is successfully forcing the change from 480i to 480p and vice versa. So USBLoader GX must be implementing something differently than Nintendont (i.e., this issue can't possibly be a limitation of my TV).
I'd be interested if someone else could please try reproduce this behavior. Note some modern displays will automatically deinterlace a 480i signal so don't let that mislead you... my display doesn't deinterlace so I can see the flicker when it's in 480i and the lack of flicker when it's in 480p. Also I'm able to verify which mode its in by checking if it's a 15kHz signal (480i) versus 31kHz (480p) through my TV's info display settings.
I'm very new at this, I got everything working and I just partitioned one of my HDD to have 1.5tb for wii backups as an NTFS and 500gb as a FAT32 for Gamecube and other things. When I'm backing up games with USB Loader GX is there any way where I can make the game automatically install to the right partition? So far they've all be installing on the NTFS one and I have to manually move the files over to the FAT32 with my PC? Thanks!
- Joined
- Oct 27, 2002
- Messages
- 23,749
- Trophies
- 4
- Age
- 46
- Location
- Engine room, learning
- XP
- 15,662
- Country
It's installing to the path you have set in the settings.
Just edit the path to point to the correct partition.
Gamecube path is selected in the path settings:
Settings > User Paths > Gamecube Main Path : set to USB2:/ (it will be your FAT32 if it's the second partition)
For wii games, the default partition is selected in the HDD menu:
Settings > HDD settings > First option in the list : click on it until you see the partition you want to use.
Why not keep everything formated to FAT32 ?
Wii games (EVEN the one bigger than 4GB) work fine on FAT32. you don't need NTFS at all on Wii.
A lot of homebrew require a FAT partition, some of them even require the FAT to be the first partition on your drive.
awefour44:
dol patching should be needed for most games. a lot of games include multiple "compatible video mode" in their main.dol file.
When you launch the game, it selects the best mode from its list based on your current detected setup.
in the loader :
Video mode : It's the "detected setup". The loader is forcing this mode before launching the game.
dol patch : it's used to edit the "compatible mode list" inside the main.dol
Video mode alone should be enough, as SSBB is compatible with 480p and the loader is setting 480p before launching the game.
When the game check your current video mode, it detects that you are using NTSC480p and pick the same mode from its list.
The dol patching is used if the main.dol doesn't contain the video mode you want to use by replacing the "possible mode to use" for the game.
I don't know why SSBB is not using 480p when using that option in the loader.
A thing to note : Channel patching doesn't seem to work.
it's a known bug for a long time. It also affects aspect ratio and ocarina (well, all patches in fact).
Clutz450 Yea, I think I'm just gonna format the whole drive to be FAT32, I mainly didn't want my big wii games to split up into 2 files, but it really isn't that big of a deal.
Cyan Thank Cyan, you're awesome with all the tutorials and help you provide on this forum. Thanks for the detailed explanation 8). I'm actually going to format the whole drive to be FAT32 now.
Cyan Thank Cyan, you're awesome with all the tutorials and help you provide on this forum. Thanks for the detailed explanation 8). I'm actually going to format the whole drive to be FAT32 now.
Similar threads
-
-
-
-
-
-
-
-
-
-
@
NormalCatelol:
i know that there is a forum for this question but, what would you guys name the switch successor? -
-
-
-
-
-
@
The Real Jdbye:
don't mind me, just liking all of SDIO's posts, they deserve it for https://gbatemp.net/threads/usb-partition-use-partitioned-usb-hdds-with-the-wii-u.656209/ -
-
-
-
-
-
-
-
-
