Nintendo Wii U Instruction Manual

© 2006 Nintendo RVL-06-0179-001-A
CONFIDENTIAL Released: October 4, 2006
Wii Optical Disc Drive Guidelines
Version 1.46
© 2006 Nintendo

Wii Optical Disc Drive Guidelines
RVL-06-0179-001-A © 2006 Nintendo
Released: October 4, 2006 CONFIDENTIAL
"Confidential"
These coded instructions, statements, and computer programs contain proprietary
information of Nintendo of America Inc. and/or Nintendo Company Ltd., and are pro-
tected by Federal copyright law. They may not be disclosed to third parties or copied
or duplicated in any form, in whole or in part, without the prior written consent of Nin-
tendo.
© 2006 Nintendo
TM and ® are trademarks of Nintendo.
Dolby, Pro Logic and the Double-D symbol are trademarks of Dolby Laboratories.
IBM is a trademark of International Business Machines Corporation.
Roland GS Sound Set is a trademark of Roland Corporation U.S.
All other trademarks and copyrights are property of their respective owners.

Graphics Library (GX)
© 2006 Nintendo RVL-06-0179-001-A
CONFIDENTIAL Released: October 4, 2006
WiiTM Optical Disc Drive Guidelines
Version 1.46 (For Nintendo GameCubeTM) + Revisions for Wii
Table of Contents
Revision History ........................................................................................................................................ iii
1 Overview.............................................................................................................................................. 1
2 About the Game Discs......................................................................................................................... 2
2.1 Game Disc Structure .................................................................................................................2
2.2 Game Disc ID ............................................................................................................................2
3 Guidelines for Error-handling............................................................................................................... 3
3.1 Error-Handling Policy with Optical Disc Drive Device Driver .....................................................3
3.2 Error Types that Developers Need to Resolve ..........................................................................3
3.2.1 Disc Cover Open Error (Wii has no cover).......................................................................3
3.2.2 No Disk Error ................................................................................................................... 3
3.2.3 Wrong Disk Error..............................................................................................................4
3.2.4 Retry Error ....................................................................................................................... 4
3.2.5 Fatal Error ........................................................................................................................ 4
3.3 Changing Error Messages .........................................................................................................4
3.4 How to Get the Error Type.........................................................................................................4
3.5 State Diagram............................................................................................................................6
3.6 Error-handling During Audio Streaming (Not required for Wii) ..................................................6
3.6.1 Error-handling During Preparation for Audio Streaming (Not required for Wii) ................ 6
3.6.2 Error-handling After Starting Audio Streaming (Not required for Wii) .............................. 7
3.6.3 Restarting Audio Streaming After it has Been Halted Due to an Error (Not required for Wii)
..........................................................................................................................................7
3.7 How to Emulate Errors...............................................................................................................7
4 Games with Multiple Game Discs........................................................................................................ 9
4.1 Game Disc exchange Process Patterns .................................................................................... 9
4.2 Specifying Game Discs at Time of Exchange..........................................................................10
4.2.1 Wild Card Usage Restrictions (Non-Game Versions) ....................................................10
4.2.2 Wild Card Usage Restrictions (Game Versions) ............................................................10
4.3 The Game Disc Exchange Procedure .....................................................................................11
4.4 Messages and Error Processing when Switching Game Discs ...............................................11
4.5 Multi-disc Emulation.................................................................................................................12
4.6 APIs for multi-disc games ........................................................................................................12
4.7 Cautions regarding multi-disc games ......................................................................................12
4.7.1 Every Game Disc should boot on its own ......................................................................12
4.7.2 Provide support for the exchange with any Game Disc .................................................12
4.7.3 Display for Game Disc exchanges .................................................................................12
4.7.4 Use labels and banners to distinguish Game Discs.......................................................12
4.7.5 Secure Memory for FST.................................................................................................13
5 Other Guidelines Regarding Accessing the Optical Disc Drive .........................................................14
5.1 Game Startup Screen ..............................................................................................................14
5.2 Various Causes of Changes in Game Disc Access Time........................................................14
5.3 dol File Restrictions .................................................................................................................14
5.4 Banner File for Game Disc Information and Displaying it in IPL Main Menu (In Wii display sep-
arate icon and banner)15
5.5 Avoid Infinite Loop of Hardware/Audio Streaming Under the Following Conditions ................16
5.5.1 Examples of Problems and How to Solve Them............................................................17
6 Other Cautions ..................................................................................................................................18

Graphics Library (GX)
RVL-06-0179-001-A ii © 2006 Nintendo
Released: October 4, 2006 CONFIDENTIAL
6.1 Describing Nintendo GameCube Optical Media ......................................................................18
Figures
Figure 1 - State Changes...........................................................................................................................6
Figure 2 - An example of Game Disc information display........................................................................ 16

Graphics Library (GX)
© 2006 Nintendo iii RVL-06-0179-001-A
CONFIDENTIAL Released: October 4, 2006
Revision History
Version Revision
Date Description of Revisions
1.46 9/29/06 • Updates for Wii. For provisional supply of information. Plan to move to Disc
Drive Library Programming Manual.
1.46 4/21/04
5/28/04
• Added table of error emulation methods for each development instrument.
• Added Chapter 6 “Other Cautions” and 6.1 regarding the description of
Nintendo GameCube optical media.
1.45 11/28/03 • Made the restriction in paragraph 5.3 a recommendation, that the total
section size should be less than 4 megabytes.
1.44 2/5/03 • Changed the instructions for distinguishing discs.
1/9/03 • Added a warning about problems with the boot program.
1.43 11/15/02 • Revised and added a note to paragraph 3.2.5 “Fatal Error”.
• Rewrote paragraphs 3.6 “Error-handling During Audio Streaming” and 3.7
“How to Emulate Errors”.
• Revised paragraph 4.7.5 “Secure Memory for FST”.
• Revised paragraph 5.4 “Banner File for Game Disc Information and
Displaying it in IPL Main Menu”.
1.42 8/09/02 • Replaced disc number with game version as an example of a wild card
in paragraph 4.2.
• Revised paragraph 4.5 to reflect updates to the AMCDDK.
• Revised paragraph 3.7 to reflect added functionality in the optical disc
emulator.
• Revised message for switching Game Discs in paragraph 4.4
• Added note to paragraph 3.6.
• Added explanation to note in paragraph 3.2.
1.41 3/29/02 • Changed recommended message for Disc Cover Open error.
1.4 2/20/02 • Added sections related to the multi-disc function
1.3 12/3/01 • Added paragraph 3.6.
1.2.2 8/31/01 • Added notes to paragraphs 2.2 and 2.4,
• Revised paragraph 2.6
1.2.1 8/3/01 • Revised messages in paragraphs 2.2.4 and 2.2.5
• Added paragraph 2.3
• Changed Game Disc to song at end of paragraph 2.6
• Revised paragraph 3.1
• Added paragraph 3.5
1.01 7/13/01 • Released by NOA

Graphics Library (GX)
RVL-06-0179-001-A iv © 2006 Nintendo
Released: October 4, 2006 CONFIDENTIAL

Graphics Library (GX)
© 2006 Nintendo 1RVL-06-0179-001-A
CONFIDENTIAL Released: October 4, 2006
1Overview
This document offers guidelines when using the Wii optical disc drive to design games that are user-
friendly with regard to Game Disc access. This document differs from the "Revolution Optical Disc Drive
Library (DVD.pdf)" document, in that it is meant not only for the programmers, but also for the designers
(who design the screen layout for error messages) and the like, and for the bug testers. For information
that is more specific to programming, see this section in the Revolution Optical Disc Drive Library (DVD).

Graphics Library (GX)
RVL-06-0179-001-A 2© 2006 Nintendo
Released: October 4, 2006 CONFIDENTIAL
2 About the Game Discs
2.1 Game Disc Structure
The structure of each Game Disc can be broadly divided into two components:
• The program part (the .dol file)
• The user file part
The dol file is the game program itself, converted from the elf file when ndrun is executed. Because the for-
mat of the elf file built by the program will differ slightly depending on the linker, the elf file is converted into
a custom-format dol file for storage on the Game Disc. The dol file is loaded and executed by the IPL.
The user file part is the component that is treated as files by the program part of the Game Disc. It does not
matter how these files are used (for data, for re-locatable modules, etc.).
2.2 Game Disc ID
Each Game Disc has a region for storing its unique ID. This unique ID is comprised of the following four
elements:
• Game code
Each game has its own specific code. The code is set by the NOA Lot Check Department.
• Company code
Each publisher has their own specific code. This code is obtained through the NOA Lot Check Depart-
ment for the US market and NOE Lot Check Department for the European market.
• Game Disc number
Every Game Disc for each game is allocated a Game Disc number. The first Game Disc of a game is
numbered "0" and subsequent Game Discs are numbered 1, 2, 3…
•Gameversion
Every version of the game is allocated a game version. It does not matter whether the game has been
released or not.
The Optical Disc Driver uses the Game Disc ID to determine whether the Game Disc is a correct Game
Disc.

Graphics Library (GX)
© 2006 Nintendo 3RVL-06-0179-001-A
CONFIDENTIAL Released: October 4, 2006
3 Guidelines for Error-handling
3.1 Error-Handling Policy with Optical Disc Drive Device Driver
The error-handling policy of our optical disc drive device driver is “polling”. No complicated error-handling
routine is needed. All the game developer needs to do is to poll the “error type” and show the proper mes-
sage on the screen.
3.2 Error Types that Developers Need to Resolve
There are four “error types” that developers need to resolve.
• Disc Cover Open Error (Wii has no disc cover)
•NoDiscError
• Wrong Disc Error
• Retry Error
• Fatal Error
A description of each error type follows.
Note: These errors are generated when the issued command is not processed normally for some rea-
son. They will not occur unless a command is issued. For example, when no command has been
issued, a No Disc error will not occur, even if a disc is ejected. Additionally, the developer does not
need to inform the game player about these status changes when they do not generate errors. In
other words, even if the game player ejects the disc during gameplay, you do not need to display
this message until the Game Disc is accessed.
3.2.1 Disc Cover Open Error (Wii has no disc cover)
When the game player opens the Disc Cover of the optical disc drive, this error will occur. Display the fol-
lowing message instructing the user to close the Disc Cover:
“The Disc Cover is open. If you want to continue the game, please close the Disc Cover.”
3.2.2 No Disc Error
This error occurs when the optical disc drive cannot find a Wii Disc. Display the following message and
instruct the user to insert the appropriate disc:
“Please insert the <Game Title> Game Disc.”
This error may also occur in the following situations:
• The Wii Disc is inserted upside down.
• A disc that is not a Wii Disc, for example if a 12cm CD, is inserted.
• An extremely dirty Wii Disc is inserted.
If the game has multiple Game Discs, please display some message like:
"Please insert <Game Title> Game Disc 1"
to clearly indicate which Game Disc must be inserted.

Graphics Library (GX)
RVL-06-0179-001-A 4© 2006 Nintendo
Released: October 4, 2006 CONFIDENTIAL
3.2.3 Wrong Disc Error
This error occurs when the wrong Game Disc has been placed in the drive. Display the following message
and instruct the user to insert the correct Game Disc:
“Please insert the <Game Title> Game Disc.”
Please be explicit when specifying which Game Disc to insert, when there are several discs in a set. For
example:
“Please insert <Game Title> Game Disc 1.”
3.2.4 Retry Error
This error occurs when there is dust, fingerprints, etc. on the Game Disc and it cannot be accessed. Dis-
play the following message instructing the user to read the Instruction Booklet. (The Instruction Booklet
tells the user to wipe the surface of the Game Disc with a soft cloth and then restart the game.)
“The Game Disc could not be read. Please read the Wii operations manual for more information.”
If a disc is inserted after a disc has been ejected, the device driver automatically performs a retry.
3.2.5 Fatal Error
This error occurs when a problem is detected that may make it impossible for the optical disc drive to
recover. Display the following message instructing the user to read the operations manual.
“An error has occurred. First press the Eject Button and eject the disc. Then turn the Wii console power off
and refer to the Wii operations manual for further instructions.”
There may be a problem with the optical disc drive or the Game Disc, so you need to stop the game after
displaying an error message.
Note: When there is a Fatal error, we recommend that you disable RESET during the presentation of the
error message. (Give priority to the display of Fatal error message).
3.3 Changing Error Messages
The error messages in Chapter 3.2 “Error Types that Developers Need to Resolve” are just examples of
these messages. You may revise these messages, as long as the meaning is accurately conveyed to the
user.
However, messages like Retry error and Fatal error reference the Wii operations manual for procedures to
handle their associated errors. In order to avoid user confusion, do not make any major alterations to these
messages.

Graphics Library (GX)
© 2006 Nintendo 5RVL-06-0179-001-A
CONFIDENTIAL Released: October 4, 2006
3.4 How to Get the Error Type
This section explains how an application can retrieve the optical disc error type.
The error type shows the device driver’s status. The device driver status can be obtained by calling the
function DVDGetDriveStatus.
Note: As mentioned in Chapter 3.2 “Error Types that Developers Need to Resolve”, errors only occur
when commands cannot be processed properly. So, no errors will occur if no commands have
been executed. For example, even if the disc is ejected, the function DVDGetDriveStatus will
not return DVD_STATE_NO_DISK (described below) if there is no command being executed. The
functions DVDGetFileInfoStatus and DVDGetCommandBlockStatus behave in the same
manner.
The following list indicates states the function will return when an error has occurred.
• DVD_STATE_COVER_OPEN (Wii has no disc cover)
• DVD_STATE_NO_DISK
• DVD_STATE_WRONG_DISK
• DVD_STATE_RETRY
• DVD_STATE_FATAL_ERROR
There are other states that can be returned from the function DVDGetDriveStatus(). They are not men-
tioned here because they do not indicate errors, and this document focuses on error handling. Refer to the
Revolution SDK Function Reference Manual for details on other states.
Note: For a game that has multiple Game Discs, DVD_STATE_MOTOR_STOPPED is returned when
Game Discs are exchanged. See Chapter 4 “Games with Multiple Game Discs” for details.
Below is pseudo-code for handling errors. For an operational demo, see the DVD sample demo, “errorhan-
dling” in the Revolution SDK.
Code 1 - Pseudo-code for Error-handling
DVDReadAsync();
do{
status = DVDGetDriveStatus();
switch (status){
case DVD_STATE_NO_DISK:
show_message_for_no_disk_on_screen();
break;
case DVD_STATE_WRONG_DISK:
show_message_for_wrong_disk_on_screen();
break;
case DVD_STATE_RETRY:
show_message_for_retry_on_screen();
break;
case DVD_STATE_FATAL_ERROR:
show_message_for_fatal_error_on_screen();
break;
}
}while (status != DVD_STATE_END) && (status != DVD_STATE_FATAL_ERROR);
In order to display an appropriate error message when a problem occurs, this routine calls the function
DVDGetDriveStatus every frame and polls the state.

Graphics Library (GX)
RVL-06-0179-001-A 6© 2006 Nintendo
Released: October 4, 2006 CONFIDENTIAL
The APIs that access the optical disc drive only return when processing is completed or if a fatal error
occurs. “Return” here means that callback is called (callback is specified with an asynchronous function),
or API ends processing and returns a value (with a synchronous function).
You can also use the function DVDGetFileInfoStatus or DVDGetCommandBlockStatus to get the
error state. These return the states of the designated file info and command block. The function DVDGet-
DriveStatus returns the state of the currently executing request.
3.5 State Diagram
The following diagram shows how the state (error type) changes.
Figure 1 - State Changes
An explanation of Figure 1 follows:
• From {No Disc, Wrong Disc, Retry} to Busy
This state change occurs when the disc is inserted. Note that the state does not change when the disc
is ejected.
•High-speed Change of Status due to Interrupt (Wii does not have one)
For example, if the Disc Cover is closed, the interrupt will take place and be processed internally. The
device driver changes states so polling is not required, making the processing minimal.
• Calibration Time when disc is inserted
Please note that when the disc is inserted, the calibration processing of the optical disc drive takes
time. For example, if in the WRONG_DISK state, it takes time to change discs and then a driver checks
the Disc ID.
3.6 Error-handling During Audio Streaming (Not required for Wii)
Use the same procedure that is described in Chapter 3.4 “How to Get the Error Type”. Note that with this
procedure, there are times when an error cannot be detected. If no error can be detected, there is no need
to use some other method in search for one.

Graphics Library (GX)
© 2006 Nintendo 7RVL-06-0179-001-A
CONFIDENTIAL Released: October 4, 2006
3.6.1 Error-handling During Preparation for Audio Streaming (Not required for
Wii)
Before the start of audio streaming, preparations must be made by executing the DVDPrepareStream
function. If an error occurs during this preparation process, the error can be detected by using the proce-
dure described in Chapter 3.4. That is to say, by calling the DVDGetDriveStatus function.
When an error is detected at this time, it is essential to notify the game player.
3.6.2 Error-handling After Starting Audio Streaming (Not required for Wii)
The DVDGetDriveStatus function cannot detect errors that occur after starting audio streaming. But
there is no need to use some other method to detect errors and no need to notify the game player if one is
detected.
3.6.3 Restarting Audio Streaming After it has Been Halted Due to an Error (Not
required for Wii)
If an error occurs during audio streaming the audio stream will halt, and it will not automatically start again,
even if the cause of the error has been removed. The developer is free to decide whether in such cases to
execute the DVDPrepareStream function again and restart the audio stream.
Consider the situation where the Disc Cover is opened while an audio stream is executing. When that hap-
pens the audio stream will halt. It is up to the developer to decide whether or not the audio stream should
start up again when the Disc Cover is closed.
3.7 How to Emulate Errors
Developers must check that appropriate error-handling routines (e.g., displaying appropriate error mes-
sages on the TV) are executed in their program. All of the different kinds of errors (Wrong Disc, Retry, and
Fatal Error) can be emulated using NDEV. For details see the NDEV manual.
DDH
All of the errors can be emulated using AMCDDK Version.3.0.2 patch #2 or later. For details, read the
AMCDDK manual.
NPDP-GDEV
All of the errors can be emulated using Version 1.01 or later. For details, read the NPDP-GDEV manual.
If you will be using the NPDP-GDEV with an inserted NPDP cartridge, read the section below concerning
NPDP.

Graphics Library (GX)
RVL-06-0179-001-A 8© 2006 Nintendo
Released: October 4, 2006 CONFIDENTIAL
NPDP
All of the errors can be emulated using Version 1.0.003 or later firmware. For Retry Error and Fatal Error,
especially, refer to the table below:
Table 1 - Error Emulation Method for Each Development Instrument
Note 1: Error appears when you hold down the button until the next disc access.
Note 2: Use different disc IDs for the disc after exchange and the disc before exchange.
Note 3: Occasionally a Retry error will be generated if buttons are not pressed in this order:
Press and hold down UP button or Disk Change button, then press Error button.
Retry Error Fatal Error
(Note 1) Wrong Disk Error No Disk Error
NDEVNPDP-
GDEV
OdemSry
(RETRY button)
OdemSry
(FATAL button)
OdemSry
(Cover Open)
OdemSry
(Select DLF File)
OdemSry
(Cover Close)
OdemSry (Eject)
OdemSry (Load)
OdemSry
(Cover Open)
OdemSry
(No Disk)
OdemSry
(Cover Close)
OdemSry (Eject)
OdemSry (Load)
NPDP
with
NPDP-GBOX
Error Button
(Note 1)
UP Button +
Error Button
(NPDP firmware
v 1.0.003 and
later (Note 1))
(Note 3)
Open/Close Button
UP Button/DOWN But-
ton
Open/Close Button
Open/Close Button
UP Button/DOWN
Button
(Select No Disk)
Open/Close Button
NPDP
with
NPDP Console
Error Button
(Note 1)
Disk Change
Button + Error
Button
(NPDP firmware
v 1.0.003 and
later (Note 1))
(Note 3)
Open/Close Button
Disk Change
Button
Open/Close Button
Open/Close Button
Disk Change
Button
(Select No disk)
Open/Close Button
RVT-R Reader
NR Reader
None None Exchange disk
(Note 2)
Remove disk
DDH >dirtydisk >breakdrive >loadrun myapp.elf
>opencover
>changedisk myapp.elf
editor “-dn=1”
>closecover
>loadrun myapp.elf
>opencover
>removedisk
>closecover

Graphics Library (GX)
© 2006 Nintendo 9RVL-06-0179-001-A
CONFIDENTIAL Released: October 4, 2006
4 Games with Multiple Game Discs (For Reference)
Please contact the NOA Licensing Department in advance, when considering games with several Game
Discs.
At the present time, such discussions are only for two-disc games, for which both discs are sold at the
same time. Please hold separate discussions with the Nintendo Licensing Department for games with
three or more Game Discs, or for the marketing of separate Game Discs.
If more than one Game Disc is needed for a single game, then the Game Discs must be exchanged at
some appropriate place in the game. The exchange is done by specifying the Game Disc ID for the next
Game Disc (see Chapter 2.2 “Game Disc ID”).
The rest of this chapter explains the different types of exchange patterns for multi-disc games and how to
specify Game Discs. It provides a broad description of the procedure for exchanging Game Discs, and
gives an example of a message displayed to instruct the player to exchange Game Discs.
4.1 Game Disc exchange Process Patterns
With multi-disc games, the Game Disc exchange process can be broadly classified into two patterns,
depending on whether or not the dol program part (Chapter 2.1 “Game Disc structure”) of the newly
inserted Game Disc is loaded and executed after Game Discs are exchanged. As an example, consider
the case where Game Disc 1 is removed and replaced with Game Disc 2.
• A When loading/running a Game Disc 2 dol file
After the switch from Game Disc 1 to Game Disc 2 is complete, please run the restart process.
Restarting will start the dol program on Game Disc 2.
• B When not loading/running a Game Disc 2 dol file
After the switch from Game Disc 1 to Game Disc 2 is complete, it will be possible to access the Game
Disc 2 user files (Chapter 2.1 “Game Disc structure”). There is nothing particular that has to be done
after the switch.
In this case, the system can be classified in two ways: to allow Game Disc 2 to start up by itself or not.
• B1 When allowing individual start up by Game Disc 2
It is conceivable that the programs on Game Disc 1 and Game Disc 2 could be the same, and only
the user file sections would be different. There may be a prompt to return to Game Disc 1,
depending upon the state of progress of the game in the Memory Card.
• B2 When not allowing individual start up by Game Disc 2
It is conceivable that Game Disc 2 could contain only data files. In this case, please display a mes-
sage like "This is a data only Game Disc. Please insert <Game Title> Game Disc 1.", and give the
user appropriate instructions when in individual start-up mode.
We don't really recommend B2 above. That's because it is possible that there could be Game Disc switch-
ing all the time, when a game is being run. Unless there is a particular reason for needing a data-only
Game Disc, we feel it is nicer to the user to have the same dol file on the second Game Disc as on the first
Game Disc, and make it possible to start-up on the second Game Disc by itself.
Comparing A and B1, B1 requires no loading of the dol program section on Game Disc 2, and the shift to
the second Game Disc will be somewhat faster. If the dol program portion of the first and second Game
Discs can be made the same, it would probably be better to choose B1.

Graphics Library (GX)
RVL-06-0179-001-A 10 © 2006 Nintendo
Released: October 4, 2006 CONFIDENTIAL
Note that in either case, we recommend making it possible to save data before switching Game Discs, for
the following reasons.
• Data loss can be avoided if there is a Game Disc read error after the switch.
• It will make debugging easier by saving the data to the Memory Card before exchanging the Game
Discs. When you have a bug either during or after the Game Disc exchange, you can easily reproduce
the bug using the saved data. If you don't save the data before the Game Disc exchange, you will have
to begin game play from the Game Disc 1 again, to reproduce the bug.
Caution
File structures that were open prior to the exchange will contain old data, so please do not use such data
after the exchange. Even if Game Disc 1 and Game Disc 2 have files with the same name, please be sure
to re-open them. To be safe, we recommend closing all open files before switching.
4.2 Specifying Game Discs at Time of Exchange
The Game Disc ID (see Chapter 2.2 “Game Disc ID”) is used for specifying Game Discs at the time of an
exchange. For details, refer to the DVDChangeDisk* function in the Revolution SDK Function Reference
Manual.
With the DVDChangeDisk* function, wildcards can be specified for Game Disc ID components. Thus,
if 0xff is specified for the Game Version, then no matter which version of the game is inserted during
the exchange, it will be treated as a correct Game Disc and the exchange will be approved, as long as
the other three Game Disc ID components (i.e., the Game Code, Company Code and Disc Number)
are correct.
In the following section, we offer some precautionary statements concerning wild cards.
4.2.1 Wild Card Usage Restrictions (Non-Game Versions)
Wild cards can only be used on game versions (not on Game Codes, Company Codes or Game Disc num-
bers). The reason is that when wild cards are used, the operation check combinations become enormous
and cause a lot of problems.
If you are nevertheless considering the use of wild cards for the elements other than game version, you
must discuss the matter with Nintendo in advance.
4.2.2 Wild Card Usage Restrictions (Game Versions)
When using wild cards for game versions, there are advantages and disadvantages to using and not using
them (when given explicit instructions). The following are some examples. Please review them and select
one or the other for use.
A When the Game Version is Explicitly Specified
• Advantages
The corresponding Game Disc versions have a one-to-one correspondence, so it is sufficient to debug
in that particular combination.
• Disadvantages
When there are future version changes, it will be necessary to upgrade the version on both Game
Discs. In other words, if Game Disc 1 specifies Game Disc 2 version 0, and Game Disc 2 was modified
to version 1 after it was sold, then once Game Disc 1 had been modified, the versions on both Game
Discs would have to be upgraded and resubmitted.

Graphics Library (GX)
© 2006 Nintendo 11 RVL-06-0179-001-A
CONFIDENTIAL Released: October 4, 2006
When a group of friends have their own copies of the same game and the versions are different and
two friends switch Game Discs, they will not work properly when Game Disc 1 and Game Disc 2 are
exchanged.
An identifying mark will be required on the label so that the version can be identified.
B When a Wild Card is Used in a Game Version
• Advantages
Independent version upgrades can be released at future dates on their own Game Discs.
Game Discs with different versions will keep running when they are used together, so friends can
switch Game Discs without any problems.
• Disadvantages
Care is required when releasing future version upgrades. In other words, when upgrading for example,
Game Disc 2, it will be necessary to assure that it can be switched with all of the Game Disc 1 versions
that are out circulating in the market.
4.3 The Game Disc Exchange Procedure
Below is an outline of the procedure that takes place from the time the player exchanges Game Discs until
the Wii can access the new Game Disc.
1. The Optical Disc Drive motor is stopped.
2. The optical disc drive motor is confirmed to be stopped, and a message is displayed telling the game
player to exchange Game Discs (see Chapter 4.4 “Messages and Error Processing when Switching
Game Discs”).
3. The system waits until the Disc Cover is opened by the player and then closed.
4. After the exchange, the Game Disc ID is checked to determine whether it is the proper Game Disc.
5. The Game Disc's File Symbol Table (FST) is loaded and access is enabled.
All of these procedures, except for the message display performed in (2), are processed by the DVD-
ChangeDisk function (See Chapter 4.6 “APIs for multi-disc games”).
You can determine the duration of the message displayed in Step 2, by using the DVDGetDriveStatus func-
tion to check the status of the Device Driver. You check the status of the Device Driver using the same
method you use for error handling (see Chapter 3.4 “How to get the error type”). When the optical disc
drive motor is stopped, the optical disc driver's status is DVD_STATE_MOTOR_STOPPED. Only display
the message in Step 2 when the optical disc driver is in this state.
If the exchanged Game Disc is not the proper Game Disc, or if there is no Game Disc in the optical disc
drive, then display an appropriate message like those shown in Chapter 4.4 “Messages and Error Process-
ing when Switching Game Discs”. The DVDChangeDisk* function can cancel the Game Disc exchange
process by calling the DVDCancel function.
4.4 Messages and Error Processing when Switching Game Discs
This section provides an example of a message to be displayed to the game player when Game Discs are
being exchanged. These sample displays are like the ones in Chapter 3.3 "Changing Error Messages,"
and they may be modified to communicate their intent to the game player.
• Instructing the player to exchange Game Discs
While the Device Driver is in the DVD_STATE_MOTOR_STOPPED state, display this message,
instructing the game player to insert the next appropriate Game Disc:
"Please insert <Game Title> Game Disc 2."
(Wii has no disc cover)

Graphics Library (GX)
RVL-06-0179-001-A 12 © 2006 Nintendo
Released: October 4, 2006 CONFIDENTIAL
If the game is a multi-disc game, be sure to provide clear instructions about which Game Disc should
be inserted next.
When you issue the DVDChangeDisk function, perform the same error handling that you would with the
DVDRead function. For details, see Chapter 3.2 “Error Types that Developers Need to Resolve” (If the
specified Game Disc is not inserted, then a Wrong Disk error should be generated.)
4.5 Multi-disc Emulation
Currenly, multi-disc emulation can be only be executed on NDEV.
4.6 APIs for Multi-disc Games
The following APIs apply to multi-disc games. For details about each API refer to the Revolution SDK
Function Reference Manual.
• DVDChangeDisk* (DVDChangeDisk as well as DVDChangeDiskAsync)
• DVDCompareDiskID
• DVDGenerateDiskID
• DVDGetCurrentDiskID
4.7 Cautions Regarding Multi-disc Games
4.7.1 Every Game Disc Should Boot on its Own
(Same content as Wii Programming Guideline, Version 1.00, paragraph 3.3 “[Only For Multiple Disc
Games] Independent Startup of All Discs [Required].”)
Even if startup of the application from a particular Wii Game Disc is not expected, always make sure that
some kind of program is executed when the disc is started independently, even if it is just a warning mes-
sage. For example, if the inserted Wii Game Disc is one of a set of two Wii Game Discs and the inserted
disc is one that cannot be played standalone, have available a program that displays a message such as
This is <game title> Game Disc 2. Please insert <game title> Game Disc 1 and restart power.”
Not doing so may cause the user to think that there is malfunction in either the Wii console or the Wii Game
Disc when a Wii Game Disc is not designed for independent startup.
Please design every Game Disc so it can boot up on its own when inserted in the Nintendo GameCube.
Have the Game Disc boot on its own -- even if the game's execution program cannot start up without the
execution program that is on some other Game Disc -- and then display a message instructing the game
player to exchange Game Discs (see Chapter 4.7.3 “Display for Game Disc exchanges”)
4.7.2 Provide Support for the Exchange with any Game Disc
Make sure the system does not lock-up, no matter what Game Disc is exchanged. For example, if Game
Disc 3 is only supposed to operate when it is booted after Game Disc 2, do not let the system lock-up if it is
exchanged after Game Disc 1 instead.
4.7.3 Display for Game Disc Exchanges
If an exchange of discs is necessary, please display instructions to this effect on the screen. See Section
4.4 “Messages and Error Processing when Switching Game Discs” to read about the contents of this
screen message.
“

Graphics Library (GX)
© 2006 Nintendo 13 RVL-06-0179-001-A
CONFIDENTIAL Released: October 4, 2006
4.7.4 Use Labels and Banners to Distinguish Game Discs
Print a label for each Game Disc, so game players can differentiate Game Discs and exchange them prop-
erly when instructed to do so. For details on banners and icons displayed by the Wii console, see “Icon and
Banner Creation Tool.”
4.7.5 Secure Memory for FST
When a normal Game Disc is exchanged, the File Symbol Table (FST) is overwritten by what is on the new
Game Disc. If the FST of the new Game Disc is smaller than the FST of the Game Disc that was swapped
out, then there is no problem. But if the new FST is larger, then it cannot be loaded. An ASSERT message
will be output, and the system will lock up.
To prevent this from happening, with a game that has multiple discs, be sure to secure a memory space of
adequate size for the FST. When using DDH, request the required FST size from each disc and specify
each value in FstMaxLen. When using NPDP-GDEV, register the group of discs in the mdf file. When this
is done, the appropriate FST size will be set automatically.
For further details, read the various development environment manuals.

Graphics Library (GX)
RVL-06-0179-001-A 14 © 2006 Nintendo
Released: October 4, 2006 CONFIDENTIAL
5 Other Guidelines Regarding Accessing the Optical Disc Drive
5.1 Game Startup Screen
After the dol file is loaded by the boot program, data and program files are read from the Game Disc. At
this time, in order to shorten the time the screen is blank as much as possible, do not read any data files.
Use only the dol file to display the first screen.
Also, the dol file should use the error-handling routines described in Chapter 3.4 “How to Get the Error
Type”. If there are no error-handling routines (including necessary data) built into the dol file, there is no
way to notify the user if some kind of problem occurs with the read before the error-handling routine’s data
is loaded.
Warning: (Not a concern with Wii)
There is a bug in the boot program that causes the system to halt under certain circumstances when the
game program is booted from the Main Menu screen. Specifically, if the Disc Cover is opened just at the
right moment while the screen fades out, the screen will remain faded out and the system will halt. The tim-
ing has to be just right for this to happen, so the rate of occurrence is very low. However, you should be
aware of this when testing the error handling of your game program. It is acceptable to ignore this bug.
Take the following steps if a problem arises and you want to determine whether it is due to this bug or to
some bug in the game program:
1. Try closing the Disc Cover. If the game program boots up, the problem was caused by a bug in the
game program.
2. Wait 10 seconds after closing the Disc Cover and then press the START button. If the game program
boots up, the problem was caused by the boot program bug. (This can be ignored.)
3. If the game program does not start up when you perform Step 2, then the problem was caused by a
bug in the game program.
This boot program bug does not occur when games are started from the Nintendo GameCubeTM logo (in
other words, booted up without going through the IPL Main Menu screen).
5.2 Various Causes of Changes in Game Disc Access Time
(Same as Wii Programming Guideline, Version 1.00, paragraph 2.1 “Prohibition of Dependency on Device
Specifications [Information]. Plan to add "Prohibition of Dependency on Device Specifications) [Required]”
to the disc drive chapter, as a disc drive related topic.)
Avoid designing a program with a dependency on the device specifications of the Wii console or its periph-
erals, since this may result in a program malfunction or crash.
There will be some specification variance between devices. Performance will also decrease as the device
ages or a disc becomes damaged.
Specifically, the devices here refer to the disc drive, disc, Wii Remote, Wii system memory, SD Memory
Card, and Nintendo GameCube Memory Card. See the corresponding chapters for details.
If a problem occurs with Game Disc access, the hardware will carry out a retry internally. This means that
even if a read has succeeded, it may have been the result of going through several retries.
Also, the calibration process requires a large amount of time, as mentioned in Chapter 3.5 “State Dia-
gram”. Therefore, when a game player opens the Disc Cover while reading, much longer time is required
than just one read.
Furthermore, due to individual differences, the access may be completed slightly faster than with the par-
ticular optical disc drive the developer is using.