ExeFS - Revision history

Neobrain: /* File headers */

2016-03-20T18:33:43Z

File headers

← Older revision		Revision as of 21:33, 20 March 2016
Line 33:		Line 33:

	==== File headers ====		==== File headers ====
	There are a maximum of 10* file headers in the ExeFS format, ~~which~~ have the following structure:		There are a maximum of 10 file headers in the ExeFS format. (This maximum number of file headers is disputable, with makerom indicating a maximum of 8 sections and makecia indicating a maximum of 10. From a non-SDK point of view, the ExeFS header format can hold no more than 10 file headers within the currently define size of 0x200 bytes.) The file headers have the following structure:

	{\| class="wikitable" border="1"		{\| class="wikitable" border="1"
Line 53:		Line 53:
	\| File size		\| File size
	\|}		\|}

	<nowiki>*</nowiki> The maximum number of ExeFS file headers, is disputable. With makerom indicating a maximum of 8 sections, and makecia indicating a maximum of 10. From a non-SDK point of view ExeFS header format can hold no more than 10 file headers within the currently define size of 0x200 bytes.

	File offsets are non-inclusive of the header's size (0x200 bytes). Also, file headers which are not used are filled with all zeros.		File offsets are non-inclusive of the header's size (0x200 bytes). Also, file headers which are not used are filled with all zeros.

2016-03-20T18:32:21Z

This is not Visual Studio, yo

2016-03-20T18:17:36Z

← Older revision		Revision as of 21:17, 20 March 2016
Line 1:		Line 1:
	~~=== Overview ===~~
	ExeFS or Executable Filesystem contains information related to the executable program, and is the part of the [[NCCH#CXI\|CXI]] format.		ExeFS or Executable Filesystem contains information related to the executable program, and is the part of the [[NCCH#CXI\|CXI]] format.

2015-10-20T17:57:04Z

Correct filenames

← Older revision		Revision as of 21:57, 20 October 2015
Line 4:		Line 4:
	The ExeFS usually contains one or more of the following files:		The ExeFS usually contains one or more of the following files:
	* .code Contains the code binary, which can be optionally reverse-LZSS compressed via an exheader flag.		* .code Contains the code binary, which can be optionally reverse-LZSS compressed via an exheader flag.
	* [[logo\|.logo]] Contains distribution licensing Binary data.		* [[logo\|logo]] Contains distribution licensing Binary data.
	* [[File Formats\|.banner]] Contains the banner which homemenu uses for this CXI.		* [[File Formats\|banner]] Contains the banner which homemenu uses for this CXI.
	* [[SMDH\|.icon]] Contains the icon which homemenu displays for this CXI.		* [[SMDH\|icon]] Contains the icon which homemenu displays for this CXI.

	=== Format ===		=== Format ===

2015-10-20T17:55:26Z

Format

← Older revision		Revision as of 21:55, 20 October 2015
Line 30:		Line 30:
	\| File hashes (10 hashes maximum, 32 bytes each, one for each header)		\| File hashes (10 hashes maximum, 32 bytes each, one for each header)
	\|}		\|}

			File hashes are stored in reverse order, i.e. the hash at offset 0x1E0 corresponds to the first ExeFS section.

	==== File headers ====		==== File headers ====

2013-09-12T13:16:49Z

← Older revision		Revision as of 17:16, 12 September 2013
Line 32:		Line 32:

	==== File headers ====		==== File headers ====
	There are a maximum of 10 file headers in the ExeFS format, which have the following structure:		There are a maximum of 10* file headers in the ExeFS format, which have the following structure:

	{\| class="wikitable" border="1"		{\| class="wikitable" border="1"
Line 52:		Line 52:
	\| File size		\| File size
	\|}		\|}

			<nowiki>*</nowiki> The maximum number of ExeFS file headers, is disputable. With makerom indicating a maximum of 8 sections, and makecia indicating a maximum of 10. From a non-SDK point of view ExeFS header format can hold no more than 10 file headers within the currently define size of 0x200 bytes.

	File offsets are non-inclusive of the header's size (0x200 bytes). Also, file headers which are not used are filled with all zeros.		File offsets are non-inclusive of the header's size (0x200 bytes). Also, file headers which are not used are filled with all zeros.

2013-07-25T12:58:55Z

It seems to actually be 10, instead of 8

← Older revision		Revision as of 16:58, 25 July 2013
Line 19:		Line 19:
	\|-		\|-
	\| 0x00		\| 0x00
	\| ~~0x80~~		\| 0xa0
	\| File headers (8 headers maximum, 16 bytes each)		\| File headers (10 headers maximum, 16 bytes each)
	\|-		\|-
	\| ~~0x80~~		\| 0xa0
	\| ~~0x80~~		\| 0x20
	\| Reserved		\| Reserved
	\|-		\|-
	\| ~~0x100~~		\| 0xc0
	\| ~~0x100~~		\| 0x140
	\| File hashes (8 hashes maximum, 32 bytes each, one for each header)		\| File hashes (10 hashes maximum, 32 bytes each, one for each header)
	\|}		\|}

	==== File headers ====		==== File headers ====
	There are a maximum of 8 file headers in the ExeFS format, which have the following structure:		There are a maximum of 10 file headers in the ExeFS format, which have the following structure:

	{\| class="wikitable" border="1"		{\| class="wikitable" border="1"

2012-07-18T15:43:04Z

← Older revision		Revision as of 19:43, 18 July 2012
Line 1:		Line 1:
	=== Overview ===		=== Overview ===
	ExeFS or Executable Filesystem contains information related to the executable program, and is the part of the CXI format.		ExeFS or Executable Filesystem contains information related to the executable program, and is the part of the [[NCCH#CXI\|CXI]] format.

	The ExeFS usually contains one or more of the following files:		The ExeFS usually contains one or more of the following files:

2012-06-08T15:04:46Z

← Older revision		Revision as of 19:04, 8 June 2012
Line 1:		Line 1:
	=== Overview ===		=== Overview ===
	ExeFS or Executable Filesystem, is the part of the CXI~~, which contains information related to the executable program~~.		ExeFS or Executable Filesystem contains information related to the executable program, and is the part of the CXI format.

	The ExeFS usually contains one or more of the following files:		The ExeFS usually contains one or more of the following files:

2012-06-08T15:03:49Z

← Older revision		Revision as of 19:03, 8 June 2012
Line 52:		Line 52:
	\| File size		\| File size
	\|}		\|}

			File offsets are non-inclusive of the header's size (0x200 bytes). Also, file headers which are not used are filled with all zeros.

	==== File hashes ====		==== File hashes ====
	Each file header has a corresponding file hash, which is the SHA256 hash calculated over the entire file contents.		Each file header has a corresponding file hash, which is the SHA256 hash calculated over the entire file contents.


	~~<nowiki>* Offsets are non-inclusive of the header's size(0x200 bytes).</nowiki>~~

	~~<nowiki>** The 'Logo' is not a compulsory part of ExeFS, so an ExeFS without a 'Logo', will have these entries of the header filled with zeros.</nowiki>~~
	.