| MAC Address | The wireless MAC address of the wii. you can get this from the internet settings, or if those are inaccessible for whatever reason, many routers will display it. It may contain dashes, colons, or spaces, but should be 12 hex characters when these extra characters are removed. |
Date | this is the date you want the message to show up under in the message board. It should be within the range of 2000 - 2035. Accepted formats are mm/dd/yyyy or in a 32bit hex representation of the number of seconds since 00:00 Jan, 01 2000. NOTE The System menu is triggered to load messages from the SD card when you scroll across days. So if you build the message for the current day, you will have to scroll to a different day and then back again to trigger the loading of it.
SysmenuVersion | This is the version of the System menu to build the exploit for. It can be read in the first page under Wii settings. Accepted formats are 3.2u, 32u, 3.2U, and 32U. Accepted versions are any official, publicly released version from 3.0 - 4.3.
SD Root | This is the base folder where you would like the message created. The design of the cdb archive uses about 13 subfolders to store files. This program will use the given folder and create the necessary folder structure and then place the exploit message in its place.
message on your SD card, you need some homebrew to load. [This one](http://bootmii.org/download/) works pretty well. Save
the homebrew as SD:/boot.elf. Then stick the SD card in your Wii, start it up, go to the message board, and then scroll to the day that the exploit was built for. It should be easily identifiable as it will be the best looking envelope there. Click it and watch the magic happen.
A - Make sure you have SD:/boot.elf. Try with a different SD card. Apparently this SD code doesn't like some cards.
### Compiling
The elf loader code should be built with a toolchain targeting the wii ppc. Change the PREFIX in ./loader/Makefile to point to yours. Once you have built ./loader/loader.bin, copy that into the ./data folder.
Along with the usual gcc tools, Wilbrand needs the bin2s program from devkitpro to build. Wilbrand has 3 makefiles. I'm using a debian Linux x86_64 system with multilib and mingw packages and the *x86 and *.win makefiles to build 3 different binaries. On any linux machine, the plain Makefile should build a native binary.
Windows users should use the *.win makefile and change the PREFIX, as I've added a little makefile voodoo in there. It SHOULD work with mingw and cygwin.
I don't have access to a Mac with a decent build system, so I can't say
others - there is some misc code involved (such as wbe32()) that was takes from various open-source projects which was very nice to have, but I'm sure I couldn't name all occurances and credit all authors appropriately
giantpune - finding the initial bug [WOOHOO!], dumping and debugging 32 version of the system menu to find the offsets, pretty much everything else involved