![]() To mount the folder H:/WiiU to C:/mounted you would use something like this: Java "-Dfile.encoding=UTF-8" -jar wiiu-fuse.jar -in H:/WiiU -mountpath Q To mount the folder H:/WiiU to Q:/ you would use something like this: (unitx) The mountpoint must not be a sticky directory which isn't owned by the user (like /tmp usually is).(unix) The user can only mount on a mountpoint for which he has write permission.The path doesn't exist - but the parent path (if existing) DOES exist.This can be almost any path (and a drive on Windows). The mountpath will be set via the -mountpath argument and will set the target of fuse-wiiu. More information about the behavious on different fileformats can be found on "Supported formats". Directories will still be as expected, and whenever a support titles can be mounted, it will be emulated as directory with the prefix. If a folder was chosen as input, it will be mirrored to the mounpath, but normal files be hidden. In most cases this will be a folder, but it's also possible to choose a WUD/WUX directly. The most imported argument in the -in argument which defines the input path. Usageįuse-wiiu will be started from the command line and requires Java 8 and a fuse implementation (see Setup). More information can be found in "Supported formats". Example: if the title 000500101004B100 doesn't have a title.tik, wiiu-fuse will try to load a 000500101004B100.key from ~/.wiiu/titleKeys. Corresponding to the title id, a TITLEID.key is expected which contains the key in binary. If a installable title doesn't provide a title.tik, it's possible to provide the needed title key in the folder ~/.wiiu/titleKeys. key is expected to contain the disc key in binary. If it doesn't exist, it'll try to load ~/.wiiu/discKeys/mygame.key. Example: If a mygame.wux is found, a mygame.key will be searched in folder next the. This step is optionalÄisc keys are expected in ~/.wiiu/discKeys, and should have the same basename as the WUD/WUX. It's possible to provide the disc keys (for decrypting WUD/WUX) or titles keys (to decrypt tmd+app) in a seperate folder. It's also possible to provide it via an command line argument -devcommonkey with the key as hex-string. The dev common key optional for most titles but is expected in either ~/.wiiu/devcommon.key or. It's also possible to provide it via an command line argument -commonkey with the key as hex-string. The retail common key is expected in either ~/.wiiu/common.key or. To decrypt the titles, some keys are required. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |