Changes

57 bytes removed ,  23:44, 29 June 2010
m
no edit summary
Line 13: Line 13:  
| source      = included
 
| source      = included
 
}}
 
}}
'''wiifuse_server''' is a wii application that responds to [[wiifuse]] requests coming over a usbgecko adapter from a remote host. this allows you to mount the wii internal nand filesystem with full read/write access remotely on your computer.
+
 
 +
'''wiifuse_server''' is a Wii application that responds to [[wiifuse]] requests coming over a usbgecko adapter from a remote host. This allows you to mount the Wii internal NAND filesystem with full read/write access remotely on your computer.
    
'''<font color="#FF0000">WARNING</font>: watch exactly what you are doing, you can <font color="#FF0000">BRICK</font> your wii with this tool. use at your own risk.'''
 
'''<font color="#FF0000">WARNING</font>: watch exactly what you are doing, you can <font color="#FF0000">BRICK</font> your wii with this tool. use at your own risk.'''
   −
== requirements ==
+
== Prerequisites ==
*an operating system capable of running [[wiifuse]]
+
* An OS capable of running [[wiifuse]]
*the [[wiifuse]] package (v0.2.0 or higher), the server described here is part of it
+
* [[wiifuse]] package (v0.2.0 or higher), the server described here is part of it
*a usbgecko adapter
+
* USBgecko adapter
*a brain and a good understanding of the wii internals
+
* Comprehension of the Wii internals
   −
== build ==
+
== Build ==
'''hint''': a precompiled binary is included
+
A precompiled binary is included.
   −
to compile the included code, you will need [http://www.devkitpro.org/ devkitPPC and libogc] r14 or higher
+
To compile the included code, you will need:
 +
* [[devkitPPC]] and [[libogc]]
 +
** r14 or higher
   −
the server code resides in "./server", just run <code>make</code> there
+
The server code resides in "./server". Run <code>make</code> there.
   −
== howto ==
+
== How-To ==
you will need an identity to authenticate against the wii's ES subsystem. an identity describes the access rights you have on the nand filesystem. it consists of 3 files:
+
You will need an identity to authenticate against the Wii's ES subsystem. An identity describes the access rights you have on the NAND filesystem. It consists of 3 files:
:*certificate chain
+
* [[certificate chain]]
:*tmd
+
* [[TMD]]
:*ticket
+
* [[Ticket]]
   −
these 3 files are, for example, part of a wii image. you can use wiifuse and the included shell script to copy these from a data partition to the needed location:
+
These 3 files are, e.g. part of a Wii image. You can use wiifuse and the included shell script to copy these from a data partition to the needed location:
    
  ~/devel/wiifuse/ '''./wiifuse ~/zelda-tp.iso ~/fuse'''
 
  ~/devel/wiifuse/ '''./wiifuse ~/zelda-tp.iso ~/fuse'''
Line 50: Line 53:  
  ~/devel/wiifuse/ '''fusermount -u ~/fuse'''
 
  ~/devel/wiifuse/ '''fusermount -u ~/fuse'''
   −
to mount the nand filesystem with the zelda access rights on pc side:
+
To mount the NAND filesystem with the zelda access rights on PC side:
    
  ~/devel/wiifuse/ '''make -C server upload'''
 
  ~/devel/wiifuse/ '''make -C server upload'''
1,140

edits