diff --git a/archive/Action_Replay/Action_Replay_DS_and_Media_Edition/CodeManager/1.00_HW0/Setup.exe b/archive/Action_Replay/Action_Replay_DS_and_Media_Edition/CodeManager/1.00_HW0/Setup.exe new file mode 100644 index 0000000..6cfe0cf Binary files /dev/null and b/archive/Action_Replay/Action_Replay_DS_and_Media_Edition/CodeManager/1.00_HW0/Setup.exe differ diff --git a/archive/Action_Replay/Action_Replay_DS_and_Media_Edition/CodeManager/1.00_HW0/WindowsInstaller-KB893803-v2-x86.exe b/archive/Action_Replay/Action_Replay_DS_and_Media_Edition/CodeManager/1.00_HW0/WindowsInstaller-KB893803-v2-x86.exe new file mode 100644 index 0000000..a7e88b5 Binary files /dev/null and b/archive/Action_Replay/Action_Replay_DS_and_Media_Edition/CodeManager/1.00_HW0/WindowsInstaller-KB893803-v2-x86.exe differ diff --git a/archive/Action_Replay/Action_Replay_DS_and_Media_Edition/CodeManager/1.00_HW0/autorun.inf b/archive/Action_Replay/Action_Replay_DS_and_Media_Edition/CodeManager/1.00_HW0/autorun.inf new file mode 100644 index 0000000..39eabe6 --- /dev/null +++ b/archive/Action_Replay/Action_Replay_DS_and_Media_Edition/CodeManager/1.00_HW0/autorun.inf @@ -0,0 +1,3 @@ +[autorun] +open=setup.exe +icon=setup.exe diff --git a/archive/Action_Replay/Action_Replay_DS_and_Media_Edition/CodeManager/1.00_HW0/msxml.msi b/archive/Action_Replay/Action_Replay_DS_and_Media_Edition/CodeManager/1.00_HW0/msxml.msi new file mode 100644 index 0000000..a352182 Binary files /dev/null and b/archive/Action_Replay/Action_Replay_DS_and_Media_Edition/CodeManager/1.00_HW0/msxml.msi differ diff --git a/archive/Action_Replay/Action_Replay_DS_and_Media_Edition/CodeManager/1.00_HW0/ndalink.inf b/archive/Action_Replay/Action_Replay_DS_and_Media_Edition/CodeManager/1.00_HW0/ndalink.inf new file mode 100644 index 0000000..f34b4e1 --- /dev/null +++ b/archive/Action_Replay/Action_Replay_DS_and_Media_Edition/CodeManager/1.00_HW0/ndalink.inf @@ -0,0 +1,87 @@ +[Version] +Signature="$CHICAGO$" +Provider=%S_Provider% +DriverVer=05/08/2000,1.42 +Class=USBIOControlledDevices +ClassGUID={96e73b6e-7a5a-11d4-9f24-0080c82727f4} +[ClassInstall] +AddReg=_AddReg_ClassInstall +[ClassInstall32] +AddReg=_AddReg_ClassInstall +[_AddReg_ClassInstall] +HKR,,,,"%S_DeviceClassDisplayName%" +HKR,,Icon,,"-20" +[Manufacturer] +%S_Mfg%=_Devices +[_Devices] +%S_DeviceDesc1%=_Install1, USB\VID_05FD&PID_EEAE +[_Install1] +CopyFiles=_CopyFiles_sys +AddReg=_AddReg_SW1, _AddReg_98, _Parameters1_98 +[_Install1.HW] +AddReg=_AddReg_HW1 +[_Install1.NTx86] +CopyFiles=_CopyFiles_sys +AddReg=_AddReg_SW1, _Parameters1_NT +[_Install1.NTx86.Services] +AddService = %S_DriverName%, 0x00000002, _NT_AddService, _NT_EventLog +[_Install1.NTx86.HW] +AddReg=_AddReg_HW1 +[_NT_AddService] +DisplayName = %S_ServiceDisplayName% +ServiceType = 1 ; SERVICE_KERNEL_DRIVER +StartType = 3 ; demand +ErrorControl = 1 ; SERVICE_ERROR_NORMAL +ServiceBinary = %10%\System32\Drivers\%S_DriverName%.sys +[_NT_EventLog] +AddReg=_NT_EventLog_AddReg +[_NT_EventLog_AddReg] +HKR,,EventMessageFile,0x00020000,"%%SystemRoot%%\System32\IoLogMsg.dll;%%SystemRoot%%\System32\drivers\%S_DriverName%.sys" +HKR,,TypesSupported, 0x00010001,7 +[_AddReg_98] +HKR,,NTMPDriver,,%S_DriverName%.sys +HKR,,DevLoader,,*ntkern +[_AddReg_SW1] +HKLM,"%S_ConfigPath%",,, +HKLM,"%S_ConfigPath%"\"%S_DeviceConfigPath1%",,, +[_AddReg_HW1] +HKR,,USBIO_ConfigurationPath,,\Registry\Machine\%S_ConfigPath%\%S_DeviceConfigPath1% +HKR,,USBIO_UserInterfaceGuid,,"{FA668F1F-02CA-49a1-A84D-BDBFDCC31A8D}" +[_Parameters1_98] +HKLM,"%S_ConfigPath%"\"%S_DeviceConfigPath1%",PowerStateOnOpen,0x00010001, 0 +HKLM,"%S_ConfigPath%"\"%S_DeviceConfigPath1%",PowerStateOnClose,0x00010001, 0 +HKLM,"%S_ConfigPath%"\"%S_DeviceConfigPath1%",EnableRemoteWakeup,0x00010001, 1 +HKLM,"%S_ConfigPath%"\"%S_DeviceConfigPath1%",MinPowerStateUsed,0x00010001, 3 +HKLM,"%S_ConfigPath%"\"%S_DeviceConfigPath1%",MinPowerStateUnused,0x00010001, 3 +HKLM,"%S_ConfigPath%"\"%S_DeviceConfigPath1%",AbortPipesOnPowerDown,0x00010001, 1 +[_Parameters1_NT] +HKLM,"%S_ConfigPath%"\"%S_DeviceConfigPath1%",PowerStateOnOpen,0x00010001, 0 +HKLM,"%S_ConfigPath%"\"%S_DeviceConfigPath1%",PowerStateOnClose,0x00010001, 0 +HKLM,"%S_ConfigPath%"\"%S_DeviceConfigPath1%",EnableRemoteWakeup,0x00010001, 1 +HKLM,"%S_ConfigPath%"\"%S_DeviceConfigPath1%",MinPowerStateUsed,0x00010001, 3 +HKLM,"%S_ConfigPath%"\"%S_DeviceConfigPath1%",MinPowerStateUnused,0x00010001, 3 +HKLM,"%S_ConfigPath%"\"%S_DeviceConfigPath1%",AbortPipesOnPowerDown,0x00010001, 1 +HKLM,"%S_ConfigPath%"\"%S_DeviceConfigPath1%",SuppressPnPRemoveDlg,0x00010001, 1 +[_CopyFiles_sys] +usbio.sys +[ControlFlags] +[DestinationDirs] +DefaultDestDir = 11 ; SYSTEM directory +_CopyFiles_sys = 10,System32\Drivers +[SourceDisksNames] +1=%S_DiskName%,, +[SourceDisksFiles] +%S_DriverName%.sys=1 +[Strings] +S_Provider="Datel" +S_Mfg="Datel" +S_DeviceClassDisplayName="USBIO controlled devices" +S_DeviceDesc1="NDS Link" +S_DiskName="Action Replay DS Driver Disk" +S_DriverName="usbio" +S_ServiceDisplayName="USBIO Driver (usbio.sys)" +S_ConfigPath="SYSTEM\CurrentControlSet\Services\USBIO" +S_DeviceConfigPath1="Parameters" +S_DeviceBaseName1="USBIO_Device" + + diff --git a/archive/Action_Replay/Action_Replay_DS_and_Media_Edition/CodeManager/1.00_HW0/readme.txt b/archive/Action_Replay/Action_Replay_DS_and_Media_Edition/CodeManager/1.00_HW0/readme.txt new file mode 100644 index 0000000..3c23e02 --- /dev/null +++ b/archive/Action_Replay/Action_Replay_DS_and_Media_Edition/CodeManager/1.00_HW0/readme.txt @@ -0,0 +1,44 @@ +Action Replay Code Manager - Readme.txt +--------------------------------------- + +Introduction +------------ + +Action Replay DS is a powerful cheat code system for Nintendo DS. +This software, Action Replay Code Manager, allows you to connect +your PC to your Action Replay DS catridge via USB to add new +codes which can be downloaded from various Internet sources using +this software. + + +Minimum System Requirements +--------------------------- + +Computer / Processor 1GHz+ processor recommended +Communication Internet connection + USB Port (USB 2.0 highly recommended) +Operating System Windows® XP Home or XP Pro. +Memory 256Mb RAM +Install size: 10MB of free hard-disk space for program + installation plus additional hard drive + space for storing codes. +Display 800X600 SVGA or higher, True Colour +Drive CD-ROM drive (for installation) + + + +Updating the Software +--------------------- + +When you first install Action Replay Code Manager it is highly +recommended that you ensure it is up-to-date by clicking the +'Update Software' button on the main menu. This will download +any software updates for the PC application and for the Action +Replay DS firmware. + + +Version History +--------------- + +1.00 First commercial release of Action Replay Code Manager + No known issues. \ No newline at end of file diff --git a/archive/Action_Replay/Action_Replay_DS_and_Media_Edition/CodeManager/1.00_HW0/usbio.sys b/archive/Action_Replay/Action_Replay_DS_and_Media_Edition/CodeManager/1.00_HW0/usbio.sys new file mode 100644 index 0000000..ff8554b Binary files /dev/null and b/archive/Action_Replay/Action_Replay_DS_and_Media_Edition/CodeManager/1.00_HW0/usbio.sys differ diff --git a/archive/Action_Replay/Action_Replay_DS_and_Media_Edition/CodeManager/1.25_HW1_ME/ActionReplayDS.inf b/archive/Action_Replay/Action_Replay_DS_and_Media_Edition/CodeManager/1.25_HW1_ME/ActionReplayDS.inf new file mode 100644 index 0000000..a5fa416 --- /dev/null +++ b/archive/Action_Replay/Action_Replay_DS_and_Media_Edition/CodeManager/1.25_HW1_ME/ActionReplayDS.inf @@ -0,0 +1,263 @@ +; +; *** This file was generated by USBIO Installation Wizard. *** +; +; +; USBIO Setup Information file V2.40 +; Copyright (c) 1998-2007 by Thesycon GmbH +; +; This file supports: +; Windows 2000 +; Windows 2000 Server +; Windows XP +; Windows Server 2003 +; +; To create a customized version of this file +; modify sections marked with ### modify here ### +; For details, refer to the USBIO Reference Manual. +; +; Note: +; Some section names (enclosed in []) are system-defined and should not be changed. +; Private section names start with an '_'. Those can be changed. +; +; Refer to the Windows DDK documentation for more information on INF files. +; + +;****************************************************************************** +; Version section +;------------------------------------------------------------------------------ +[Version] +Signature="$Windows NT$" +Provider=%S_Provider% +DriverVer=02/07/2007,2.40.0.0 + +; This specifies the .cat file provided by WHQL if the driver is certified. +CatalogFile=ActionReplayDS.cat + +; +; ### modify here ### +; Select an appropriate class for the device. +; There are several options: +; - Use the class shown below. It is defined by USBIO and is appropriate for testing purposes. +; - Define your own class by generating a private GUID and a class description. +; - Use a system-defined class. This is required for a device that belongs to a device class +; that is supported by system-provided drivers, HID, USB Audio for instance. +; For example, to replace the default USB mouse driver by USBIO you have to specify the HID +; class here: Class=HIDClass ClassGuid={745a17a0-74d3-11d0-b6fe-00a0c90f57da} +; +; we use a private device class that is defined by USBIO: +Class=USBIOControlledDevices +ClassGUID={96e73b6e-7a5a-11d4-9f24-0080c82727f4} + + +;****************************************************************************** +; Class Install section (optional) +;------------------------------------------------------------------------------ +; +; ### modify here ### +; The following sections are required if a private device class is used +; (see also the comments above). +; These sections should be removed completely if a system-defined class is used. +; +[ClassInstall32] +AddReg=_AddReg_ClassInstall + +[_AddReg_ClassInstall] +HKR,,,,"%S_DeviceClassDisplayName%" +HKR,,Icon,,"-20" + + +;****************************************************************************** +; Options +;------------------------------------------------------------------------------ +[ControlFlags] +; Advanced options can be specified here. +; For details, refer to the Windows DDK documentation. + + +;****************************************************************************** +; Manufacturer section +;------------------------------------------------------------------------------ +[Manufacturer] +%S_Mfg%=_Models + + +;****************************************************************************** +; Models section +;------------------------------------------------------------------------------ +; x86-based systems +[_Models] +; This section specifies your device's hardware ID. + +; *** The following line was generated by USBIO Installation Wizard. *** +%S_DeviceDesc%=_Install, USB\Vid_05fd&Pid_eeae&Rev_0301 + + + +;****************************************************************************** +; Install sections x86-based systems +;------------------------------------------------------------------------------ +[_Install.ntx86] +CopyFiles=_CopyFiles_sys + +[_Install.ntx86.Services] +AddService = %S_DriverName%, 0x00000002, _AddService, _EventLog + +[_Install.ntx86.HW] +AddReg=_AddReg_HW + +[_AddService] +ServiceType = 1 ; SERVICE_KERNEL_DRIVER +StartType = 3 ; SERVICE_DEMAND_START +ErrorControl = 1 ; SERVICE_ERROR_NORMAL +ServiceBinary = %10%\System32\Drivers\%S_DriverName%.sys + +[_EventLog] +AddReg=_EventLog_AddReg + +[_EventLog_AddReg] +HKR,,EventMessageFile,%REG_EXPAND_SZ%,"%%SystemRoot%%\System32\IoLogMsg.dll;%%SystemRoot%%\System32\drivers\%S_DriverName%.sys" +HKR,,TypesSupported, %REG_DWORD%,7 + + +;****************************************************************************** +; Registry sections +;------------------------------------------------------------------------------ +[_AddReg_HW] +; The following string is used by the Cleanup Wizard to unambiguously identify +; USBIO devices and INF files. The entry can be removed completely from a final +; product's INF where the Cleanup Wizard is not needed. +; On the other hand, it does not harm anything if the entry is kept in place. +HKR,,CleanupWizard_DeviceIdentString,%REG_SZ%,"{DAB6A146-D93E-48ab-B3E5-374AB8FFF277}" + +; +; ### modify here ### +; Enable the next line to create an additional private user interface for your device. +; This is strongly recommended if you ship the driver together with a product. +; DO NOT USE an existing GUID. Generate a new one instead ! +; Use guidgen.exe to generate a new GUID, copy-paste it into the following line. +;HKR,,DriverUserInterfaceGuid,%REG_SZ%,"{????????-????-????-????-????????????}" + +; Uncomment this line to disable the default software interface of the driver +; This is recommended if you ship the driver together with a product. +;HKR,, DisableDefaultInterface, %REG_DWORD%, 1 + +; ### modify here ### +; Set the default behaviour of the driver for Windows 2000 and Windows XP +; For a description of the parameters, refer to the USBIO Reference Manual. +HKR,,PowerStateOnOpen, %REG_DWORD%, 0 +HKR,,PowerStateOnClose, %REG_DWORD%, 0 +HKR,,MinPowerStateUsed, %REG_DWORD%, 3 +HKR,,MinPowerStateUnused, %REG_DWORD%, 3 +HKR,,EnableRemoteWakeup, %REG_DWORD%, 0 +HKR,,AbortPipesOnPowerDown,%REG_DWORD%, 1 +HKR,,UnconfigureOnClose, %REG_DWORD%, 1 +HKR,,ResetDeviceOnClose, %REG_DWORD%, 0 +HKR,,MaxIsoPackets, %REG_DWORD%, 512 +HKR,,ShortTransferOk, %REG_DWORD%, 1 +HKR,,RequestTimeout, %REG_DWORD%, 1000 +HKR,,SuppressPnPRemoveDlg, %REG_DWORD%, 1 + +; Uncomment the following lines to enable automatic configuration +; of the device when the USBIO driver starts. +;HKR,,ConfigIndex, %REG_DWORD%, 0 +;HKR,,Interface, %REG_DWORD%, 0 +;HKR,,AlternateSetting, %REG_DWORD%, 0 + +; Uncomment the following lines to enable FX firmware download. +; The firmware file must be located in "%SystemRoot%\System32\Drivers". +; You cannot specify a path for the file. +;HKR,,FxFwFile, %REG_SZ%, "YourFirmwareFile.ihx" +;HKR,,FxBootloaderCheck, %REG_DWORD%, 1 +;HKR,,FxExtRamBase, %REG_DWORD%, 0x4000 + +; NOTE: You can copy the firmware file to "%SystemRoot%\System32\Drivers" during driver installation. +; If you want to do this then you have to add the firmware file to [_CopyFiles_sys] and +; [SourceDisksFiles] sections. See below. + + +;****************************************************************************** +; Copy Files section +;------------------------------------------------------------------------------ +[_CopyFiles_sys] +; ### modify here ### +; Specify the correct file name of the driver binary. +; *** The following line was generated by USBIO Installation Wizard. *** +ActionReplayDS.sys +; If you want to copy a firmware file, activate the following line. +;YourFirmwareFile.ihx + + +;****************************************************************************** +; Destination Directories +;------------------------------------------------------------------------------ +[DestinationDirs] +DefaultDestDir = 12 ; %SystemRoot%\system32\drivers +_CopyFiles_sys = 12 + + +;****************************************************************************** +; Disk Layout +;------------------------------------------------------------------------------ +[SourceDisksNames.x86] +1=%S_DiskName%,, + +[SourceDisksFiles.x86] +; ### modify here ### +; Specify the correct file name of the driver binary. +; *** The following line was generated by USBIO Installation Wizard. *** +ActionReplayDS.sys=1 +; If you want to copy a firmware file, activate the following line. +;YourFirmwareFile.ihx=1 + + + +;****************************************************************************** +; Text Strings +;------------------------------------------------------------------------------ +[Strings] +; +; Non-Localizable Strings, DO NOT MODIFY! +; +REG_SZ = 0x00000000 +REG_MULTI_SZ = 0x00010000 +REG_EXPAND_SZ = 0x00020000 +REG_BINARY = 0x00000001 +REG_DWORD = 0x00010001 + + +; +; Localizable Strings, modify as required +; + +; ### modify here ### +; Edit the strings in this section according to your needs. +; Some of the strings are shown at the user interface. + +; provider name +S_Provider="Datel Design & Development" +; manufacturer name +S_Mfg="Datel Design & Development" + +; device class display name, shown in Device Manager +S_DeviceClassDisplayName="USBIO controlled devices" + + +; device description +; *** The following line was generated by USBIO Installation Wizard. *** +S_DeviceDesc="Action Replay DS (NDS Link)" + +; device description +S_DeviceDesc1="Action Replay DS (NDS Link)" + +; disk name +S_DiskName="Action Replay DS (NDS Link) Driver Disk" + + +; File name of driver executable. +; If the name is modified, the [_CopyFiles_sys] and [SourceDisksFiles] +; sections must also be modified ! +; *** The following line was generated by USBIO Installation Wizard. *** +S_DriverName="ActionReplayDS" + + +; *** EOF *** diff --git a/archive/Action_Replay/Action_Replay_DS_and_Media_Edition/CodeManager/1.25_HW1_ME/ActionReplayDS.sys b/archive/Action_Replay/Action_Replay_DS_and_Media_Edition/CodeManager/1.25_HW1_ME/ActionReplayDS.sys new file mode 100644 index 0000000..121994a Binary files /dev/null and b/archive/Action_Replay/Action_Replay_DS_and_Media_Edition/CodeManager/1.25_HW1_ME/ActionReplayDS.sys differ diff --git a/archive/Action_Replay/Action_Replay_DS_and_Media_Edition/CodeManager/1.25_HW1_ME/ActionReplayDS_x64.inf b/archive/Action_Replay/Action_Replay_DS_and_Media_Edition/CodeManager/1.25_HW1_ME/ActionReplayDS_x64.inf new file mode 100644 index 0000000..9a721ef --- /dev/null +++ b/archive/Action_Replay/Action_Replay_DS_and_Media_Edition/CodeManager/1.25_HW1_ME/ActionReplayDS_x64.inf @@ -0,0 +1,261 @@ +; +; *** This file was generated by USBIO Installation Wizard. *** +; +; +; USBIO Setup Information file V2.40 +; Copyright (c) 1998-2007 by Thesycon GmbH +; +; This file supports: +; Windows XP x64 Edition +; Windows Server 2003 x64 Edition +; +; To create a customized version of this file +; modify sections marked with ### modify here ### +; For details, refer to the USBIO Reference Manual. +; +; Note: +; Some section names (enclosed in []) are system-defined and should not be changed. +; Private section names start with an '_'. Those can be changed. +; +; Refer to the Windows DDK documentation for more information on INF files. +; + +;****************************************************************************** +; Version section +;------------------------------------------------------------------------------ +[Version] +Signature="$Windows NT$" +Provider=%S_Provider% +DriverVer=02/07/2007,2.40.0.0 + +; This specifies the .cat file provided by WHQL if the driver is certified. +CatalogFile=ActionReplayDS_x64.cat + +; +; ### modify here ### +; Select an appropriate class for the device. +; There are several options: +; - Use the class shown below. It is defined by USBIO and is appropriate for testing purposes. +; - Define your own class by generating a private GUID and a class description. +; - Use a system-defined class. This is required for a device that belongs to a device class +; that is supported by system-provided drivers, HID, USB Audio for instance. +; For example, to replace the default USB mouse driver by USBIO you have to specify the HID +; class here: Class=HIDClass ClassGuid={745a17a0-74d3-11d0-b6fe-00a0c90f57da} +; +; we use a private device class that is defined by USBIO: +Class=USBIOControlledDevices +ClassGUID={96e73b6e-7a5a-11d4-9f24-0080c82727f4} + + +;****************************************************************************** +; Class Install section (optional) +;------------------------------------------------------------------------------ +; +; ### modify here ### +; The following sections are required if a private device class is used +; (see also the comments above). +; These sections should be removed completely if a system-defined class is used. +; +[ClassInstall32] +AddReg=_AddReg_ClassInstall + +[_AddReg_ClassInstall] +HKR,,,,"%S_DeviceClassDisplayName%" +HKR,,Icon,,"-20" + + +;****************************************************************************** +; Options +;------------------------------------------------------------------------------ +[ControlFlags] +; Advanced options can be specified here. +; For details, refer to the Windows DDK documentation. + + +;****************************************************************************** +; Manufacturer section +;------------------------------------------------------------------------------ +[Manufacturer] +%S_Mfg%=_Models, ntamd64 + + +;****************************************************************************** +; Models section +;------------------------------------------------------------------------------ +; x64-based systems +[_Models.ntamd64] +; This section specifies your device's hardware ID. + +; *** The following line was generated by USBIO Installation Wizard. *** +%S_DeviceDesc%=_Install, USB\Vid_05fd&Pid_eeae&Rev_0301 + + +;****************************************************************************** +; Install sections x64-based systems +;------------------------------------------------------------------------------ +[_Install.ntamd64] +CopyFiles=_CopyFiles_sys_x64 + +[_Install.ntamd64.Services] +AddService = %S_ServiceName%, 0x00000002, _AddService_x64, _EventLog_x64 + +[_Install.ntamd64.HW] +AddReg=_AddReg_HW + +[_AddService_x64] +ServiceType = 1 ; SERVICE_KERNEL_DRIVER +StartType = 3 ; SERVICE_DEMAND_START +ErrorControl = 1 ; SERVICE_ERROR_NORMAL +ServiceBinary = %10%\System32\Drivers\%S_DriverName_x64%.sys + +[_EventLog_x64] +AddReg=_EventLog_x64_AddReg + +[_EventLog_x64_AddReg] +HKR,,EventMessageFile,%REG_EXPAND_SZ%,"%%SystemRoot%%\System32\IoLogMsg.dll;%%SystemRoot%%\System32\drivers\%S_DriverName_x64%.sys" +HKR,,TypesSupported, %REG_DWORD%,7 + + +;****************************************************************************** +; Registry sections +;------------------------------------------------------------------------------ +[_AddReg_HW] +; The following string is used by the Cleanup Wizard to unambiguously identify +; USBIO devices and INF files. The entry can be removed completely from a final +; product's INF where the Cleanup Wizard is not needed. +; On the other hand, it does not harm anything if the entry is kept in place. +HKR,,CleanupWizard_DeviceIdentString,%REG_SZ%,"{DAB6A146-D93E-48ab-B3E5-374AB8FFF277}" + +; +; ### modify here ### +; Enable the next line to create an additional private user interface for your device. +; This is strongly recommended if you ship the driver together with a product. +; DO NOT USE an existing GUID. Generate a new one instead ! +; Use guidgen.exe to generate a new GUID, copy-paste it into the following line. +;HKR,,DriverUserInterfaceGuid,%REG_SZ%,"{????????-????-????-????-????????????}" + +; Uncomment this line to disable the default software interface of the driver +; This is recommended if you ship the driver together with a product. +;HKR,, DisableDefaultInterface, %REG_DWORD%, 1 + +; ### modify here ### +; Set the default behaviour of the driver for Windows 2000 and Windows XP +; For a description of the parameters, refer to the USBIO Reference Manual. +HKR,,PowerStateOnOpen, %REG_DWORD%, 0 +HKR,,PowerStateOnClose, %REG_DWORD%, 0 +HKR,,MinPowerStateUsed, %REG_DWORD%, 3 +HKR,,MinPowerStateUnused, %REG_DWORD%, 3 +HKR,,EnableRemoteWakeup, %REG_DWORD%, 0 +HKR,,AbortPipesOnPowerDown,%REG_DWORD%, 1 +HKR,,UnconfigureOnClose, %REG_DWORD%, 1 +HKR,,ResetDeviceOnClose, %REG_DWORD%, 0 +HKR,,MaxIsoPackets, %REG_DWORD%, 512 +HKR,,ShortTransferOk, %REG_DWORD%, 1 +HKR,,RequestTimeout, %REG_DWORD%, 1000 +HKR,,SuppressPnPRemoveDlg, %REG_DWORD%, 1 + +; Uncomment the following lines to enable automatic configuration +; of the device when the USBIO driver starts. +;HKR,,ConfigIndex, %REG_DWORD%, 0 +;HKR,,Interface, %REG_DWORD%, 0 +;HKR,,AlternateSetting, %REG_DWORD%, 0 + +; Uncomment the following lines to enable FX firmware download. +; The firmware file must be located in "%SystemRoot%\System32\Drivers". +; You cannot specify a path for the file. +;HKR,,FxFwFile, %REG_SZ%, "YourFirmwareFile.ihx" +;HKR,,FxBootloaderCheck, %REG_DWORD%, 1 +;HKR,,FxExtRamBase, %REG_DWORD%, 0x4000 + +; NOTE: You can copy the firmware file to "%SystemRoot%\System32\Drivers" during driver installation. +; If you want to do this then you have to add the firmware file to [_CopyFiles_sys] and +; [SourceDisksFiles] sections. See below. + + +;****************************************************************************** +; Copy Files section +;------------------------------------------------------------------------------ +[_CopyFiles_sys_x64] +; ### modify here ### +; Specify the correct file name of the driver binary. +; *** The following line was generated by USBIO Installation Wizard. *** +ActionReplayDS_x64.sys +; If you want to copy a firmware file, activate the following line. +;YourFirmwareFile.ihx + + +;****************************************************************************** +; Destination Directories +;------------------------------------------------------------------------------ +[DestinationDirs] +DefaultDestDir = 12 ; %windir%\system32\drivers +_CopyFiles_sys_x64 = 12 + + +;****************************************************************************** +; Disk Layout +;------------------------------------------------------------------------------ +[SourceDisksNames.amd64] +1=%S_DiskName%,, + +[SourceDisksFiles.amd64] +; ### modify here ### +; Specify the correct file name of the driver binary. +; *** The following line was generated by USBIO Installation Wizard. *** +ActionReplayDS_x64.sys=1 +; If you want to copy a firmware file, activate the following line. +;YourFirmwareFile.ihx=1 + + +;****************************************************************************** +; Text Strings +;------------------------------------------------------------------------------ +[Strings] +; +; Non-Localizable Strings, DO NOT MODIFY! +; +REG_SZ = 0x00000000 +REG_MULTI_SZ = 0x00010000 +REG_EXPAND_SZ = 0x00020000 +REG_BINARY = 0x00000001 +REG_DWORD = 0x00010001 + + +; +; Localizable Strings, modify as required +; + +; ### modify here ### +; Edit the strings in this section according to your needs. +; Some of the strings are shown at the user interface. + +; provider name +S_Provider="Datel Design & Development" +; manufacturer name +S_Mfg="Datel Design & Development" + +; device class display name, shown in Device Manager +S_DeviceClassDisplayName="USBIO controlled devices" + + +; device description +; *** The following line was generated by USBIO Installation Wizard. *** +S_DeviceDesc="Action Replay DS (NDS Link) x64" + +; device description +S_DeviceDesc1="Action Replay DS (NDS Link) x64" + +; disk name +S_DiskName="Action Replay DS (NDS Link) Driver Disk" + + +; File name of driver executable. +; If the name is modified, the [_CopyFiles_sys] and [SourceDisksFiles] +; sections must also be modified ! +; *** The following line was generated by USBIO Installation Wizard. *** +S_ServiceName="ActionReplayDS" +; *** The following line was generated by USBIO Installation Wizard. *** +S_DriverName_x64="ActionReplayDS_x64" + + +; *** EOF *** diff --git a/archive/Action_Replay/Action_Replay_DS_and_Media_Edition/CodeManager/1.25_HW1_ME/ActionReplayDS_x64.sys b/archive/Action_Replay/Action_Replay_DS_and_Media_Edition/CodeManager/1.25_HW1_ME/ActionReplayDS_x64.sys new file mode 100644 index 0000000..aa78d10 Binary files /dev/null and b/archive/Action_Replay/Action_Replay_DS_and_Media_Edition/CodeManager/1.25_HW1_ME/ActionReplayDS_x64.sys differ diff --git a/archive/Action_Replay/Action_Replay_DS_and_Media_Edition/CodeManager/1.25_HW1_ME/Setup.exe b/archive/Action_Replay/Action_Replay_DS_and_Media_Edition/CodeManager/1.25_HW1_ME/Setup.exe new file mode 100644 index 0000000..0cb8079 Binary files /dev/null and b/archive/Action_Replay/Action_Replay_DS_and_Media_Edition/CodeManager/1.25_HW1_ME/Setup.exe differ diff --git a/archive/Action_Replay/Action_Replay_DS_and_Media_Edition/CodeManager/1.25_HW1_ME/WindowsInstaller-KB893803-v2-x86.exe b/archive/Action_Replay/Action_Replay_DS_and_Media_Edition/CodeManager/1.25_HW1_ME/WindowsInstaller-KB893803-v2-x86.exe new file mode 100644 index 0000000..a7e88b5 Binary files /dev/null and b/archive/Action_Replay/Action_Replay_DS_and_Media_Edition/CodeManager/1.25_HW1_ME/WindowsInstaller-KB893803-v2-x86.exe differ diff --git a/archive/Action_Replay/Action_Replay_DS_and_Media_Edition/CodeManager/1.25_HW1_ME/actionreplayds.cat b/archive/Action_Replay/Action_Replay_DS_and_Media_Edition/CodeManager/1.25_HW1_ME/actionreplayds.cat new file mode 100644 index 0000000..7e3ce87 Binary files /dev/null and b/archive/Action_Replay/Action_Replay_DS_and_Media_Edition/CodeManager/1.25_HW1_ME/actionreplayds.cat differ diff --git a/archive/Action_Replay/Action_Replay_DS_and_Media_Edition/CodeManager/1.25_HW1_ME/actionreplayds_x64.cat b/archive/Action_Replay/Action_Replay_DS_and_Media_Edition/CodeManager/1.25_HW1_ME/actionreplayds_x64.cat new file mode 100644 index 0000000..3827f47 Binary files /dev/null and b/archive/Action_Replay/Action_Replay_DS_and_Media_Edition/CodeManager/1.25_HW1_ME/actionreplayds_x64.cat differ diff --git a/archive/Action_Replay/Action_Replay_DS_and_Media_Edition/CodeManager/1.25_HW1_ME/autorun.inf b/archive/Action_Replay/Action_Replay_DS_and_Media_Edition/CodeManager/1.25_HW1_ME/autorun.inf new file mode 100644 index 0000000..39eabe6 --- /dev/null +++ b/archive/Action_Replay/Action_Replay_DS_and_Media_Edition/CodeManager/1.25_HW1_ME/autorun.inf @@ -0,0 +1,3 @@ +[autorun] +open=setup.exe +icon=setup.exe diff --git a/archive/Action_Replay/Action_Replay_DS_and_Media_Edition/CodeManager/1.25_HW1_ME/msxml.msi b/archive/Action_Replay/Action_Replay_DS_and_Media_Edition/CodeManager/1.25_HW1_ME/msxml.msi new file mode 100644 index 0000000..a352182 Binary files /dev/null and b/archive/Action_Replay/Action_Replay_DS_and_Media_Edition/CodeManager/1.25_HW1_ME/msxml.msi differ diff --git a/archive/Action_Replay/Action_Replay_DS_and_Media_Edition/CodeManager/1.25_HW1_ME/readme.txt b/archive/Action_Replay/Action_Replay_DS_and_Media_Edition/CodeManager/1.25_HW1_ME/readme.txt new file mode 100644 index 0000000..5b96d1f --- /dev/null +++ b/archive/Action_Replay/Action_Replay_DS_and_Media_Edition/CodeManager/1.25_HW1_ME/readme.txt @@ -0,0 +1,50 @@ +Action Replay Code Manager - Readme.txt +--------------------------------------- + +Introduction +------------ + +Action Replay DS is a powerful cheat code system for Nintendo DS. +This software, Action Replay Code Manager, allows you to connect +your PC to your Action Replay DS cartridge via USB to add new +codes which can be downloaded from various Internet sources using +this software. + + +Minimum System Requirements +--------------------------- + +Computer / Processor 1GHz+ processor recommended +Communication Internet connection + USB Port (USB 2.0 highly recommended) +Operating System Windows® XP Home or XP Pro. +Memory 256Mb RAM +Install size: 10MB of free hard-disk space for program + installation plus additional hard drive + space for storing codes. +Display 800X600 SVGA or higher, True Colour +Drive CD-ROM drive (for installation) + + + +Updating the Software +--------------------- + +When you first install Action Replay Code Manager it is highly +recommended that you ensure it is up-to-date by clicking the +'Update Software' button on the main menu. This will download +any software updates for the PC application and for the Action +Replay DS firmware. + + +Version History +--------------- + +1.00 First commercial release of Action Replay Code Manager + No known issues. +1.21 Support for new board rev. +1.22/23 Codelist changes + +1.24 Driver & software updates +1.25 Signed drivers for Vista / Vista64 + \ No newline at end of file diff --git a/archive/Action_Replay/Action_Replay_DS_and_Media_Edition/FIRM/ARDS_HW0_1.55.bin b/archive/Action_Replay/Action_Replay_DS_and_Media_Edition/FIRM/ARDS_HW0_1.55.bin new file mode 100644 index 0000000..757a747 Binary files /dev/null and b/archive/Action_Replay/Action_Replay_DS_and_Media_Edition/FIRM/ARDS_HW0_1.55.bin differ diff --git a/archive/Action_Replay/Action_Replay_DS_and_Media_Edition/FIRM/ARDS_HW1_1.71.bin b/archive/Action_Replay/Action_Replay_DS_and_Media_Edition/FIRM/ARDS_HW1_1.71.bin new file mode 100644 index 0000000..e8f0bdb Binary files /dev/null and b/archive/Action_Replay/Action_Replay_DS_and_Media_Edition/FIRM/ARDS_HW1_1.71.bin differ diff --git a/archive/Action_Replay/Action_Replay_DS_and_Media_Edition/FIRM/ARME_2.01_Full.bin b/archive/Action_Replay/Action_Replay_DS_and_Media_Edition/FIRM/ARME_2.01_Full.bin new file mode 100644 index 0000000..ea3f740 Binary files /dev/null and b/archive/Action_Replay/Action_Replay_DS_and_Media_Edition/FIRM/ARME_2.01_Full.bin differ diff --git a/archive/Action_Replay/Action_Replay_DS_and_Media_Edition/FIRM/ARME_2.05_Full.bin b/archive/Action_Replay/Action_Replay_DS_and_Media_Edition/FIRM/ARME_2.05_Full.bin new file mode 100644 index 0000000..ea3f740 Binary files /dev/null and b/archive/Action_Replay/Action_Replay_DS_and_Media_Edition/FIRM/ARME_2.05_Full.bin differ diff --git a/archive/Action_Replay/Action_Replay_DS_and_Media_Edition/FIRM/ARME_2.05_Upgrade.bin b/archive/Action_Replay/Action_Replay_DS_and_Media_Edition/FIRM/ARME_2.05_Upgrade.bin new file mode 100644 index 0000000..8c76c76 Binary files /dev/null and b/archive/Action_Replay/Action_Replay_DS_and_Media_Edition/FIRM/ARME_2.05_Upgrade.bin differ diff --git a/archive/Action_Replay/Action_Replay_DS_and_Media_Edition/README.txt b/archive/Action_Replay/Action_Replay_DS_and_Media_Edition/README.txt new file mode 100644 index 0000000..6c1b168 --- /dev/null +++ b/archive/Action_Replay/Action_Replay_DS_and_Media_Edition/README.txt @@ -0,0 +1,70 @@ +Recovering a bricked red-label, media edition, or pre-DSi Pokémon ARDS (only tested on DS Phat/Lite): +HW0 (USB mode works on <=1.55): +Install CodeManager 1.00 and the driver (must use WinXP/an XP VM with USB passthrough/32-bit Windows/or force driver signatures off). +Connect the USB side of the ARDS (device will show up in devmgmt.msc, if it's unknown, update the driver from there, pointing at the folder) +Run 'ARDS_hw0_1.02.nds' from a flashcart. +Swap to the ARDS, tap the mouse icon if it doesn't automatically enter PC mode. +Drag&Drop 'ARDS_HW0_1.55.bin' on the top section of CodeManager (*above* the codelists, or it'll parse wrong) +Wait for the firmware to upload, confirm saving it afterwards. +Wait for the reboot prompt, reboot your console, firmware should now load properly. +Check if code upload works properly. If not, see later section. + +HW1 (USB Mode works on >1.5X): +Install CodeManager 1.25 and the driver (standard for XP/32-bit, x64 for Vista+ 64-bit) +Connect the USB side of the ARDS (device will show up in devmgmt.msc, if it's unknown, update the driver from there, pointing at the folder) +Run 'ARDS_hw1_ME_1.71.nds' from a flashcart. +Swap to the ARDS, tap the mouse icon if it doesn't automatically enter PC mode. +Drag&Drop 'ARDS_HW1_1.71.bin' on the top section of CodeManager (*above* the codelists, or it'll parse wrong) +Wait for the firmware to upload, confirm saving it afterwards. +Wait for the reboot prompt, reboot your console, firmware should now load properly. +Check if code upload works properly. If not, see later section. + +Media Edition (microSD slot) recovery: +Install CodeManager 1.25 and the driver (standard for XP/32-bit, x64 for Vista+ 64-bit) +Connect the USB side of the ARDS (device will show up in devmgmt.msc, if it's unknown, update the driver from there, pointing at the folder) +Run 'ARDS_hw1_ME_1.71.nds' from a flashcart. +Swap to the ARDS, tap the mouse icon if it doesn't automatically enter PC mode. +Drag&Drop 'ARME_2.05_Full.bin' on the top section of CodeManager (*above* the codelists, or it'll parse wrong) +Wait for the firmware to upload, confirm saving it afterwards. +Wait for the reboot prompt, reboot your console, firmware should now load properly. +Check if code upload works properly. If not, see later section. +Codelist SD import/export may not work on 2.05 (but it has better game compatibility), hence 2.01 is also provided. + +Media Edition (microSD slot) upgrade: +Install CodeManager 1.25 and the driver (standard for XP/32-bit, x64 for Vista+ 64-bit) +Connect the USB side of the ARDS (device will show up in devmgmt.msc, if it's unknown, update the driver from there, pointing at the folder) +Launch your ARME, go into Action Replay mode, tap the mouse icon if it doesn't automatically enter PC mode. +Drag&Drop 'ARME_2.05_Upgrade.bin' on the top section of CodeManager (*above* the codelists, or it'll parse wrong) +Wait for the firmware to upload, confirm saving it afterwards. +Wait for the reboot prompt, reboot your console, firmware should now load and display 2.05 in AR mode. +Check if code upload works properly. If not, see later section. +Codelist SD import/export may not work on 2.05 (but it has better game compatibility), hence 2.01 is also provided (see recovery, or write the CCAR header with ards-firmwaretool). + +If you can't add codes (not enough free space): +Hold A+B, followed by Start+Select as soon as the white screen (before unlicensed text) appears. +ARME users: hold all four buttons right after tapping to enter AR mode, before loading appears. + +External sources: +ARDS FirmwareTool: https://github.com/RattletraPM/ards-firmwaretool +CodeManager 1.25: http://uk.codejunkies.com/support/article.aspx?article_id=417 +fw1.55: http://web.archive.org/web/20131011070331if_/http://www.datelcustomerservice.com/files/NDS-ARDS_firm_1_55.zip +fw1.71: http://uk.codejunkies.com/support/article.aspx?article_id=434 +fw2.05 (upgrade): http://web.archive.org/web/20141120191443if_/http://www.datelcustomerservice.com/files/NDS-ARME_firm_2_05.zip + +Missing: Pokemon ARDS dump/fw. +Untested: Recovering with a DSi/3DS. May work from TWiLightMenu or ntr_launcher with the AR already inserted, only glitched out for me. + +Further interesting shenanigans: + +This trilogy of blog posts fixing a bricked HW0 unit. +https://blog.claranguyen.me/post/2022/06/20/ards-breakdown-pt1/ +https://blog.claranguyen.me/post/2022/07/10/ards-breakdown-pt2/ +https://blog.claranguyen.me/post/2022/08/06/ards-breakdown-pt3/ +My first ARME was bricked the same way as described in pt2 but at offset 0x5556. One byte off. + +AR Media Edition can access the Max Media Player Microdrive / CF Dock contents. +It also shares a DLDI with the ARDSi-µSD and Games'n'Music. It even boots TWiLightMenu. Painfully slowly. + +Why 1.02 for HW0? +Mine came with 1.54, and constantly spat out "Error!" when connected to CodeManager. Swap-booted 1.55 didn't wanna talk to any version either. +Turns out, 1.02 works fine. And so does 1.55 *after* flashing it through 1.02. Datel hardware is just weird sometimes. \ No newline at end of file diff --git a/archive/Action_Replay/Action_Replay_DS_and_Media_Edition/ROM/ARDS_hw0_1.02.nds b/archive/Action_Replay/Action_Replay_DS_and_Media_Edition/ROM/ARDS_hw0_1.02.nds new file mode 100644 index 0000000..4afae2a Binary files /dev/null and b/archive/Action_Replay/Action_Replay_DS_and_Media_Edition/ROM/ARDS_hw0_1.02.nds differ diff --git a/archive/Action_Replay/Action_Replay_DS_and_Media_Edition/ROM/ARDS_hw1_ME_1.71.nds b/archive/Action_Replay/Action_Replay_DS_and_Media_Edition/ROM/ARDS_hw1_ME_1.71.nds new file mode 100644 index 0000000..5808e3c Binary files /dev/null and b/archive/Action_Replay/Action_Replay_DS_and_Media_Edition/ROM/ARDS_hw1_ME_1.71.nds differ diff --git a/archive/Action_Replay/Action_Replay_DSi_non-3DS_FWUpdate_v1.25/ARDSi-FirmwareUpdate-1.4.5.exe b/archive/Action_Replay/Action_Replay_DSi_and_3DS/ARDSi-FirmwareUpdate-1.4.5.exe similarity index 100% rename from archive/Action_Replay/Action_Replay_DSi_non-3DS_FWUpdate_v1.25/ARDSi-FirmwareUpdate-1.4.5.exe rename to archive/Action_Replay/Action_Replay_DSi_and_3DS/ARDSi-FirmwareUpdate-1.4.5.exe diff --git a/archive/Action_Replay/Action_Replay_DSi_non-3DS_FWUpdate_v1.25/ActionReplayDsiCodeManagerSetup-2018.exe b/archive/Action_Replay/Action_Replay_DSi_and_3DS/ActionReplayDsiCodeManagerSetup-2018.exe similarity index 100% rename from archive/Action_Replay/Action_Replay_DSi_non-3DS_FWUpdate_v1.25/ActionReplayDsiCodeManagerSetup-2018.exe rename to archive/Action_Replay/Action_Replay_DSi_and_3DS/ActionReplayDsiCodeManagerSetup-2018.exe diff --git a/archive/Action_Replay/Action_Replay_DSi_non-3DS_FWUpdate_v1.25/README.txt b/archive/Action_Replay/Action_Replay_DSi_and_3DS/README.txt similarity index 50% rename from archive/Action_Replay/Action_Replay_DSi_non-3DS_FWUpdate_v1.25/README.txt rename to archive/Action_Replay/Action_Replay_DSi_and_3DS/README.txt index 22a43b3..1404b1c 100644 --- a/archive/Action_Replay/Action_Replay_DSi_non-3DS_FWUpdate_v1.25/README.txt +++ b/archive/Action_Replay/Action_Replay_DSi_and_3DS/README.txt @@ -1,5 +1,3 @@ -THIS IS SPECIFICALLY FOR DSi ACTION REPLAY CARTS, NOT DSi + 3DS MODELS!!! - 1: Installing CodeManager Install "ActionReplayDsiCodeManagerSetup-2018.exe" Run "Action Replay DSi Code Manager" @@ -11,8 +9,15 @@ Click on the Code Manager icon in the top left Press About Action Replay DSi Code Manager Press "Reset Hardware" accept any warnings and wait. -3: Updating the AR -Install "ARDSi-FirmwareUpdate-1.4.5.exe" -Run "DSi Compatible Action Replay Firmware Update" -Connect your Action Replay cart -Press "Start" and wait. \ No newline at end of file +3: Updating the AR + DSi/microSD version: + Install "ARDSi-FirmwareUpdate-1.4.5.exe" + Run "DSi Compatible Action Replay Firmware Update" + Connect your Action Replay cart + Press "Start" and wait. + + Blue-label/3DS version: + Install "Setup_AR3DS_FirmwareUpdate (Jun 2013).exe" + Run "3DS Compatible Action Replay Firmware Update" + Connect your Action Replay cart + Press "Start" and wait. \ No newline at end of file diff --git a/archive/Action_Replay/Action_Replay_DSi_and_3DS/Setup_AR3DS_FirmwareUpdate (Jun 2013).exe b/archive/Action_Replay/Action_Replay_DSi_and_3DS/Setup_AR3DS_FirmwareUpdate (Jun 2013).exe new file mode 100644 index 0000000..f40f8ee Binary files /dev/null and b/archive/Action_Replay/Action_Replay_DSi_and_3DS/Setup_AR3DS_FirmwareUpdate (Jun 2013).exe differ diff --git a/archive/Action_Replay/Makefile b/archive/Action_Replay/Makefile index cf6fbf6..3cabb1e 100644 --- a/archive/Action_Replay/Makefile +++ b/archive/Action_Replay/Makefile @@ -5,10 +5,13 @@ export BASE := $(shell basename $(CURDIR)) export OUT := $(TOPDIR)/../../out export COMMON := $(TOPDIR)/../../common-kernels -package: directory Action_Replay_DSi_non-3DS_FWUpdate_v1.25.zip +package: directory Action_Replay_DS_and_Media_Edition.zip Action_Replay_DSi_and_3DS.zip directory: mkdir -p $(OUT)/$(BASE) -Action_Replay_DSi_non-3DS_FWUpdate_v1.25.zip: directory - cd $(TOPDIR)/Action_Replay_DSi_non-3DS_FWUpdate_v1.25 && zip -r $(OUT)/$(BASE)/$@ * +Action_Replay_DS_and_Media_Edition.zip: directory + cd $(TOPDIR)/Action_Replay_DS_and_Media_Edition && zip -r $(OUT)/$(BASE)/$@ * + +Action_Replay_DSi_and_3DS.zip: directory + cd $(TOPDIR)/Action_Replay_DSi_and_3DS && zip -r $(OUT)/$(BASE)/$@ *