(2006/08/02)
Up until now, the security level had been lowered in order to connect to the temporary download server. However, the actual working server is up now, so the security has been improved.
We added the error code 540XX (the final two digits indicate the type of access point connected to) when disconnecting from an access point.
We fixed a bug that was causing problems in the error code set when using the DWC_UpdateConnection function to detect a disconnection from an access point.
We fixed a bug where the callback did not occur when an error occurred with the DWC_LoginToStorageServerAsync function.
We revised the following documents contained in $NITRODWC_ROOT/docs. For details, see the revision history in the respective documents:
"Nintendo Wi-Fi Connection NITRO-DWC Programming Manual"
"Nintendo Wi-Fi Connection NITRO-DWC Programming Manual -Download Edition-"
Nintendo Wi-Fi Connection NITRO-DWC Programming Manual - General-Purpose Ranking Edition-"
We fixed a bug where user-defined data was unable to be obtained normally.
Version 1.00 --> Version 1.01
None.
(2006/07/03)
We added the function DWC_NASLogin*, which performs the verification process for Nintendo Authentication. Up until now, this process had been performed inside the DWC_LoginAsync function, but when FriendsMatch Library features such as friend management and matchmaking are not in use, this function performs the authentication process instead.
We have added the dwc_naslogin_sample sample demo in accordance with these changes.
NOTE: Since the FriendsMatch Library is not included in NITRO-DWC-DL, the authentication process must be performed with this function.
We added a function to check that a connection to an access point is being maintained normally. Up until now, this process had been performed inside the DWC_ProcessFriendsMatch function, but when FriendsMatch Library features such as friend management and matchmaking are not in use, this function performs the connection check instead.
NOTE: Since the FriendsMatch Library is not included in NITRO-DWC-DL, the connection check must be performed with this function.
Up until now, the game name "gmtest" has been used in the sample demo, but since developers who had been generally using GameSpy used it as a shared name, there was the possibility that it would give a glimpse into the information about games in development, and that data on a back-end server could be maliciously altered. Because of this issue, we have changed the name exclusively for the NITRO-DWC sample demo to "dwctest".
Since the functions GX_SetBGScrOffset and GX_SetBGCharOffset were not being called explicitly when initializing a Wi-Fi connection configuration, there was a bug where the screen display was becoming corrupted when changes were made to offsets with these functions. This bug has been fixed.
None.
(2006/06/22)
The DWCBuddyFriendCallback function, which is called when a friend relationship is established, will now be called when the network communication used to establish the friend relationship is successful. This network communication used to establish the friend relationship may be performed twice, depending on the timing. Should that happen, the callback will have occurred each time.
, We have made changes so that the the callback is not called when a friend relationship is already established.
We have revised the process for making an automatic connection to the Internet for access point authentication processes in order to improve connectivity to access points that accept only open system authentications.
We made revisions to the following documents which are contained in $NITRODWC_ROOT/docs: For details, see the Revision History for each document.
Nintendo Wi-Fi Connection NITRO-DWC Programming Manual
Nintendo Wi-Fi Connection NITRO-DWC Programming Manual - General-Purpose Ranking Version -
We added user-defined data to the CRC, and made changes to check for falsification.
We made changes for when user-defined data is not used in the general purpose ranking library. Users can now select NULL as the data argument and 0 for the size in the DWC_RnkPutScoreAsync function.
We fixed the issue where the program will stop due to an insufficient receive buffer when the download server returns an error.
Along with this fix was an addition of error code 31030 for an insufficient receive buffer error. Also, the minimum buffer size passed to DWC_NdGetFileAsync was set to 128 bytes. A buffer of at least 128 bytes will need to be specified, even if the downloaded data is smaller than this size.
None.
(2006/06/08)
We made changes to the internal operations of the process for obtaining service locator information that the download feature uses.
None.
(2006/06/06)
Added general-purpose ranking constants.
For details, see the documentation in $NITRODWC_ROOT/docs.
Added the library for downloading content from the Download server provided by Nintendo.
For details, see the documentation in $NITRODWC_ROOT/docs.
Made the following additions and changes to the error information that can be obtained with DWC_GetLastError and DWC_GetLastErrorEx:
When FREESPOT was set for the SSID of connection targets 1 to 3 in the Settings Utility and a connection test was performed, the error that occurred had the error code is 5XX05, whereas it should have been some error code between 5XX00 and 5XX02. That problem has been fixed.
When the end user saved owner information to the DS and entered a nickname with 10 characters, an error code 20109 would be generated when connecting to Wi-Fi Connection. That problem has been corrected.
Note: This problem does not arise in NITRO-DWC 1.0 and later versions.
Note: This is a problem that gets corrected by the NITRO-DWC 1.1 PLUS patch.
When MatchMake was started after disconnecting during a game, sometimes that MatchMake process would not end. That problem has been fixed.
This problem occurred when the Reception state of Reliable transmission was to reset after peer-to-peer communications was disconnected.
Note: This is a problem that gets corrected by the NITRO-DWC 1.1 PLUS patch.
The Reception timeout callback specified by the DWC_SetUserRecvTimeoutCallback function was not being called. This problem was corrected.
Data sent using DWC_SendReliable* would accumulate in the Send buffer because there was no acknowledgment confirming reception by the receiver side. While the Send buffer remained full in this way, there would be no call to the Reception timeout callback.
Note: This is a problem that gets corrected by the NITRO-DWC 1.1 PLUS2 patch.
When connecting at a hotspot, the required information would not be sent to the Authentication server. This problem has been fixed.
This problem made it impossible to connect at some hotspots.
Note: This problem does not arise in NITRO-DWC 1.0 and later versions.
Note: This is a problem that gets corrected by the NITRO-DWC 1.1 PLUS2 patch.
The screen name in the game that gets sent to the Authentication server using the DWC_LoginAsync function has been extended to 25 characters. Before the maximum length was 10 characters.
In accordance, made changes and additions to the explanation for the ingamesn argument of the DWC_LoginAsync function in the Reference Manual.
Note: This change is made by the NITRO-DWC 1.1 PLUS2.
The following three functions:
Revised the 'Nintendo Wi-Fi Connection NITRO-DWC Programming Manual' included in $NITRODWC_ROOT/docs.
Also made additions to the Programming Manual for the general-purpose ranking feature and the download feature.
Additions and revisions were made to the items listed below. For details, see the Revision History for each item.
Note: The Revision History does not show small revisions to terminology, etc.
Deleted the directory '$NITRODWC_ROOT/add-ins' from the package.
None.
(2006/03/10)
Added DWC_StopScMatchingAsync as a function to cancel server-client matchmaking.
Added DWC_CancelGHTTPRequest as a function to cancel HTTP communication.
Added DWC_GetApInfo as a function that gets data specific to the connected access point after completing an Internet connection. This function obtains the connection candidate (targets 1 through 3, the Nintendo Wi-Fi USB Connector, etc.) to which the access point is connected and the access point's SSID and BSSID. In addition, location information can also be obtained for Wi-Fi Station connections.
Added the function DWC_GetDateTime for getting the current date and time in GMT based on the time information retreived from the authentication server during authentication processing. This function can also be used to get the GMT date and time after authentication. Be aware that there may be discrepancies in minute/second units.
The DWC_SetConnectApType function was added to explicitly set the target connection candidate (targets 1 through 3, the Nintendo Wi-Fi Station, etc.) before connecting to the Internet. The DWC_ConnectInetAsync function, which then runs, will only connect to the specifed candidate. Use this function for debugging. This specification will be ignored in the FINALROM version.
If this function is used instead of DWC_ConnectInetAsync when connecting to the Internet, you can explicitly specify the SSIP and WEP key for the access point. Use this function for debugging.
This simple demo shows the process for connecting to the Internet. It also includes a demo for the new functions DWC_SetConnectApType and DWC_DebugConnectInetAsync.
If an attempt to set a value larger than that defined in DWC_TRANSPORT_SEND_MAX was made, the value was reset to DWC_TRANSPORT_SEND_MAX and TRUE was returned; this was changed to use assert processing.
Several revisions were made to the displayed message when the test fails during Wi-Fi connection settings.
The Wi-Fi User Data Migration Device Program included in the Wi-Fi connection settings was updated with a NITRO-SDK 3.0 build version.
Fixed an issue where the sound effect would loop while the B button was pressed when cancelling the AOSS settings in the Wi-Fi connection settings.
Fixed an issue where the connection test failure would stop for the Nintendo Wi-Fi USB Connector in the Wi-Fi Connection Settings.
* The connection test used in the Wi-Fi connection settings is the same as the Internet auto-connect process used in games.
Fixed an issue where a very long URL for hotspot authentication would result in a connection stop, while connecting to a hotspot for an Internet connection.
Fixed an issue where a freeze would occur when the DWC_GetInetStatus function was called between the DWC_InitInet and DWC_ConnectInetAsync function calls.
Fixed an issue where a freeze would occur if DWC_ProcessInet was called when the auto-connect control object for an Internet connection was still uninitialized (DWC_InitInet had not been called).
Fixed an issue where a freeze would occur when the DWC_CleanupInet function was called between the DWC_InitInet and DWC_ConnectInetAsync function calls.
Revised the random number generation method used when creating user data. Because the tick value was used as the random seed, if the OS_InitTick function is called with the same timing as the DWC_CreateUserData function, the same login ID can be created. To fix this, the base value for the random seed was changed to use the OS_GetLowEntropyData function.
Unused files and unnecessary notes were deleted.
The content of the User Data Management and Friend Connection Overview documentation was moved to the Programming Guidelines and NITRO-DWC Programming Manual. The original document was removed.
Supplemental descriptions were added to the NITRO-DWC Programming Manual and Function Reference.
None.
(2006/01/30)
DWC_SetFriendStatusCallback was added to configure the callback functions that are called when a friend's communication state changes.
The above callback functions are usually set as the arguments of the friend list synchronous process function DWC_UpdateServersAsync. But, even when no friend list synchronous process is needed and there is a need to know the friend's communication state in real-time, use this function to configure the callback functions.
There was a bug where TRUE was returned when the DWC_IsSendableReliable function was called but FALSE was returned when the DWC_SendReliable* function was called during the generation of an error.
This bug has been fixed so that the DWC_IsSendableReliable function will return FALSE in this kind of situation.
The maximum number of people that can connect with matchmaking in the DWC Library is 32, so an ASSERT was added that checks whether the arguments of the DWC_ConnectToAnybodyAsync, DWC_ConnectToFriendsAsync, and DWC_SetupGameServer functions exceed this number.
The maximum number of friends that the DWC Library can handle is 64, so an ASSERT was added that checks whether the friend list length arguments of the DWC_InitFriendsMatch and DWC_ConnectToFriendsAsync functions exceed this number.
No DWC error was set when a memory allocation error occurred inside the DWC_SetSendDelay, DWC_SetRecvDelay, DWC_SetSendDrop, and DWC_SetRecvDrop functions.
This is revised so the DWC_ECODE_TYPE_ALLOC FATAL ERROR is properly set.
Added return values for failures to the GHTTP library functions below:
The function DWC_Base64Encode (used to encode Base 64) and the function DWC_Base64Decode (used to decode Base 64) were added.
Previously, when status data was configured with the DWC_SetOwnStatusData function, the character string for the statusString argument of the friend state change notification callback DWCFriendStatusCallback could not be used. However, if the DWC_Base64Decode function is used, the statusString character string (a Base 64 character string) will be decoded and can be referenced.
During matchmaking, a temporary parent-child relationship is formed between connected DS devices.
There was a bug where, if the network fails due to a reason such as the power being cut off on the parent DS, any connected child DS devices would freeze up (but matchmaking could be cancelled).
This bug has been fixed so, that should this sort of situation occur and a child DS cannot communicate with its parent for a fixed amount of time, it will re-attempt matchmaking.
The DWC_CheckFriendKey function was being used to check the validity of friend registration keys on the CRC. However, there was a bug that was generating parameter errors during the friend list synchronous process. This occurred even though this function returned TRUE when the GS profile ID included in the friend registration key was negative and a correct friend registration key was input into the CRC.
This has been fixed so that a FALSE will return for friend registration keys whose GS profile ID is negative.
The DWC_LoadOwnDataAsync function, which loaded your data from a data storage server, was unable to load anything except Private data.
Therefore, the following functions have been added: the DWC_LoadOwnPublicDataAsync function, which loads Public data, and the DWC_LoadOwnPrivateDataAsync function, which loads Private data.
There was a bug where, even though a FALSE was specified in the distantFriend argument of the DWC_ConnectToFriendsAsync function, a connection would be made with friends outside of what was specified in the friendIdxList argument.
This bug was fixed so that if a FALSE is specified for distantFriend, there will only be connections made with those friends specified in friendIdxList (or all friends if friendIdxList=NULL).
There was a bug where, after the networking state became unstable and a DWC error was generated, the internal process would continue and fatal error code 71002 would be generated.
This was fixed so that the fatal error does not occur.
Changes were made so that the sample source comments and the terminology used in the reference are consistent.
Specifically, "matching", which was forbidden from being used in the glossary, was changed to "matchmaking".
The following revisions were made to the $NITRODWC_ROOT/build/demos/dwc_frienddata_sample and the $NITRODWC_ROOT/build/demos/dwc_friend_match_sample sample demos.
The following revision was made to the $NITRODWC_ROOT/build/demos/dwc_sample sample demo:
None.
Nintendo Technical Support Center
NTR-06-0404-001-C2
CONFIDENTIAL