6,264
edits
Changes
→Errors
| 0xD9004676
| 0xD9004676
| FSUSER: The specified service-command / archive is not accessible, due to the currently used exheader accessinfo not having the required bit(s) set. (This error can also indicate that the required ARM9 access-control mount flag is not enabled, in the exheader for any of the running ARM11 processes)
| FSUSER: The specified service-command / archive is not accessible, due to the currently used exheader accessinfo not having the required bit(s) set. (This error can also indicate that the required ARM9 access-control mount flag is not enabled, in the exheader for any of the running ARM11 processes)
|-
| 0xE0C046F9
| FSPXI: Specified read-size doesn't match the actual filesize, when accessing ExeFS.
|-
|-
| 0xE0E046BE
| 0xE0E046BE
| Invalid lowpath. This can also indicate that the specified archive-id does not exist, or that the specified archive-id is not accessible over FSPXI. In certain cases this can also be caused by attempting to open a FSUSER archive where none of the required bit(s) for the archive are set in the user-process exheader accessinfo.
| Invalid lowpath. This can also indicate that the specified archive-id does not exist, or that the specified archive-id is not accessible over FSPXI. In certain cases this can also be caused by attempting to open a FSUSER archive where none of the required bit(s) for the archive are set in the user-process exheader accessinfo.
|-
|-
| 0xE0C046F9
| 0xE0E046C1
| FSPXI: Specified read-size doesn't match the actual filesize, when accessing ExeFS.
| File-reading returns this when the input 64bit file-pos is negative, or when the file-pos is larger than the filesize.
|-
|-
| 0xE160F402
| 0xE160F402