Homebrew Does the vwii menu get full?

  • Thread starter Thread starter dylanlisgo
  • Start date Start date
  • Views Views 1,564
  • Replies Replies 14

dylanlisgo

Member
Newcomer
Joined
Aug 18, 2018
Messages
17
Reaction score
2
Trophies
0
Age
40
XP
98
Country
United Kingdom
might seem like a stupid question but I'm trying to install lots of Wii ware and need to know if it gets full or does it expand?
 
can i extend that?
You are not likely to fill up all of them given that the vWii only has 512MB of storage. If you want more space/more slots, you can solve both of those issues by using an emuNAND.
You can choose if you want to use cIOS emuNAND which requires very little setup, just enable the option in USB Loader GX for partial emuNAND redirection, with only saves/channels redirected and the other NAND files loaded from your real NAND (or if you dump the NAND using the option in USB Loader GX this enables full emuNAND redirection as well but I don't think that has any benefits when using the cIOS emuNAND method) It doesn't have full compatibility, but it lets you launch sysNAND and emuNAND installed games the same way from within USB Loader GX seamlessly (launching them this way also bypasses the 48 channel limit)
Any game that doesn't work with this emuNAND setup, you can install to sysNAND, they all show up the same and work the same so you wouldn't even be able to tell the difference.

The other option is a neek emuNAND, which requires some setup, but does have 100% compatibility. For this method a NAND dump on SD/USB is required. The drawback is that in order to launch a game through neek, the Wii has to reboot into the emuNAND, it can't simply launch the game directly like the other method. The game should still automatically load without navigating the emuNAND system menu, and by installing a channel to return to sysNAND, it can also return to sysNAND automatically once exiting the game (but will return to system menu on sysNAND and not back to USB Loader GX)
That might sound pretty complicated but essentially what it means is that USB Loader GX boots neek, which loads the emuNAND, which loads USB Loader GX again inside your emuNAND (using a neek feature which allows to autoboot a title), which then loads the game you selected, and upon exit, USB Loader GX launches the return to sysNAND channel, console reboots and you're returned to the sysNAND vWii system menu. I think I got all that right. It's not as seamless as the other method and takes longer to boot games, and to exit them afterwards, but it's still a fully automatic process once set up correctly, and has the benefit of full compatibility with all WiiWare. Alternatively if you want to stay in emuNAND and launch another emuNAND game after exiting the first one, that's also possible and saves time.

You can even choose to use cIOS emuNAND by default, and only boot neek for games that are not compatible with cIOS emuNAND, by changing the per game settings, that way most of the emuNAND games will launch and exit quickly, and only some that are not compatible will need to go through the longer neek boot process.

Either of these methods store the emuNAND in the same format/location, as files on SD (or alternatively USB), only limited by the size of your SD card/USB drive. And in both cases, to install games, you can simply use the emuNAND WAD manager from USB Loader GX without needing to boot into emuNAND first.
 
You are not likely to fill up all of them given that the vWii only has 512MB of storage. If you want more space/more slots, you can solve both of those issues by using an emuNAND.
You can choose if you want to use cIOS emuNAND which requires very little setup, just enable the option in USB Loader GX for partial emuNAND redirection, with only saves/channels redirected and the other NAND files loaded from your real NAND (or if you dump the NAND using the option in USB Loader GX this enables full emuNAND redirection as well but I don't think that has any benefits when using the cIOS emuNAND method) It doesn't have full compatibility, but it lets you launch sysNAND and emuNAND installed games the same way from within USB Loader GX seamlessly (launching them this way also bypasses the 48 channel limit)
Any game that doesn't work with this emuNAND setup, you can install to sysNAND, they all show up the same and work the same so you wouldn't even be able to tell the difference.

The other option is a neek emuNAND, which requires some setup, but does have 100% compatibility. For this method a NAND dump on SD/USB is required. The drawback is that in order to launch a game through neek, the Wii has to reboot into the emuNAND, it can't simply launch the game directly like the other method. The game should still automatically load without navigating the emuNAND system menu, and by installing a channel to return to sysNAND, it can also return to sysNAND automatically once exiting the game (but will return to system menu on sysNAND and not back to USB Loader GX)
That might sound pretty complicated but essentially what it means is that USB Loader GX boots neek, which loads the emuNAND, which loads USB Loader GX again inside your emuNAND (using a neek feature which allows to autoboot a title), which then loads the game you selected, and upon exit, USB Loader GX launches the return to sysNAND channel, console reboots and you're returned to the sysNAND vWii system menu. I think I got all that right. It's not as seamless as the other method and takes longer to boot games, and to exit them afterwards, but it's still a fully automatic process once set up correctly, and has the benefit of full compatibility with all WiiWare. Alternatively if you want to stay in emuNAND and launch another emuNAND game after exiting the first one, that's also possible and saves time.

You can even choose to use cIOS emuNAND by default, and only boot neek for games that are not compatible with cIOS emuNAND, by changing the per game settings, that way most of the emuNAND games will launch and exit quickly, and only some that are not compatible will need to go through the longer neek boot process.

Either of these methods store the emuNAND in the same format/location, as files on SD (or alternatively USB), only limited by the size of your SD card/USB drive. And in both cases, to install games, you can simply use the emuNAND WAD manager from USB Loader GX without needing to boot into emuNAND first.

Can I not just merge the Wii menu and sd menu together like on the 3ds?
 
Can I not just merge the Wii menu and sd menu together like on the 3ds?
No, it's just not designed that way. The SD menu doesn't actually load games from SD, it has to copy it into NAND first, which takes time. EmuNAND actually runs the games from SD, so it's a better solution.
 
No, it's just not designed that way. The SD menu doesn't actually load games from SD, it has to copy it into NAND first, which takes time. EmuNAND actually runs the games from SD, so it's a better solution.
I still have compatibility issues with my EmuNAND setup, I thought neek2o was supposed to eliminate that?
 
Are you sure you're loading games in neek mode?
You can also try booting into emuNAND first and running them there.
USBLoader says I'm booting it in Neek mode, but some games will only work if I change the NAND Emulation settings per game to Full or Partial, and some don't work at all. I installed SNEEK from the ModMii EmuNAND Builder, since UNEEK DI doesn't with my HDD.
 
USBLoader says I'm booting it in Neek mode, but some games will only work if I change the NAND Emulation settings per game to Full or Partial, and some don't work at all. I installed SNEEK from the ModMii EmuNAND Builder, since UNEEK DI doesn't with my HDD.

What usually works for me is to set nand emulation to full, for compatibility there's a list you can check that tells you which games can boot with ios and which will only work with neek. Also make sure your emunand path is set correctly.
 

Site & Scene News

Popular threads in this forum