iQueBrew - User contributions [en]

Ticket.sys

2018-05-06T13:38:43Z

Asper: Created page with "This file contains CMD and ticket information about purchased and trial titles. Single tickets can be extracted with iquetool and the single obtained files are dividied in 3 p..."

This file contains CMD and ticket information about purchased and trial titles.
Single tickets can be extracted with iquetool and the single obtained files are dividied in 3 parts:

{| class="wikitable"
|-
! Offset
! Length
! Type
! Description
! Information
|-
| 0x0
| 0x2800
| bytes
| opaque_data
| is_secure_app ?
|-
| 0x2800
| 0x1AC
| bytes
| CMD data
| [http://www.iquebrew.org/index.php?title=CMD CMD structure]
|-
| 0x29AC
| 0x1A0
| bytes
| Ticket data
| [http://www.iquebrew.org/index.php?title=Ticket Ticket structure]
|-
|}

Ticket

2018-05-06T10:44:37Z

Asper:

An iQue '''Ticket''' is used to store data about a piece of content and per-console information. It is contained inside the ticket file after the CMD data.

{| class="wikitable"
|-
! Offset
! Length
! Type
! Description
! Information
|-
| 0x00
| 0x04
| bytes
| console_id
| console id that this ticket is for
|-
| 0x04
| 0x02
| int16
| ticket_id
| if bit 15 set then this is a trial ticket
|-
| 0x06
| 0x02
| uint16
| limit_enum
| 0 or 2 = time, 1 = number of launches
|-
| 0x08
| 0x02
| int16
| limit_value
| number of minutes, or number of launches
|-
| 0x0A
| 0x02
| int16
| padding
| IV used to encrypt titlekey (with common key)
|-
| 0x0C
| 0x04
| int32
| ticket_crl_version
|
|-
| 0x10
| 0x10
| bytes
| titlekey_iv
| IV used to encrypt titlekey (with ecdh key)
|-
| 0x20
| 0x40
| int32
| ecc_pubkey
| used with console's ECC privkey to derive unique titlekey encryption key via ECDH
|-
| 0x60
| 0x40
| bytes
| signer
| certificate used to sign the ticket
|-
| 0xA0
| 0x100
| bytes
| signature
| RSA-2048, over rest of tik+all of CMD

CMD

2018-05-06T10:19:43Z

Asper: Created page with "An iQue '''Content MetaData (CMD)''' is used to store data about a piece of content, such as the size, hash and ID. It's used as part of the SKSA (for info about the SA1/S..."

An iQue '''Content MetaData (CMD)''' is used to store data about a piece of content, such as the size, hash and ID. It's used as part of the [[SKSA]] (for info about the SA1/SA2) and also used as part of the [[Title Data]] structure (for info about the game title).

Each ticket is signed via RSA-2048 using a CP (content protection?) certificate, the method for signing/verifying has been found for SA1/SA2, but game tickets don't seem to work. It's likely that some part of the structure is changed in memory just before the iQue validates it.

== Format ==
The CMD format is similar to a [http://wiibrew.org/wiki/Ticket Wii ticket], though it seems the structure was reworked sometime between the iQue and Wii.

It's assumed that the title key needed to decrypt an SA / .app is part of the structure, though likely encrypted with a common-key that's yet to be dumped from the console.

{| class="wikitable"
|-
! Offset
! Length
! Type
! Description
! Information
|-
| 0x0
| 0x8
| bytes
| ca_crl_version
| Unknown (always 0?)
|-
| 0x8
| 0x4
| int32
| cmd_crl_version
| Unknown (always 1?)
|-
| 0xC
| 0x4
| uint32
| content_size
| Content Size
|-
| 0x10
| 0x4
| int32
| unused_flags
| bit 0 on if SA; nothing checks it though
|-
| 0x14
| 0x10
| bytes
| titlekey_iv
| IV used to encrypt titlekey (with common key)
|-
| 0x24
| 0x14
| bytes
| content_hash
| sha1 hash of plaintext content
|-
| 0x38
| 0x10
| bytes
| content_iv
| IV used to encrypt content
|-
| 0x48
| 0x4
| int32
| recrypt_flag
| if bit 1 on, content will be re-encrypted on first launch, using console-unique key stored in Virage2 in the SoC
|-
| 0x4C
| 0x4
| int32
| allowed_hardware
| bitfield, each bit enables access to some MMIO regs new to iQue Player:
* bits 0-7: new PI stuff
* bit 0: PI buffer used for aes/NAND read output and PI DMA (1KB at PI_BASE+0x10000)
* bit 1: NAND flash regs in PI
* bit 2: memory mapper for old PI dma
* bit 3: hardware AES-engine in PI
* bit 4: new PI dma engine, DMAs from/to PI buffer
* bit 5: new GPIO; power + LED
* bit 6: external IO bus stuff (debug?)
* bit 7: new PI error stuff
* bit 8: enables access to USB regs
* bit 9: enables access to internal ram used for SK stack
(0 for games, 0x13 for iQue Club, 0x1F7/0x1B3 for SA)
|-
| 0x50
| 0x4
| int32
| allowed_secure_kernel_calls
| one bit per syscall bit 0 allows skc 0, etc.
|-
| 0x54
| 0x4
| int32
| console_id
| can be zero; if not can only run on certain (used for SAs, not games)
|-
| 0x58
| 0x40
| chars
| signer
| Authority (cert used to sign ticket)
|-
| 0x98
| 0x4
| uint32
| content_id
| Content ID (can't be higher than 99999999, if (cid / 100) % 10 == 9, this is a game manual)
|-
| 0x9C
| 0x10
| bytes
| titlekey
| crypted with common key, and if this is not an SA, then crypted again with key derived using ECDH of console's privkey and pubkey in ticket
|-
| 0xAC
| 0x100
| bytes
| signature
| RSA-2048 signature
|}

In different SAs which seem to have matching bytes in the encrypted data, the field at 0x38 seems to be the only constant between them, likely our best suspect for the title-key.

== Signature ==
The signature is made from a SHA1 hash of 0x0 - 0xAC. In SA1/SA2 this hash seems to be valid for the given signature, but for some reason game tickets don't seem to validate.

Comparing CMDs for the same game from two different devices, the area at 0x9C-0xAC seems to completely change, while the actual signature remains the same. It's likely that this area is probably decrypted using a per-device key just before verification.

=== Fake Signing ===
As the iQue is so similar to Wii it was guessed that fake-signing may be possible. Sadly tests done with SA1 tickets have all been unsuccessful, though it could be possible that the way SK validates signatures is completely different to how SA1/SA2 validates them (it may be that SK uses an Assembly version for validation, while SA1/SA2 use the C version shared with the Wii, though this is all just speculation at this point)

[[Category:File formats]]

Virage0-1

2018-05-06T10:16:48Z

Asper:

Virage0 and Virage1 are a 2 rewritable 64 (0x40) Byte memory regions located inside the SoC. They can only be read in secure mode. They contain play-time data.

{| class="wikitable"
|-
! Offset
! Size
! Description
! Note
|-
| 0x00 || 0x04 || ??? || seems to be always 00 00 01 00
|-
| 0x04 || 0x04 || ??? || seems to be always 00 00 00 1A
|-
| 0x08 || 0x02 x 26 || play-time || 600 minutes = 0x0258
|-
| 0x4C || 0x04 || CRC ||

Virage0-1

2018-05-06T10:16:26Z

Asper: Created page with "Virage0 and Virage1 are a 2 rewritable 64 (0x40) Byte memory regions located inside the SoC. They can only be read in secure mode. They contain play-time data. {| class="wiki..."

Virage0 and Virage1 are a 2 rewritable 64 (0x40) Byte memory regions located inside the SoC. They can only be read in secure mode. They contain play-time data.

{| class="wikitable"
|-
! Offset
! Size
! Description
! Note
|-
| 0x00 || 0x04 || ??? || seems to be always 00 00 01 00
|-
| 0x44 || 0x04 || ??? || seems to be always 00 00 00 1A
|-
| 0x08 || 0x02 x 26 || play-time || 600 minutes = 0x0258
|-
| 0x4C || 0x04 || CRC ||

Ticket

2018-05-06T09:49:33Z

Asper:

An iQue '''Ticket''' is used to store data about a piece of content, such as the size, hash and ID. It's used as part of the [[SKSA]] (for info about the SA1/SA2) and also used as part of the [[Title Data]] structure (for info about the game title).

Each ticket is signed via RSA-2048 using a CP (content protection?) certificate, the method for signing/verifying has been found for SA1/SA2, but game tickets don't seem to work. It's likely that some part of the structure is changed in memory just before the iQue validates it.

== Format ==
The ticket format is similar to a [http://wiibrew.org/wiki/Ticket Wii ticket], though it seems the structure was reworked sometime between the iQue and Wii.

It's assumed that the title key needed to decrypt an SA / .app is part of the structure, though likely encrypted with a common-key that's yet to be dumped from the console.

{| class="wikitable"
|-
! Offset
! Length
! Type
! Description
! Information
|-
| 0x0
| 0x8
| bytes
| ca_crl_version
| Unknown (always 0?)
|-
| 0x8
| 0x4
| int32
| cmd_crl_version
| Unknown (always 1?)
|-
| 0xC
| 0x4
| uint32
| content_size
| Content Size
|-
| 0x10
| 0x4
| int32
| unused_flags
| bit 0 on if SA; nothing checks it though
|-
| 0x14
| 0x10
| bytes
| titlekey_iv
| IV used to encrypt titlekey (with common key)
|-
| 0x24
| 0x14
| bytes
| content_hash
| sha1 hash of plaintext content
|-
| 0x38
| 0x10
| bytes
| content_iv
| IV used to encrypt content
|-
| 0x48
| 0x4
| int32
| recrypt_flag
| if bit 1 on, content will be re-encrypted on first launch, using console-unique key stored in Virage2 in the SoC
|-
| 0x4C
| 0x4
| int32
| allowed_hardware
| bitfield, each bit enables access to some MMIO regs new to iQue Player:
* bits 0-7: new PI stuff
* bit 0: PI buffer used for aes/NAND read output and PI DMA (1KB at PI_BASE+0x10000)
* bit 1: NAND flash regs in PI
* bit 2: memory mapper for old PI dma
* bit 3: hardware AES-engine in PI
* bit 4: new PI dma engine, DMAs from/to PI buffer
* bit 5: new GPIO; power + LED
* bit 6: external IO bus stuff (debug?)
* bit 7: new PI error stuff
* bit 8: enables access to USB regs
* bit 9: enables access to internal ram used for SK stack
(0 for games, 0x13 for iQue Club, 0x1F7/0x1B3 for SA)
|-
| 0x50
| 0x4
| int32
| allowed_secure_kernel_calls
| one bit per syscall bit 0 allows skc 0, etc.
|-
| 0x54
| 0x4
| int32
| console_id
| can be zero; if not can only run on certain (used for SAs, not games)
|-
| 0x58
| 0x40
| chars
| signer
| Authority (cert used to sign ticket)
|-
| 0x98
| 0x4
| uint32
| content_id
| Content ID (can't be higher than 99999999, if (cid / 100) % 10 == 9, this is a game manual)
|-
| 0x9C
| 0x10
| bytes
| titlekey
| crypted with common key, and if this is not an SA, then crypted again with key derived using ECDH of console's privkey and pubkey in ticket
|-
| 0xAC
| 0x100
| bytes
| signature
| RSA-2048 signature
|}

In different SAs which seem to have matching bytes in the encrypted data, the field at 0x38 seems to be the only constant between them, likely our best suspect for the title-key.

== Signature ==
The signature is made from a SHA1 hash of 0x0 - 0xAC. In SA1/SA2 this hash seems to be valid for the given signature, but for some reason game tickets don't seem to validate.

Comparing tickets for the same game from two different devices, the area at 0x9C-0xAC seems to completely change, while the actual signature remains the same. It's likely that this area is probably decrypted using a per-device key just before verification.

=== Fake Signing ===
As the iQue is so similar to Wii it was guessed that fake-signing may be possible. Sadly tests done with SA1 tickets have all been unsuccessful, though it could be possible that the way SK validates signatures is completely different to how SA1/SA2 validates them (it may be that SK uses an Assembly version for validation, while SA1/SA2 use the C version shared with the Wii, though this is all just speculation at this point)

[[Category:File formats]]

Virage2

2018-05-04T16:26:29Z

Asper:

Virage2 is a rewritable 256 (0xFF) Byte memory region located inside the SoC. It can only be read in secure mode, and is mapped to <tt>0xBFCA0000</tt>.

{| class="wikitable"
|-
! Offset
! Size
! Description
! Note
|-
| 0x00 || 0x14 || SK Hash || common
|-
| 0x14 || 0x10 x 4 || ROM Patch || common
|-
| 0x54 || 0x20 || EccPublicKey || per-console
|-
| 0x74 || 0x04 || bbId || per-console
|-
| 0x78 || 0x40 || EccPrivateKey || per-console
|-
| 0xB8 || 0x10 || bootAppKey (COMMON KEY)|| common
|-
| 0xC8 || 0x10 || recryptListKey || per-console
|-
| 0xD8 || 0x10 || appStateKey || per-console
|-
| 0xE8 || 0x10 || selfMsgKey || per-console
|-
| 0xF8 || 0x04 || csumAdjust || per-console
|-
| 0xFC || 0x04 || jtagEnable || common

Virage2

2018-05-03T20:38:32Z

Asper:

OTP is a One Time Programmable 256 (0xFF) Byte memory region located inside the SoC. It seems to be called "virage2" in the SDK code. It can only be read in secure mode, and is mapped to <tt>0xBFCA0000</tt>.

{| class="wikitable"
|-
! Offset
! Size
! Description
! Note
|-
| 0x00 || 0x14 || SK Hash || common
|-
| 0x14 || 0x10 x 4 || ROM Patch || common
|-
| 0x54 || 0x20 || EccPublicKey || per-console
|-
| 0x74 || 0x04 || bbId || per-console
|-
| 0x78 || 0x40 || EccPrivateKey || per-console
|-
| 0xB8 || 0x10 || bootAppKey (COMMON KEY)|| common
|-
| 0xC8 || 0x10 || recryptListKey || per-console
|-
| 0xD8 || 0x10 || appStateKey || per-console
|-
| 0xE8 || 0x10 || selfMsgKey || per-console
|-
| 0xF8 || 0x04 || csumAdjust || per-console
|-
| 0xFC || 0x04 || jtagEnable || common

Power supply

2018-05-03T05:07:33Z

Asper:

{{DISPLAYTITLE:iQue Player Power Supply}}

[[File:Power_supply.jpg|thumb|right|300px|iQue Player Power Supply.]]

The iQue Player is powered by a 5V DC 2A power supply. The included adaptor draws 110mA 220V AC at 50Hz from a Chinese power socket and converts it to the required voltage. Power is supplied to the player through a standard 2.1 x 5.5 x 10mm barrel jack, which connects to the combined power/video cable. The center tip is positive.

An alternative supply may be created with a suitably high-Wattage USB power supply and a standard barrel jack.

[[File:POWER_ADAPTER.jpg|thumb|left|300px|Alternative power supply adapter.]]

File:Power supply.jpg

2018-05-03T05:06:30Z

Asper:

Virage2

2018-05-02T21:05:36Z

Asper:

OTP is a One Time Programmable 256 (0xFF) Bytes memory located inside the SoC and seems to be called "virage2" inside SDK code. It can only be read in secure mode, and is mapped to <tt>0xBFCA0000</tt>.

{| class="wikitable"
|-
! Offset
! Size
! Description
! Note
|-
| 0x00 || 0x14 || SK Hash || common
|-
| 0x14 || 0x10 x 4 || ROM Patch || common
|-
| 0x54 || 0x20 || EccPublicKey || per-console
|-
| 0x74 || 0x04 || bbId || per-console
|-
| 0x78 || 0x40 || EccPrivateKey || per-console
|-
| 0xB8 || 0x10 || bootAppKey - COMMON KEY || common
|-
| 0xC8 || 0x10 || recryptListKey || per-console
|-
| 0xD8 || 0x10 || appStateKey || per-console
|-
| 0xE8 || 0x10 || selfMsgKey || per-console
|-
| 0xF8 || 0x04 || csumAdjust || per-console
|-
| 0xFC || 0x04 || jtagEnable || common

Virage2

2018-05-02T21:03:31Z

Asper:

OTP is a One Time Programmable 256Bytes memory stored somewhere inside a console chip (maybe inside the "big" NEC chip) and seems to be called "virage2" inside SDK code. OTP can be dumped together with bootROM using a patched .rec file able to launch a modified .sta save file; when executed, the code writes a new .sta file containing BOOROM+OTP; dump it from iQue console using ique_diag.exe to save it to your PC (ique_diag.exe -> B -> 3 savegameId.sta); inside the dumped .sta file OTP data can be found from 0x20CC to 0x21CB

{| class="wikitable"
|-
! Offset
! Size
! Description
! Note
|-
| 0x00 || 0x14 || SK Hash || common
|-
| 0x14 || 0x10 x 4 || ROM Patch || common
|-
| 0x54 || 0x20 || EccPublicKey || per-console
|-
| 0x74 || 0x04 || bbId || per-console
|-
| 0x78 || 0x40 || EccPrivateKey || per-console
|-
| 0xB8 || 0x10 || bootAppKey - COMMON KEY || common
|-
| 0xC8 || 0x10 || recryptListKey || per-console
|-
| 0xD8 || 0x10 || appStateKey || per-console
|-
| 0xE8 || 0x10 || selfMsgKey || per-console
|-
| 0xF8 || 0x04 || csumAdjust || per-console
|-
| 0xFC || 0x04 || jtagEnable || common

Virage2

2018-05-02T21:01:34Z

Asper:

OTP is stored somewhere inside a console chip (maybe inside the "big" NEC chip) and seems to be called "virage2" inside SDK code. OTP can be dumped together with bootROM using a patched .rec file able to launch a modified .sta save file; when executed, the code writes a new .sta file containing BOOROM+OTP; dump it from iQue console using ique_diag.exe to save it to your PC (ique_diag.exe -> B -> 3 savegameId.sta); inside the dumped .sta file OTP data can be found from 0x20CC to 0x21CB

{| class="wikitable"
|-
! Offset
! Size
! Description
! Note
|-
| 0x00 || 0x14 || SK Hash || common
|-
| 0x14 || 0x10 x 4 || ROM Patch || common
|-
| 0x54 || 0x20 || EccPublicKey || per-console
|-
| 0x74 || 0x04 || bbId || per-console
|-
| 0x78 || 0x40 || EccPrivateKey || per-console
|-
| 0xB8 || 0x10 || bootAppKey - COMMON KEY || common
|-
| 0xC8 || 0x10 || recryptListKey || per-console
|-
| 0xD8 || 0x10 || appStateKey || per-console
|-
| 0xE8 || 0x10 || selfMsgKey || per-console
|-
| 0xF8 || 0x04 || csumAdjust || per-console
|-
| 0xFC || 0x04 || jtagEnable || common

Virage2

2018-05-02T21:00:50Z

Asper:

OTP is stored somewhere inside a console chip (maybe inside the "big" NEC chip) and seems to be called "virage2" inside SDK code. OTP can be dumped together with bootROM using a patched .rec file able to launch a modified .sta save file; when executed, the code writes a new .sta file containing BOOROM+OTP; dump it from iQue console using ique_diag.exe to save it to your PC (ique_diag.exe -> B -> 3 savegameId.sta); inside the dumped .sta file OTP data can be found from 0x20CC to 0x21CB

{| class="wikitable"
|-
! Offset
! Size
! Description
! Note
|-
| 0x00 || 0x14 || SK Hash || common
|-
| 0x14 || 0x10 || ROM Patch || common
|-
| 0x24 || 0x10 || ROM Patch || common
|-
| 0x34 || 0x10 || ROM Patch || common
|-
| 0x44 || 0x10 || ROM Patch || common
|-
| 0x54 || 0x20 || EccPublicKey || per-console
|-
| 0x74 || 0x04 || bbId || per-console
|-
| 0x78 || 0x40 || EccPrivateKey || per-console
|-
| 0xB8 || 0x10 || bootAppKey - COMMON KEY || common
|-
| 0xC8 || 0x10 || recryptListKey || per-console
|-
| 0xD8 || 0x10 || appStateKey || per-console
|-
| 0xE8 || 0x10 || selfMsgKey || per-console
|-
| 0xF8 || 0x04 || csumAdjust || per-console
|-
| 0xFC || 0x04 || jtagEnable || common

Virage2

2018-05-02T20:57:08Z

Asper:

OTP is an 8Kb ROM is stored somewhere inside a console chip (maybe inside the "big" NEC chip) and seems to be called "virage2" inside SDK code. OTP can be dumped together with bootROM using a patched .rec file able to launch a modified .sta save file.

{| class="wikitable"
|-
! Offset
! Size
! Description
! Note
|-
| 0x00 || 0x14 || SK Hash || common
|-
| 0x14 || 0x10 || ROM Patch || common
|-
| 0x24 || 0x10 || ROM Patch || common
|-
| 0x34 || 0x10 || ROM Patch || common
|-
| 0x44 || 0x10 || ROM Patch || common
|-
| 0x54 || 0x20 || EccPublicKey || per-console
|-
| 0x74 || 0x04 || bbId || per-console
|-
| 0x78 || 0x40 || EccPrivateKey || per-console
|-
| 0xB8 || 0x10 || bootAppKey - COMMON KEY || common
|-
| 0xC8 || 0x10 || recryptListKey || per-console
|-
| 0xD8 || 0x10 || appStateKey || per-console
|-
| 0xE8 || 0x10 || selfMsgKey || per-console
|-
| 0xF8 || 0x04 || csumAdjust || per-console
|-
| 0xFC || 0x04 || jtagEnable || common

Virage2

2018-05-02T20:56:50Z

Asper: Created page with "OTP is stored somewhere inside a console chip (maybe inside the "big" NEC chip) and seems to be called "virage2" inside SDK code. OTP can be dumped together with bootROM using..."

OTP is stored somewhere inside a console chip (maybe inside the "big" NEC chip) and seems to be called "virage2" inside SDK code. OTP can be dumped together with bootROM using a patched .rec file able to launch a modified .sta save file.

{| class="wikitable"
|-
! Offset
! Size
! Description
! Note
|-
| 0x00 || 0x14 || SK Hash || common
|-
| 0x14 || 0x10 || ROM Patch || common
|-
| 0x24 || 0x10 || ROM Patch || common
|-
| 0x34 || 0x10 || ROM Patch || common
|-
| 0x44 || 0x10 || ROM Patch || common
|-
| 0x54 || 0x20 || EccPublicKey || per-console
|-
| 0x74 || 0x04 || bbId || per-console
|-
| 0x78 || 0x40 || EccPrivateKey || per-console
|-
| 0xB8 || 0x10 || bootAppKey - COMMON KEY || common
|-
| 0xC8 || 0x10 || recryptListKey || per-console
|-
| 0xD8 || 0x10 || appStateKey || per-console
|-
| 0xE8 || 0x10 || selfMsgKey || per-console
|-
| 0xF8 || 0x04 || csumAdjust || per-console
|-
| 0xFC || 0x04 || jtagEnable || common

Power supply

2018-04-29T21:14:59Z

Asper:

{{DISPLAYTITLE:iQue Player Power Supply}}

The iQue Player is powered by a 5V DC 2A power supply. The included adaptor draws 110mA 220V AC at 50Hz from a Chinese power socket and converts it to the required voltage. Power is supplied to the player through a standard 2.1 x 5.5 x 10mm barrel jack, which connects to the combined power/video cable. The centre pin is positive.
[[File:20180429_182842.jpg]]

An alternative supply may be created with a suitably high-Wattage USB power supply and a standard barrel jack.

[[File:POWER_ADAPTER.jpg]]

File:POWER ADAPTER.jpg

2018-04-29T21:13:59Z

Asper:

Power supply

2018-04-29T21:11:16Z

Asper:

File:20180429 182842.jpg

2018-04-29T21:10:18Z

Asper:

Controller

2018-04-01T10:57:36Z

Asper:

== Controllers ==
[[File:Controllers.png]]

[[File:Controllers.jpg]]

[[File:ControllersBundles.jpg]]

Controllers have a darker color than the iQue console-controller and they can be bought separately or in bundle with a multiplayer adapter (Family Pack) where you can add up to 3 other players.

== Controller Pinout ==
[[File:Controller_Pinout.jpg]]

They are nothing more (or less) than a N64 original controller.

The iQue output +5V on the controller's connector but it is unused by the controller. So games might still be compatible with rumble pak if nintendo did not remove support in their software. With this +5V output they could have released an iQue controller with build-in rumble support.
Information retrieved [https://assemblergames.com/threads/ique-player.16863/page-5 here].

Controller

2018-04-01T10:22:12Z

Asper:

== Controllers ==
[[File:Controllers.png]]

[[File:Bundles.jpg]]

[[File:ControllersBundles.jpg]]

Controllers have a darker color than the iQue console-controller and they can be bought separately or in bundle with a multiplayer adapter (Family Pack) where you can add up to 3 other players.

== Controller Pinout ==
[[File:Controller_Pinout.jpg]]

They are nothing more (or less) than a N64 original controller.

The iQue output +5V on the controller's connector but it is unused by the controller. So games might still be compatible with rumble pak if nintendo did not remove support in their software. With this +5V output they could have released an iQue controller with build-in rumble support.
Information retrieved [https://assemblergames.com/threads/ique-player.16863/page-5 here].

Controller

2018-04-01T10:20:14Z

Asper:

== Controllers ==
[[File:Controllers.png]]

[[File:ControllersBundles.jpg]]

[[File:Multiplayer.jpg]]

Controllers have a darker color than the iQue console-controller and they can be bought separately or in bundle with a multiplayer adapter (Family Pack) where you can add up to 3 other players.

== Controller Pinout ==
[[File:Controller_Pinout.jpg]]

They are nothing more (or less) than a N64 original controller.

The iQue output +5V on the controller's connector but it is unused by the controller. So games might still be compatible with rumble pak if nintendo did not remove support in their software. With this +5V output they could have released an iQue controller with build-in rumble support.
Information retrieved [https://assemblergames.com/threads/ique-player.16863/page-5 here].

File:ControllersBundles.jpg

2018-04-01T10:19:34Z

Asper:

Controller

2018-04-01T10:17:11Z

Asper:

== Controllers ==
[[File:Controllers.png]]

[[File:ControllersBundles.jpg]]

Controllers have a darker color than the iQue console-controller and they can be bought separately or in bundle with a multiplayer adapter (Family Pack) where you can add up to 3 other players.

== Controller Pinout ==
[[File:Controller_Pinout.jpg]]

They are nothing more (or less) than a N64 original controller.

The iQue output +5V on the controller's connector but it is unused by the controller. So games might still be compatible with rumble pak if nintendo did not remove support in their software. With this +5V output they could have released an iQue controller with build-in rumble support.
Information retrieved [https://assemblergames.com/threads/ique-player.16863/page-5 here].

Controller

2018-04-01T10:16:54Z

Asper:

== Controllers ==
[[File:Controllers.png]]

[[File:ControllersBundles.jpg]]

Controllers have a darker color than the iQue console-controller and they can be bought separately or in bundle with a multiplayer adapter (Family Pack) where you can add up to 3 other players.

== Controller Pinout ==
[[File:Controller_Pinout.jpg]]

They are nothing more (or less) than a N64 original controller.

The iQue output +5V on the controller's connector but it is unused by the controller. So games might still be compatible with rumble pak if nintendo did not remove support in their software. With this +5V output they could have released an iQue controller with build-in rumble support.
Information retreived [https://assemblergames.com/threads/ique-player.16863/page-5 here].

Controller

2018-04-01T10:16:05Z

Asper: Created page with "== Controllers == File:Controllers.png File:ControllersBundles.jpg Controllers have a darker color than the iQue console-controller and they can be bought separately..."

File:Controllers.png

2018-04-01T10:08:33Z

Asper:

File:Controller Pinout.jpg

2018-04-01T10:06:06Z

Asper:

File:Controllers.jpg

2018-04-01T10:03:48Z

Asper:

Video cable

2018-04-01T09:50:58Z

Asper:

== Video Cable Pinout ==
[[File:Pinout.jpg]]

S-video is available on the port. The controller uses the same common N64 controller pinout, so you can plug in a real N64 controller but you need to power it from an external source.
{| class="wikitable"
|-
! Pin N.
! Description
|-
| 1
| Controller # 3 input
|-
| 2
| Y (S-Video)
|-
| 3
| GND (Video)
|-
| 4
| GND (Audio)
|-
| 5
| Audio L
|-
| 6
| GND
|-
| 7
| Batt Data ??
|-
| 8
| Power input +
|-
| 9
| Power input +
|-
| 10
| Power input -
|-
| 11
| Power input -
|-
| 12
| Batt data ??
|-
| 13
| GND (Audio)
|-
| 14
| Audio R
|-
| 15
| Video Composite
|-
| 16
| C (S-Video)
|-
| 17
| Controller # 2 input
|-
| 18
| Controller # 4 input
|}

== S-Video Signal ==
[[File:Cable_multi.jpg]]

The multiplayer box is passing-through the S-video signal, but unfortunately the cable that goes between the iQue and that box does not pass the S-Video signal, so to use the multiplayer box with s-video you would need to modify that cable.

Information retrieved [https://assemblergames.com/threads/ique-player-s-video-cable-mod-d-ique-pinout.32934/ here].

Video cable

2018-04-01T09:45:05Z

Asper:

== Video Cable Pinout ==
[[File:Pinout.png]]

S-video is available on the port. The controller uses the same common N64 controller pinout, so you can plug in a real N64 controller but you need to power it from an external source.
{| class="wikitable"
|-
! Pin N.
! Description
|-
| 1
| Controller # 3 input
|-
| 2
| Y (S-Video)
|-
| 3
| GND (Video)
|-
| 4
| GND (Audio)
|-
| 5
| Audio L
|-
| 6
| GND
|-
| 7
| Batt Data ??
|-
| 8
| Power input +
|-
| 9
| Power input +
|-
| 10
| Power input -
|-
| 11
| Power input -
|-
| 12
| Batt data ??
|-
| 13
| GND (Audio)
|-
| 14
| Audio R
|-
| 15
| Video Composite
|-
| 16
| C (S-Video)
|-
| 17
| Controller # 2 input
|-
| 18
| Controller # 4 input
|}

== S-Video Signal ==
[[File:Cable_multi.png]]

The multiplayer box is passing-through the S-video signal, but unfortunately the cable that goes between the iQue and that box does not pass the S-Video signal, so to use the multiplayer box with s-video you would need to modify that cable.

Information retrieved [https://assemblergames.com/threads/ique-player-s-video-cable-mod-d-ique-pinout.32934/ here].

Video cable

2018-04-01T09:44:22Z

Asper:

== Video Cable Pinout ==
[[File:Pinout.png]]

S-video is available on the port. The controller uses the same common N64 controller, so you can plug a real n64 controller but you need to power it externally.
{| class="wikitable"
|-
! Pin N.
! Description
|-
| 1
| Controller # 3 input
|-
| 2
| Y (S-Video)
|-
| 3
| GND (Video)
|-
| 4
| GND (Audio)
|-
| 5
| Audio L
|-
| 6
| GND
|-
| 7
| Batt Data ??
|-
| 8
| Power input +
|-
| 9
| Power input +
|-
| 10
| Power input -
|-
| 11
| Power input -
|-
| 12
| Batt data ??
|-
| 13
| GND (Audio)
|-
| 14
| Audio R
|-
| 15
| Video Composite
|-
| 16
| C (S-Video)
|-
| 17
| Controller # 2 input
|-
| 18
| Controller # 4 input
|}

== S-Video Signal ==
[[File:Cable_multi.png]]

The multiplayer box is passing-through the S-video signal, but unfortunately the cable that goes between the iQue and that box does not pass the S-Video signal, so to use the multiplayer box with s-video you would need to modify that cable.

Information retrieved [https://assemblergames.com/threads/ique-player-s-video-cable-mod-d-ique-pinout.32934/ here].

Video cable

2018-04-01T09:43:37Z

Asper:

== Video Cable Pinout ==
[[File:Pinout.png]]

S-video is available on the port. What controller uses same hardware as normal n64 controller, so you can plug real n64 controller. But need to power then externally.
{| class="wikitable"
|-
! Pin N.
! Description
|-
| 1
| Controller # 3 input
|-
| 2
| Y (S-Video)
|-
| 3
| GND (Video)
|-
| 4
| GND (Audio)
|-
| 5
| Audio L
|-
| 6
| GND
|-
| 7
| Batt Data ??
|-
| 8
| Power input +
|-
| 9
| Power input +
|-
| 10
| Power input -
|-
| 11
| Power input -
|-
| 12
| Batt data ??
|-
| 13
| GND (Audio)
|-
| 14
| Audio R
|-
| 15
| Video Composite
|-
| 16
| C (S-Video)
|-
| 17
| Controller # 2 input
|-
| 18
| Controller # 4 input
|}

== S-Video Signal ==
[[File:Cable_multi.png]]

The multiplayer box is passing-through the S-video signal, but unfortunately the cable that goes between the iQue and that box does not pass the S-Video signal, so to use the multiplayer box with s-video you would need to modify that cable.

Information retrieved [https://assemblergames.com/threads/ique-player-s-video-cable-mod-d-ique-pinout.32934/ here].

Video cable

2018-04-01T09:41:15Z

Asper:

== Video Cable Pinout ==
[[File:Pinout.png]]

The format of the SKSA is simple: a 64KiB SK, followed by SA1 (ticket + data), optionally followed by SA2 (ticket + data):
{| class="wikitable"
|-
! Pin N.
! Description
|-
| 1
| Controller # 3 input
|-
| 2
| Y (S-Video)
|-
| 3
| GND (Video)
|-
| 4
| GND (Audio)
|-
| 5
| Audio L
|-
| 6
| GND
|-
| 7
| Batt Data ??
|-
| 8
| Power input +
|-
| 9
| Power input +
|-
| 10
| Power input -
|-
| 11
| Power input -
|-
| 12
| Batt data ??
|-
| 13
| GND (Audio)
|-
| 14
| Audio R
|-
| 15
| Video Composite
|-
| 16
| C (S-Video)
|-
| 17
| Controller # 2 input
|-
| 18
| Controller # 4 input
|}

== S-Video Signal ==
[[File:Cable_multi.png]]

The multiplayer box is passing-through the S-video signal, but unfortunately the cable that goes between the iQue and that box does not pass the S-Video signal, so to use the multiplayer box with s-video you would need to modify that cable.

Information retrieved [https://assemblergames.com/threads/ique-player-s-video-cable-mod-d-ique-pinout.32934/ here].

Video cable

2018-04-01T09:40:48Z

Asper:

== Video Cable Pinout ==
[[File:Pinout.png]]
The format of the SKSA is simple: a 64KiB SK, followed by SA1 (ticket + data), optionally followed by SA2 (ticket + data):
{| class="wikitable"
|-
! Pin N.
! Description
|-
| 1
| Controller # 3 input
|-
| 2
| Y (S-Video)
|-
| 3
| GND (Video)
|-
| 4
| GND (Audio)
|-
| 5
| Audio L
|-
| 6
| GND
|-
| 7
| Batt Data ??
|-
| 8
| Power input +
|-
| 9
| Power input +
|-
| 10
| Power input -
|-
| 11
| Power input -
|-
| 12
| Batt data ??
|-
| 13
| GND (Audio)
|-
| 14
| Audio R
|-
| 15
| Video Composite
|-
| 16
| C (S-Video)
|-
| 17
| Controller # 2 input
|-
| 18
| Controller # 4 input
|}

== S-Video Signal ==
[[File:Cable_multi.png]]
The multiplayer box is passing-through the S-video signal, but unfortunately the cable that goes between the iQue and that box does not pass the S-Video signal, so to use the multiplayer box with s-video you would need to modify that cable.

Information retrieved [https://assemblergames.com/threads/ique-player-s-video-cable-mod-d-ique-pinout.32934/ here].

Video cable

2018-04-01T09:39:56Z

Asper: Created page with "== Video Cable Pinout == alt video cable pinout layout The format of the SKSA is simple: a 64KiB SK, followed by SA1 (ticket + data), opti..."

== Video Cable Pinout ==
[[File:Pinout.png|200px|thumb|left|alt video cable pinout layout]]
The format of the SKSA is simple: a 64KiB SK, followed by SA1 (ticket + data), optionally followed by SA2 (ticket + data):
{| class="wikitable"
|-
! Pin N.
! Description
|-
| 1
| Controller # 3 input
|-
| 2
| Y (S-Video)
|-
| 3
| GND (Video)
|-
| 4
| GND (Audio)
|-
| 5
| Audio L
|-
| 6
| GND
|-
| 7
| Batt Data ??
|-
| 8
| Power input +
|-
| 9
| Power input +
|-
| 10
| Power input -
|-
| 11
| Power input -
|-
| 12
| Batt data ??
|-
| 13
| GND (Audio)
|-
| 14
| Audio R
|-
| 15
| Video Composite
|-
| 16
| C (S-Video)
|-
| 17
| Controller # 2 input
|-
| 18
| Controller # 4 input
|}

== S-Video Signal ==
[[File:Cable_multi.png|200px|thumb|left]
The multiplayer box is passing-through the S-video signal, but unfortunately the cable that goes between the iQue and that box does not pass the S-Video signal, so to use the multiplayer box with s-video you would need to modify that cable.

Information retrieved [https://assemblergames.com/threads/ique-player-s-video-cable-mod-d-ique-pinout.32934/ here].

File:Cable multi.jpg

2018-04-01T09:37:57Z

Asper:

File:Pinout.jpg

2018-04-01T09:32:37Z

Asper:

IQue Player

2018-03-25T21:35:52Z

Asper:

{{DISPLAYTITLE:iQue Player}}
[[File:iQue Player.png|thumb|An '''iQue Player'''.]]

The '''iQue Player''' is a game console created by iQue and BroadOn (formerly Routefree, later iGware, now Acer Cloud) in partnership with Nintendo, only released in China in late 2003. iQUe company was co-founded by engineer [https://en.wikipedia.org/wiki/Wei_Yen Dr. Wei Yen], an USA-CHN scientist mainly involved in the development of the N64 GFX chip "Reality Engine"; he is also the founder of ArtX, a company that was commissioned by Nintendo to produce the Game Cube processor named "Flipper".

The reason for this union was dictated by the fact that, since 2000, the Chinese market "suffered" from a [https://en.wikipedia.org/wiki/Video_gaming_in_China#Changes_to_video_game_ban_in_China ban on gaming consoles] because they were considered harmful to the psyche of children (the ban ceased in 2015); Nintendo needed to circumvent the problem and to be able to insert its consoles in the vast market of China ([https://www.thegamesmachine.it/speciali/72045/time-machine-online-nintendo-cina-ique/ here it is a plausible explanation] on how it seems to have done). The opportunity came with iQue products, of which the "i Que Player" represents the progenitor and corresponds to the Chinese version of the Nintendo 64 (there are also iQue GBA, GBA SP, GB Micro, iQue DS, DS Lite, the iQue 3DS)!

This console, whose name in Chinese means "Divine gaming machine", is not a normal N64 but a "compressed" version of it in a single chip: based on the Nintendo 64, the iQue Player adds features like removable [[NAND]] flash memory, PC connectivity (via USB), slightly better performance, and 14 different [[games]] translated into Simplified Chinese.

IQue Player

2018-03-25T21:35:08Z

Asper:

{{DISPLAYTITLE:iQue Player}}
[[File:iQue Player.png|thumb|An '''iQue Player'''.]]

The '''iQue Player''' is a game console created by iQue and BroadOn (formerly Routefree, later iGware, now Acer Cloud) in partnership with Nintendo, released only in China in late 2003. iQUe company was co-founded by engineer [https://en.wikipedia.org/wiki/Wei_Yen Dr. Wei Yen], an USA-CHN scientist mainly involved in the development of the N64 GFX chip "Reality Engine"; he is also the founder of ArtX, a company that was commissioned by Nintendo to produce the Game Cube processor named "Flipper".

The reason for this union was dictated by the fact that, since 2000, the Chinese market "suffered" from a [https://en.wikipedia.org/wiki/Video_gaming_in_China#Changes_to_video_game_ban_in_China ban on gaming consoles] because they were considered harmful to the psyche of children (the ban ceased in 2015); Nintendo needed to circumvent the problem and to be able to insert its consoles in the vast market of China ([https://www.thegamesmachine.it/speciali/72045/time-machine-online-nintendo-cina-ique/ here it is a plausible explanation] on how it seems to have done). The opportunity came with iQue products, of which the "i Que Player" represents the progenitor and corresponds to the Chinese version of the Nintendo 64 (there are also iQue GBA, GBA SP, GB Micro, iQue DS, DS Lite, the iQue 3DS)!

This console, whose name in Chinese means "Divine gaming machine", is not a normal N64 but a "compressed" version of it in a single chip: based on the Nintendo 64, the iQue Player adds features like removable [[NAND]] flash memory, PC connectivity (via USB), slightly better performance, and 14 different [[games]] translated into Simplified Chinese.

IQue Player

2018-03-25T21:33:47Z

Asper:

{{DISPLAYTITLE:iQue Player}}
[[File:iQue Player.png|thumb|An '''iQue Player'''.]]

The '''iQue Player''' is a game console created by iQue and BroadOn (formerly Routefree, later iGware, now Acer Cloud) in partnership with Nintendo, released only in China in late 2003. iQUe company was co-founded by engineer [https://en.wikipedia.org/wiki/Wei_Yen Dr. Wei Yen], an USA-JAP scientist mainly involved in the development of the N64 GFX chip "Reality Engine"; he is also the founder of ArtX, a company that was commissioned by Nintendo to produce the Game Cube processor named "Flipper".

The reason for this union was dictated by the fact that, since 2000, the Chinese market "suffered" from a [https://en.wikipedia.org/wiki/Video_gaming_in_China#Changes_to_video_game_ban_in_China ban on gaming consoles] because they were considered harmful to the psyche of children (the ban ceased in 2015); Nintendo needed to circumvent the problem and to be able to insert its consoles in the vast market of China ([https://www.thegamesmachine.it/speciali/72045/time-machine-online-nintendo-cina-ique/ here it is a plausible explanation] on how it seems to have done). The opportunity came with iQue products, of which the "i Que Player" represents the progenitor and corresponds to the Chinese version of the Nintendo 64 (there are also iQue GBA, GBA SP, GB Micro, iQue DS, DS Lite, the iQue 3DS)!

This console, whose name in Chinese means "Divine gaming machine", is not a normal N64 but a "compressed" version of it in a single chip: based on the Nintendo 64, the iQue Player adds features like removable [[NAND]] flash memory, PC connectivity (via USB), slightly better performance, and 14 different [[games]] translated into Simplified Chinese.

IQue Player

2018-03-25T21:27:36Z

Asper:

{{DISPLAYTITLE:iQue Player}}
[[File:iQue Player.png|thumb|An '''iQue Player'''.]]

The '''iQue Player''' is a game console created by iQue and BroadOn (formerly Routefree, later iGware, now Acer Cloud) in partnership with Nintendo, released only in China in late 2003. iQUe company was co-founded by engineer [https://en.wikipedia.org/wiki/Wei_Yen Dr.Wii Yen], an USA-JAP scientist mainly involved in the development of the N64 GFX chip "Reality Engine"; he is also the founder of ArtX, a company that was commissioned by Nintendo to produce the Game Cube processor named "Flipper".

The reason for this union was dictated by the fact that, since 2000, the Chinese market "suffered" from a [https://en.wikipedia.org/wiki/Video_gaming_in_China#Changes_to_video_game_ban_in_China ban on gaming consoles] because they were considered harmful to the psyche of children (the ban ceased in 2015); Nintendo needed to circumvent the problem and to be able to insert its consoles in the vast market of China ([https://www.thegamesmachine.it/speciali/72045/time-machine-online-nintendo-cina-ique/ here it is a plausible explanation] on how it seems to have done). The opportunity came with iQue products, of which the "i Que Player" represents the progenitor and corresponds to the Chinese version of the Nintendo 64 (there are also iQue GBA, GBA SP, GB Micro, iQue DS, DS Lite, the iQue 3DS)!

This console, whose name in Chinese means "Divine gaming machine", is not a normal N64 but a "compressed" version of it in a single chip: based on the Nintendo 64, the iQue Player adds features like removable [[NAND]] flash memory, PC connectivity (via USB), slightly better performance, and 14 different [[games]] translated into Simplified Chinese.

Games

2018-03-25T08:21:53Z

Asper:

== Released Games (14) ==

{| class="wikitable"
|-
! Title
! Chinese Title
! Literal Translation
! Release Date
! Game CID
! Manual CID
|-
| Wave Race 64
| [[水上摩托]]
| Motorcycling on Water
| November 17, 2003
| [http://cds.idc.ique.com:16963/cds/download?content_id=5101104 51011]
| [http://cds.idc.ique.com:16963/cds/download?content_id=5101904 51019]
|-
| Star Fox 64
| [[星际火狐]]
| Interstellar Fire Fox
| November 17, 2003
| [http://cds.idc.ique.com:16963/cds/download?content_id=4101105 41011]
| [http://cds.idc.ique.com:16963/cds/download?content_id=4101904 41019]
|-
| Dr. Mario 64
| [[马力欧医生]]
| Dr. Mario
| November 17, 2003
| [http://cds.idc.ique.com:16963/cds/download?content_id=6101104 61011]
| [http://cds.idc.ique.com:16963/cds/download?content_id=6101904 61019]
|-
| Super Mario 64
| [[神游马力欧]]
| iQue Mario
| November 17, 2003
| [http://cds.idc.ique.com:16963/cds/download?content_id=1101104 11011]
| [http://cds.idc.ique.com:16963/cds/download?content_id=1101906 11019]
|-
| The Legend of Zelda: Ocarina of Time
| [[塞尔达传说-时光之笛]]
| The Legend of Zelda: Ocarina of Time
| November 17, 2003
| [http://cds.idc.ique.com:16963/cds/download?content_id=2101104 21011]
| [http://cds.idc.ique.com:16963/cds/download?content_id=2101904 21019]
|-
| Mario Kart 64
| [[马力欧卡丁车]]
| Mario Kart
| December 25, 2003
| [http://cds.idc.ique.com:16963/cds/download?content_id=5201105 52011]
| [http://cds.idc.ique.com:16963/cds/download?content_id=5201906 52019]
|-
| F-Zero X
| [[F-Zero X 未来赛车]]
| F-Zero X Future Racing
| February 25, 2004
| [http://cds.idc.ique.com:16963/cds/download?content_id=5202103 52021]
| [http://cds.idc.ique.com:16963/cds/download?content_id=5202904 52029]
|-
| Yoshi's Story
| [[耀西故事]]
| Yoshi Story
| March 25, 2004
| [http://cds.idc.ique.com:16963/cds/download?content_id=1102101 11021]
| [http://cds.idc.ique.com:16963/cds/download?content_id=1102906 11029]
|-
| Paper Mario
| [[纸片马力欧]]
| Paper Mario
| June 8, 2004
| [http://cds.idc.ique.com:16963/cds/download?content_id=2102104 21021]
| [http://cds.idc.ique.com:16963/cds/download?content_id=2102904 21029]
|-
| Sin and Punishment: Successor of the Earth
| [[罪与罚-地球的继承者]]
| Sin and Punishment: Successor of the Earth
| September 25, 2004
| [http://cds.idc.ique.com:16963/cds/download?content_id=4102103 41021]
| [http://cds.idc.ique.com:16963/cds/download?content_id=4102901 41029]
|-
| Excitebike 64
| [[越野摩托]]
| Off-road Motorcycling
| June 15, 2004
| [http://cds.idc.ique.com:16963/cds/download?content_id=5102108 51021]
| [http://cds.idc.ique.com:16963/cds/download?content_id=5102902 51029]
|-
| Super Smash Bros.
| [[任天堂明星大乱斗]]
| Nintendo Stars Great Melee
| November 15, 2005
| [http://cds.idc.ique.com:16963/cds/download?content_id=1201105 12011]
| [http://cds.idc.ique.com:16963/cds/download?content_id=1201901 12019]
|-
| Custom Robo
| [[组合机器人]]
| Combination Robot
| May 1, 2006
| [http://cds.idc.ique.com:16963/cds/download?content_id=2105103 21051]
| N/A
|-
| Animal Crossing
| [[动物森林]]
| Animal Forest
| June 1, 2006
| [http://cds.idc.ique.com:16963/cds/download?content_id=2104108 21041]
| N/A
|}

== Cancelled Games (2) ==
{| class="wikitable"
|-
! Title
! Chinese Title
! Literal Translation
! Planned Release Time
! Game CID
! Manual CID
|-
| The Legend of Zelda: Majora's Mask
| [[塞尔达传说-魔力面具]]
| The Legend of Zelda: The Magical Mask
| 2004/2005
| 21031 (not on CDS)
| N/A
|-
| (Unknown Title)
| (Unknown Title)
| (Unknown Title)
| ????
| [http://cds.idc.ique.com:16963/cds/download?content_id=2106101 21061]
| N/A
|}

Games

2018-03-24T21:01:59Z

Asper:

== Released Games (14) ==

{| class="wikitable"
|-
! Title
! Chinese Title
! Release Date
|-
! Wave Race 64
! 水上摩托
! November 17, 2003
|-
! Star Fox 64
! 星际火狐
! November 17, 2003
|-
! Dr. Mario 64
! 马力欧医生
! November 17, 2003
|-
! Super Mario 64
! 神游马力欧
! November 17, 2003
|-
! The Legend of Zelda: Ocarina of Time
! 塞尔达传说-时光之笛
! November 17, 2003
|-
! Mario Kart 64
! 马力欧卡丁车
! December 25, 2003
|-
! F-Zero X
! F-Zero X 未来赛车
! February 25, 2004
|-
! Yoshi's Story
! 耀西故事
! March 25, 2004
|-
! Paper Mario
! 纸片马力欧
! June 8, 2004
|-
! Sin and Punishment: Successor of the Earth
! 罪与罚-地球的继承者
! September 25, 2004
|-
! Excitebike 64
! 越野摩托
! June 15, 2004
|-
! Super Smash Bros.
! 任天堂明星大乱斗
! November 15, 2005
|-
! Custom Robo
! 组合机器人
! May 1, 2006
|-
! Animal Crossing
! 动物森林
! June 1, 2006
|}

Games

2018-03-24T19:41:09Z

Asper:

== Released Games (14) ==

{| class="wikitable"
|-
! Title
! Chinese Title
|-
! Wave Race 64
! 水上摩托
|-
! Lylat Wars
! 星际火狐
|-
! Super Mario 64
! 神游马力欧
|-
! The Legend of Zelda: Ocarina of Time
! 塞尔达传说-时光之笛
|-
! Mario Kart 64
! 马力欧卡丁车
|-
! F-Zero X
! F-Zero X 未来赛车
|-
! Yoshi's Story
! 耀西故事
|-
! Paper Mario
! 纸片马力欧
|-
! Sin and Punishment: Successor of the Earth
! 罪与罚-地球的继承者
|-
! Excitebike 64
! 越野摩托
|-
! Super Smash Bros.
! 任天堂明星大乱斗
|-
! Animal Crossing
! 动物森林
|-
! Dr. Mario 64
! 马力欧医生
|-
! Custom Robo
! 组合机器人
|}

Games

2018-03-24T19:40:13Z

Asper: Created page with "== Format == {| class="wikitable" |- ! Title ! Chinese Title |- ! Wave Race 64 ! 水上摩托 |- ! Lylat Wars ! 星际火狐 |- ! Super Mario 64 ! 神游马力欧 |- ! The..."

== Format ==

{| class="wikitable"
|-
! Title
! Chinese Title
|-
! Wave Race 64
! 水上摩托
|-
! Lylat Wars
! 星际火狐
|-
! Super Mario 64
! 神游马力欧
|-
! The Legend of Zelda: Ocarina of Time
! 塞尔达传说-时光之笛
|-
! Mario Kart 64
! 马力欧卡丁车
|-
! F-Zero X
! F-Zero X 未来赛车
|-
! Yoshi's Story
! 耀西故事
|-
! Paper Mario
! 纸片马力欧
|-
! Sin and Punishment: Successor of the Earth
! 罪与罚-地球的继承者
|-
! Excitebike 64
! 越野摩托
|-
! Super Smash Bros.
! 任天堂明星大乱斗
|-
! Animal Crossing
! 动物森林
|-
! Dr. Mario 64
! 马力欧医生
|-
! Custom Robo
! 组合机器人
|}

Titles

2018-03-24T18:56:34Z

Asper:

Those are the tiles downlaodable via http://cds.idc.ique.com:16963/cds/download?content_id=xxx where xxx must be replaced with the following IDs:

10000000- old firmware ?
10000001- old firmware ?
10000002- old firmware ?
10000003 - probably last firmware ?
1101104 - Super Mario 64
1101902 - SM64 Manual (old version)
1101906 - SM64 (Manual)
1102101 - Yoshi's Story
1102902 - Yoshi's Story manual (old version)
1102904 - Yoshi's Story manual (old version)
1102906 - Yoshi's Story manual
1201105 - Super Smash Bros.
1201901 - SSB (Manual)
2101104 - Ocarina of Time
2101902 - OOT manual (old version)
2101904 - OOT manual
2102104 - Paper Mario
2102902 - PM manual (old version)
2102904 - PM manual
2104108 - Animal Crossing
2105103 - Custom Robo
4101104 - Star Fox (old version)
4101105 - Star Fox
4101902 - Star Fox manual (old version)
4101904 - Star Fox manual
4102103 - Sin&Punishment
4102901 - Sin&Punishment manual
5101104 - Wave Race
5101902 - WR manual (old version)
5101904 - WR manual
5102108 - Excitebike 64
5102902 - EB64 manual
5201104 - Mario Kart 64(old version)
5201105 - Mario Kart 64
5201902 - MK64 manual (old version)
5201906 - MK64 manual
5202103 - F-Zero
5202902 - F-Zero Manuale (old version)
5202904 - F-Zero Manuale
6101104 - Dr.Mario
6101902 - Dr.Mario Manual (old version)
6101904 - Dr.Mario Manual

Titles

2018-03-24T18:56:15Z

Asper:

Those are the tiles downlaodable via http://cds.idc.ique.com:16963/cds/download?content_id=xxx where xxx must be replaced with the following IDs:

10000000- old firmware ?

10000001- old firmware ?

10000002- old firmware ?
10000003 - probably last firmware ?
1101104 - Super Mario 64
1101902 - SM64 Manual (old version)
1101906 - SM64 (Manual)
1102101 - Yoshi's Story
1102902 - Yoshi's Story manual (old version)
1102904 - Yoshi's Story manual (old version)
1102906 - Yoshi's Story manual
1201105 - Super Smash Bros.
1201901 - SSB (Manual)
2101104 - Ocarina of Time
2101902 - OOT manual (old version)
2101904 - OOT manual
2102104 - Paper Mario
2102902 - PM manual (old version)
2102904 - PM manual
2104108 - Animal Crossing
2105103 - Custom Robo
4101104 - Star Fox (old version)
4101105 - Star Fox
4101902 - Star Fox manual (old version)
4101904 - Star Fox manual
4102103 - Sin&Punishment
4102901 - Sin&Punishment manual
5101104 - Wave Race
5101902 - WR manual (old version)
5101904 - WR manual
5102108 - Excitebike 64
5102902 - EB64 manual
5201104 - Mario Kart 64(old version)
5201105 - Mario Kart 64
5201902 - MK64 manual (old version)
5201906 - MK64 manual
5202103 - F-Zero
5202902 - F-Zero Manuale (old version)
5202904 - F-Zero Manuale
6101104 - Dr.Mario
6101902 - Dr.Mario Manual (old version)
6101904 - Dr.Mario Manual

Titles

2018-03-24T18:55:59Z

Asper: Created page with "Those are the tiles downlaodable via http://cds.idc.ique.com:16963/cds/download?content_id=xxx where xxx must be replaced with the following IDs: 10000000- old firmware ? 100..."