Process Services: Difference between revisions
No edit summary |
No edit summary |
||
Line 43: | Line 43: | ||
| 0x000D0042 | | 0x000D0042 | ||
| GenerateRandomBytes | | GenerateRandomBytes | ||
|- | |||
| 0x000E0082 | |||
| Interface for [[Process_Services_PXI]] New3DS command 0x04010084. | |||
|- | |||
| 0x000F0082 | |||
| Interface for [[Process_Services_PXI]] New3DS command 0x04020082. | |||
|- | |||
| 0x00100042 | |||
| Interface for [[Process_Services_PXI]] New3DS command 0x04030044. | |||
|- | |||
| 0x00110042 | |||
| Interface for [[Process_Services_PXI]] New3DS command 0x04040044. | |||
|} | |} | ||
Line 48: | Line 60: | ||
For GetRomId, GetRomId2, and GetRomMakerCode, PS-module uses [[FS:GetProgramLaunchInfo]] with the processID which was sent to PS-module via the command input. If GetProgramLaunchInfo fails, PS-module returns error 0xC90107FA. When the mediatype is value2 for gamecard, the PSPXI command is used, otherwise PS-module just clears the output data for the command response. | For GetRomId, GetRomId2, and GetRomMakerCode, PS-module uses [[FS:GetProgramLaunchInfo]] with the processID which was sent to PS-module via the command input. If GetProgramLaunchInfo fails, PS-module returns error 0xC90107FA. When the mediatype is value2 for gamecard, the PSPXI command is used, otherwise PS-module just clears the output data for the command response. | ||
PS module does not use any CheckNew3DS commands: commands 0x000E0082..0x00110042 are handled by PS module regardless of whether this is running on Old3DS/New3DS. Using these commands on Old3DS will result in Process9 returning an invalid command header error. |