A Wii Homebrew Project to play GC Games on Wii and vWii on Wii U

• Works on Wii and Wii U (in vWii mode)
• Full-speed loading from a USB device or an SD card.
• Loads 1:1 and shrunken .GCM/.ISO disc images.
• Loads games as extracted files (FST format)
• Loads CISO-format disc images. (uLoader CISO format)
• Memory card emulation
• Play audio via disc audio streaming
• Bluetooth controller support (Classic Controller (Pro), Wii U Pro Controller)
• HID controller support via USB
• Custom button layout when using HID controllers
• Cheat code support
• Changeable configuration of various settings
• Reset/Power off via button combo (R + Z + Start) (R + Z + B + D-Pad Down)
• Advanced video mode patching, force progressive and force 16:9 widescreen
• Auto boot from loader
• Disc switching
• Use the official Nintendo GameCube controller adapter
• BBA Emulation (see BBA Emulation Readme)

• Play retail discs
• Play backups from writable DVD media (Old Wii only)
• Use real memory cards
• GBA-Link cable
• WiiRd
• Allow use of the Nintendo GameCube Microphone

• Game Boy Player

On an original Wii with GameCube memory-card ports, enable both Memcard Emulation and hybrid EXI in the settings menu to use a virtual memory card in Slot A and physical peripherals, such as the GameCube microphone, in slot 2 (Slot B).

The hybrid option defaults to off, including for settings saved by older versions. It has no effect unless memory card emulation is also enabled, and does nothing on Wii U/vWii or for Triforce games. While active, it does not load or expose a virtual Slot B memory card; existing Slot B save images are left untouched. Turn it off to restore the existing virtual Slot B behavior.

Leave Debugger and Debugger Wait off when using a Slot B peripheral: the USB Gecko debugger uses the same physical slot. With Log enabled, the startup log reports EXI: Hybrid EXI mode: virtual Slot A, physical Slot B.

Slot B uses the game's own EXI routines on the real hardware, while Slot A and EXI channel 2 stay emulated. The hardware interrupts of the emulated channels stay masked, and the virtual Slot A interrupt status is only dispatched while a virtual EXI interrupt is pending, so physical Slot B interrupts reach the game.

CPU-level regression checks are available after building. With Python and the unicorn package installed, run:

python scripts\test_hybrid_exi.py --devkitarm C:\path\to\devkitARM -v

These checks exercise the compiled ARM patch helpers, the settings upgrade, and PowerPC routing and interrupt handlers in emulation, including all activation flag combinations. They do not emulate the microphone or replace hardware testing. Optionally add --game-image D:\games\GP7E01\game.iso to exercise the USA Mario Party 7 interrupt-dispatch patch, native immediate-transfer routine, and interrupt handlers against a local disc image. These game tests are skipped when the image is omitted, missing, or not GP7E01. This test does not save or distribute game code.

1. Get the loader.dol, rename it to boot.dol and put it in /apps/Nintendont/ along with the files meta.xml and icon.png.
2. Copy your GameCube games to the /games/ directory. Subdirectories are optional for 1-disc games in ISO/GCM and CISO format.
   • For 2-disc games, you should create a subdirectory /games/MYGAME/ (where MYGAME can be anything), then name disc 1 as "game.iso" and disc 2 as "disc2.iso".
   • For extracted FST, the FST must be located in a subdirectory, e.g. /games/FSTgame/sys/boot.bin .
3. Connect your storage device to your Wii or Wii U and start The Homebrew Channel.
4. Select Nintendont.

For compile Nintendont yourself, get the following versions of the toolchain compiling PPC tools:

• devkitARM r53-1
• devkitPPC r35-2
• libOGC 1.8.23-1

These versions can be downloaded here: https://www.mediafire.com/folder/j0juqb5vvd6z5/devkitPro_archives

On Windows, run the "Build.bat" batch script for build Nintendont.

On Unix, run the "Build.sh" script.

Please use these specific versions for compiling Nintendont, because if you try to compile them on latest dkARM/dkPPC/libOGC, you'll get a lot of compiler warnings and your build will crash when attemping to return to Nintendont menu, so be warned about that.

• The Wii and Wii U SD card slot is known to be slow. If you're using an SD card and are having performance issues, consider either using a USB SD reader or a USB hard drive.
• USB flash drives are known to be problematic.
• Nintendont runs best with storage devices formatted with 32 KB clusters. (Use either FAT32 or exFAT.)