Difference between revisions of "Wiifuse"

Revision as of 01:12, 14 February 2008

wiifuse - coded by dhewg, #wiidev efnet

based on gcfuse code by:

latest stable version: v0.1.2
current version: v0.2.0-wip1

readme

about

wiifuse is a program that allows you to mount a gamecube or wii dvd disc image as a read-only part of the file system. this allows users to browse the directory structure and read the files within.

in contrast to the gamecube, wii images do have multiple partitions. these are encrypted, and wiifuse supports on the fly decryption - provided you have the required 128bit AES key.

further, wiifuse provides access to special data found on these discs. among others, this includes the main executable and informational things like the game name.

requirements

an operating system which
- is supported by FUSE
- supports POSIX compatible threads
FUSE 2.6.x or higher
openssl

build

to build wiifuse, you will need a working compiler and the development packages for the required libraries, have a look at the os specific notes.

the archive includes a Makefile, so just run

make

usage

./wiifuse <image_file> <mount_point> [<FUSE library options>]

hints:

append -f for debug messages (process won't daemonize).
append -o allow_other to let other users access the mount point.
append -h for common FUSE library options.
use fusermount -u <mount_point> to unmount a previously mounted image.

example

$ ./wiifuse ~/zelda_tp.iso ~/wii_image -o allow_other
$ ls -l ~/wii_image

total 0 lrwxrwxrwx 1 dhewg 1 Mar 15 2007 data -> partition2 dr-xr-xr-x 4 dhewg 0 Mar 15 2007 partition0 dr-xr-xr-x 6 dhewg 0 Mar 15 2007 partition1 dr-xr-xr-x 6 dhewg 0 Mar 15 2007 partition2 lrwxrwxrwx 1 dhewg 1 Mar 15 2007 update -> partition1

$ cat ~/wii_image/data/header/name

The Legend of Zelda Twilight Princess

$ mplayer ~/wii_image/data/fs/Movie/demo_movie98_00.thp
$ fusermount -u ~/wii_image

troubleshooting

check if the FUSE kernel module is loaded
- linux: lsmod | grep fuse
- freebsd: kldstat | grep fuse
- os x: kextstat | grep fuse
verify your key file, the md5sum of the 16 byte file (without line feed) currently is 8d1a2ebcd82a3469b77facf15d9c8e50.
append -d 2>&1 | tee ~/wiifuse.log to the wiifuse cmdline. this will create a logfile called wiifuse.log in your home directory, open it in your favorite text editor to get an idea of whats going wrong.

if you still can't get it working, copy and paste the content of that logfile to something like rafb and /msg me the resulting link.

os specific notes

debian / ubuntu

to install the required packages:

apt-get install build-essential fuse-utils libfuse-dev libssl-dev

to mount an image without root privileges, add the user to the fuse group:

adduser dhewg fuse

gentoo

emerge sys-fs/fuse

freebsd

install the required ports:

sysutils/fusefs-kmod
sysutils/fusefs-libs

further doc's

os x

required software:

download

changelog

v0.2.0-wip1

new client/server mode. requires an usb gecko and wiifuse server running on a gamecube or wii in gc mode - for now ;)
new metadata: title id symlinks, tmd infos

v0.1.2

added more disc id's
support for virtual console partitions (found 14 vc games on brawl)
stat compliant - `du` works now
statvfs compliant - `df` works now
minor cleanups and fixes

v0.1.1

fixed some serious u64 offset bugs
corrected the main.dol size calculation
some easy partition validation
support for symlinks
cleaned up and extended the available metadata

@@ Line 15: / Line 15: @@
 :in contrast to the gamecube, wii images do have multiple partitions. these are encrypted, and wiifuse supports on the fly decryption - provided you have the required 128bit AES key.
-:further, wiifuse provides access to special data found on these disc's. among others, this includes the main executable and informational things like the game name.
+:further, wiifuse provides access to special data found on these discs. among others, this includes the main executable and informational things like the game name.
 ===requirements===
@@ Line 33: / Line 33: @@
 :hints:
-:*append <code>-f</code> for debug messages (process won't deamonize).
+:*append <code>-f</code> for debug messages (process won't daemonize).
 :*append <code>-o allow_other</code> to let other users access the mount point.
 :*append <code>-h</code> for common FUSE library options.