6,263
edits
Changes
Jump to navigation
Jump to search
Line 10:
Line 10: + + + + + + + + + + + + + + + + + + + + + + + + + + + +
no edit summary
The DSi will then send its country code, username, and serial number to the 3DS, 3DS will send its country-code/username/serial# to DSi as well.
The DSi will then send its country code, username, and serial number to the 3DS, 3DS will send its country-code/username/serial# to DSi as well.
The DSi sends a list of owned titles to the 3DS. The 3DS then seems to query the shop server via SOAP to check which titles may be transferred, it then replies to the DSi with a list of titles(of the titles which were sent to it) that can be transferred. When the user selects which title to transfer, DSi sends the banner of that title to the 3DS and many frames later the titleID.
The DSi sends a list of owned titles to the 3DS. The 3DS then seems to query the shop server via SOAP to check which titles may be transferred, it then replies to the DSi with a list of titles(of the titles which were sent to it) that can be transferred. When the user selects which title to transfer, DSi sends the banner of that title to the 3DS and many frames later the titleID.
When DSi sends the title list, after the first 6 bytes of the 802.11 data payload, is the below header. Following the header is the list of titles.
{| class="wikitable" border="1"
|-
! Offset
! Length
! Notes
|-
| 0x0
| 0x4
| Always zero?
|-
| 0x0
| 0x4
| ?
|-
| 0x8
| 0x4
| Total titles?
|-
| 0xc
| 0x1
| Filler
|-
| 0xd
| 0x48
| All 0xFF bytes.
|}
=== Title record from DSi ===
=== Title record from DSi ===