Filesystem services: Difference between revisions

Line 1,269: Line 1,269:
|-
|-
| 0
| 0
| 0 for NCCH data, 1 for savedata. The latter is only valid for FSPXI.
| 0 for NCCH data, 1 for savedata. The latter is only valid for FSPXI. Value 2 is allowed via archive 0x3, it's unknown what this is.
|-
|-
| 1
| 1
Line 1,288: Line 1,288:
In this scenario, OpenFile returns a handle to the RomFS archive.
In this scenario, OpenFile returns a handle to the RomFS archive.


The 0x3 archive is an interface for the 0x2345678A archive with the current process programID+mediatype. The 3 words here are written to 0x2345678A-archive file_lowpath+0, with the rest of that lowpath set to all-zero. File lowpath:
The 0x3 archive is an interface for the 0x2345678A archive with the current process programID+mediatype. The file lowpath is 3-words. These words are written to 0x2345678A-archive file_lowpath+0, with the rest of that lowpath set to all-zero. File lowpath:
{| class="wikitable" border="1"
{| class="wikitable" border="1"
|-
|-
Line 1,295: Line 1,295:
|-
|-
| 0
| 0
| Type:
| See above. The only values which FS-module doesn't allow to be used here are:
* 0x0: Main RomFS.
* 0x1: Error 0xE0E046BE.
* 0x1: Invalid.
* 0x3: Error 0xE0E046BE.
* 0x2: Unknown.
* 0x3: Invalid.
* 0x4: FS-module executes svcBreak when using this.
* 0x4: FS-module executes svcBreak when using this.
|-
|-