1<html> 2<head> 3<meta http-equiv="Content-Type" content="text/html; charset=utf-8"> 4<LINK rel="stylesheet" type="text/css" href="../CSS/revolution.css"> 5<base target="main"> 6<title>Nmenu</title> 7</head> 8 9<body> 10 11<h1>Nmenu</h1> 12 13<h2>Location</h2> 14<p><code>$REVOLUTION_SDK_ROOT/RVL/bin/tools/Nmenu.elf</code></p> 15 16<h2>Overview</h2> 17<p> 18In Nmenu you can import WAD files, execute imported applications, and delete imported applications. Additionally auto import, auto run, and auto import/run can be performed by specifying options at startup time. A variety of modes and startup options are described below.<br> <br> <font color="red">Some of the operations have changed since version 2.0 of the NADK, corresponding to the addition of support for the Wii Remote.</font> 19</p> 20 21<h2>Mode Description</h2> 22<H3>1. IMPORT MODE</H3> 23<p> 24A list of the WAD files in <CODE><DvdRoot>/viewer</CODE> can be viewed. 25</p> 26<p> 27Select a WAD file using the Nintendo GameCube Controller or the Wii Remote +Control Pad up/down buttons, and press the A button to import. In Import Mode, the following information can be viewed (each file's information may be loaded by pressing the +Control Pad left/right buttons). 28</p> 29<ul> 30<li>Application game code</li> 31<li>Application game version</li> 32<li>The game version is shown when the application has been imported. If not imported, "Not installed" is displayed.</li> 33</ul> 34<p> 35Move to the next mode, Title List Mode, with the B button.</p> 36 37<H3>2. TITLE LIST MODE</H3> 38<p> 39A list of the imported applications can be viewed. 40</p> 41<p> 42If content files are lacking, such as when they have been deleted from the Wii Menu, applications will be displayed as <B>Incomplete</B>. Select an application using the Controller up/down buttons, and press the A button to execute. An application shown as <B>Incomplete</B> cannot execute, so you will need to import that application again. In addition, when an application is incomplete, you may not be able to obtain the information displayed below, and instead only <B>?</B> will be displayed. 43</p> 44<p> 45An application can be deleted by pressing the X button on the Nintendo GameCube Controller or the 1 button on the Wii Remote. All the imported applications can be deleted by pressing the Y button on the Nintendo GameCube Controller or the 2 button on the Wii Remote. In Title List Mode, the following information can be viewed (information may be toggled using the Controller or +Control Pad left/right buttons, as with Import Mode). 46</p> 47<ul> 48<li>Application game code</li> 49<li>Application game version</li> 50<li>Application company code</li> 51<li>Number of contents used by the application (number of dedicated and shared contents)</li> 52</ul> 53<p> 54The B button switches to SD Browser mode. 55</p> 56 57<H3>3. SD Browser Mode</H3> 58<p> 59A list of files on an SD Card can be seen when an SD Card is inserted. Any WAD files on the SD Card can also be imported. <b>Only WAD files can be imported.</b> 60</p> 61<p> 62Files or directories can be selected using up/down on the Controller or +Control Pad. A selected directory can be opened with the A button, and the contents of that directory will be shown. If the selected item is a WAD file, it can be imported. A file or directory can be deleted by pressing the X button on the Nintendo GameCube Controller or the 1 button on the Wii Remote. It can be moved to the root directory by pressing the Y button on the Nintendo GameCube Controller or the 2 button on the Wii Remote. Return to Import Mode with the B button.<br> <br>In any mode, <CODE>OSReturnToMenu</CODE> is called by pressing START on the Nintendo GameCube Controller or HOME on the Wii Remote. 63</p> 64 65<h2>Auto Import/Run</h2> 66<p> 67When starting <CODE>Nmenu</CODE> with <CODE>ndrun</CODE>, auto import and auto run can be performed by specifying the following options after <CODE>-a</CODE>. However, to use auto run by itself, the application must be imported in advance.<br> <br>Starting with NADK version 2.0, options <CODE>e</CODE> and <CODE>d</CODE> have been added. Option <CODE>e</CODE> is used for simulating a MEM2 size of 128MB; <CODE>d</CODE> is used for debugging. These options can be enabled by specifying them together with the automatic execution option <CODE>l</CODE> (lower case L). Be aware that if the debugger option is specified but you are not performing debugger startup using CodeWarrior, the application will not start. The <CODE>e</CODE> and <CODE>d</CODE> options may be specified together. 68</p> 69<TABLE border="1" > 70 <tr> 71<TD valign="top" width="120" bgcolor="#ffffe8"><CODE><STRONG><EM>-i</EM></STRONG></CODE></TD> 72<TD width="720">Continues to import specified <CODE>.wad</CODE> files automatically. <b><font color="red">The <CODE>.wad</CODE> files must be located in <CODE>${DvdRoot}/viewer</CODE>.</font></b></TD> 73 </tr> 74 <tr> 75<TD valign="top" width="120" bgcolor="#ffffe8"><CODE><STRONG><EM>-l</EM></STRONG></CODE></TD> 76<TD width="720">Lowercase L ("<CODE>l</CODE>"). Continues to execute specified applications automatically. Note that what is specified is the initial code (for example: 0001) and not the name of a .<CODE>wad</CODE> file (for example: <CODE>cntdemo.wad</CODE>).<font color="red">The method was changed to the specification of the initial code beginning with NADK version 2.0. </font><br>As mentioned above, if <CODE>e</CODE> is specified at the same time, a MEM2 size of 128MB will be simulated. If <CODE>d</CODE> is simultaneously specified, it will run in debugger startup mode.</TD> 77 </tr> 78 <tr> 79<TD valign="top" width="120" bgcolor="#ffffe8"><CODE><STRONG><EM>-il</EM></STRONG></CODE></TD> 80<TD width="720">Continues to import and execute the specified <CODE>.wad</CODE> files automatically.<br>Similarly, if <CODE>e</CODE> is simultaneously specified, simulation will be performed with a MEM2 size of 128MB. If <CODE>d</CODE> is simultaneously specified, it will run in debugger startup mode.</TD> 81 </tr> 82</TABLE> 83<p> 84The following is the command for automatically importing and executing <CODE>cntdemo.wad</CODE>:<br>(This assumes <CODE>cntdemo.wad</CODE> is located in <CODE>dvddata/viewer</CODE>.) 85</p> 86<TABLE border="1" width="100%"> 87 <TBODY> 88 <TR> 89 <TD width="100%"> 90 <PRE><CODE> 91% ndrun Nmenu.elf -a -il cntdemo.wad</CODE></PRE> 92 </TD> 93 </TR> 94 </TBODY> 95</TABLE> 96<p> 97The following is the command for automatically executing <CODE>cntdemo.wad</CODE> (Game Code 0001) with a MEM2 size of 128MB:<br>(This assumes <CODE>cntdemo.wad</CODE> has already been imported.) 98</p> 99<TABLE border="1" width="100%"> 100 <TBODY> 101 <TR> 102 <TD width="100%"> 103 <PRE><CODE> 104% ndrun Nmenu.elf -a -le 0001</CODE></PRE> 105 </TD> 106 </TR> 107 </TBODY> 108</TABLE> 109 110<h2>Nmenu.wad</h2> 111<p> 112Starting with Revolution SDK 3.2, a WAD file has been added to the package for Nmenu. Once the Nmenu WAD file has been imported as a Channel, procedures for starting discs and ELF files can be subsequently omitted. 113</p> 114<p> 115The <CODE>Nmenu.wad</CODE> file has basically the same controls and specifications as the normal <CODE>Nmenu.elf</CODE>. However, there is no feature for importing from a disc and therefore no Import Mode. It will be set to Title List Mode at startup time. Import NAND applications from an SD Card in SD Browser Mode. 116</p> 117 118<h2>Import Errors and Error Handling Procedures</h2> 119<p> 120<table class="arguments" border="1" cellspacing="0"> 121 <tbody> 122 <tr> 123<td bgcolor="#C0C0C0", width=10%>Error Codes</td> 124<td bgcolor="#C0C0C0">Error Descriptions and Error Handling Procedures</td> 125 </tr> 126 <tr> 127 <td>-1010</td> 128 <td> 129 An error writing to Wii console NAND memory. Occurs when there is insufficient available space in Wii console NAND memory. Check whether there is enough available space to import this WAD file. If there is enough space, restart Nmenu and try to import again. 130 </td> 131 </tr> 132 <tr> 133 <td>-1022</td> 134 <td> 135 This error is generated when inconsistencies are discovered between the WAD file header information and the content file itself. The error may occur for the following reasons. 136 <ol> 137 <li>The file may be corrupt. Try copying the file to <CODE>DvdRoot/SD Card</CODE> again or creating the WAD file again.</li> 138 <li>A blank file of 0 bytes may have been specified at the time of creation. Check whether a blank 0-byte DOL file or archive was specified at creation time due to a build or archive failure.</li> 139 <li>When the attempt was made to import a locally created data title, there might already have been a data title with the same game code. It might have been downloaded from a server with the e-commerce feature. You can import the file by first using Nmenu to delete that application, but note that this creates inconsistencies with the data on the server.</li> 140 </ol> 141 </td> 142 </tr> 143 <tr> 144 <td>-1035</td> 145 <td> 146 An attempt was made to import and overwrite a WAD file configured with a game version that cannot be downgraded. If you first use Nmenu to delete the application you can then import normally. You cannot resolve this problem by selecting <B>Data Management</B> from the Wii Menu and deleting the application.</td> 147 </tr> 148 <tr> 149 <td>-2011</td> 150 <td> 151 The WAD file failed the validity check. The file may be corrupt. Try copying the file to <CODE>DvdRoot/SD Card</CODE> again or creating the WAD file again.</td> 152 </tr> 153 <tr> 154 <td>-3001</td> 155 <td> 156 This error occurs when the header information in the WAD file is invalid. Check whether you tried importing a file that is not a WAD file because the extension was altered, for example, during renaming.</td> 157 </tr> 158 <tr> 159 <td>-3004</td> 160 <td> 161 The file failed to open. Try starting Nmenu again. If this does not solve the problem, try changing to another SD Card. 162 </td> 163 </tr> 164 <tr> 165 <td>-3005</td> 166 <td> 167 The file failed to load. Try starting Nmenu again. If this does not solve the problem, try changing to another SD Card.</td> 168 </tr> 169 </tbody> 170</table> 171<p>If import fails for reasons other than the above errors, or if the problems cannot be resolved using the methods mentioned above, please contact support@nintendo.com.</p> 172 173<h2>Restoring Corrupt Icons That Have Been Imported</h2> 174<p> 175Nmenu can delete titles with corrupt icons that have been imported to the development machine. If the Wii Menu is installed on the development machine, then Nmenu must start automatically. If you use <CODE>Nmenu-for-corrupted-icon_xx.gcm</CODE> then Nmenu can start automatically even if the Wii Menu has been imported. Nmenu will start even if you do not perform any operations on the Heath and Safety screen. After Nmenu starts, delete the problem titles. <br> 176</p> 177 178<h2>Notes</h2> 179<ul> 180<li> 181<b>The game version is also affected when a WAD file is imported in Nmenu, overwriting an earlier WAD file. </b>To read about game version rules, see the <a href="intro.html">Introduction</a>.<br><br> 182</li> 183<li> 184By default, applications are generated with a game code of "<CODE>0001</CODE>" (<CODE>0x30303031</CODE>), so the application is overwritten when another is imported. To prevent overwriting, use the <CODE>WAD_OPTION</CODE> option in <CODE>make</CODE> (or the <CODE>makeWad</CODE> option) to specify a game code. <br><br> 185</li> 186<li> 187Note that if you start Nmenu with the Wii Menu installed and run <B>Delete All</B>, the Wii Menu uninstaller will be deleted as well. If it has been deleted, you can use the firmware update program (<CODE>fwupdate</CODE>), included in the Revolution SDK, to uninstall the Wii Menu. However, Channels will not be deleted by this method. Reinstall the Wii Menu and then uninstall the Channels using normal procedures. <br><br> 188</li> 189<li> 190Nmenu checks the available space in NAND memory when applications are being installed. It displays a warning if there is insufficient space, but you can choose to ignore the warning and continue the installation process. Note that in such cases the installation may encroach on space reserved by the system. This will not trigger any major problems such as corrupting the system. However, it may affect some applications that make use of this region. You can resolve the problem by uninstalling the installed applications. <br><br> 191</li> 192</ul> 193 194<h2>Revision History</h2> 195<p> 1962010/01/06 Revised the note regarding available memory space.<br>2009/11/24 Added notes regarding available memory space.<br>2009/07/27 Added information about the cause and workaround for a -1010 error.<br>2009/07/06 Explained how to restore a corrupt icon that has been imported.<br>2009/04/07 Added import errors and error handing procedures.<br>2008/07/09 Added the Nmenu WAD file to the package. Added notes and workarounds related to <B>Delete All</B> on the Wii Menu.<br>2008/06/05 Added mention of the game version's effect on overwrite-imports in Nmenu.<br>2008/01/28 Added the process for handling cases where content files and system files have been deleted.<br>2008/01/11 Changed the description of the import error caused by differing game versions.<br>2007/11/20 Standardized use of "Nmenu."<BR>2007/09/10 Added information on game versions. Deleted an explanation related to deleting shared content.<br>2007/05/10 Added the automatic execution option. Revised the Wii Remote operation methods.<br>2006/10/25 Added an SD Mode to Nmenu.<BR>2006/09/15 Added a precaution regarding automatic execution.<BR>2006/08/15 Initial version. 197</p> 198 199<hr><p>CONFIDENTIAL</p></body> 200</html> 201