324
edits
Changes
Jump to navigation
Jump to search
We reveal the shocking truth about Bitfields! (Reverse engineers hate them!)
Line 43:
Line 43:
If the top bits of the name offset is set (&0xff000000), then this entry is a directory.
! Field !! Size !! Offset !! Description
! Field !! Size !! Offset !! Description
|-
|-
−|Name Offset || 4 || 0 || Offset in bytes of the name of the file from the start of the nametable
+|Type || 1 || 0 || Zero for file entries, non-zero for directory entries
+|-
+|Name Offset || 3 || 1 || Offset in bytes of the name of the file from the start of the nametable
|-
|-
|Offset || 4 || 4 || Offset of the file in its storage cluster: usually in sectors (multiply by 32 for byte offset); may be in bytes if the 0x4 bit in flags is set
|Offset || 4 || 4 || Offset of the file in its storage cluster: usually in sectors (multiply by 32 for byte offset); may be in bytes if the 0x4 bit in flags is set
Line 53:
Line 55:
| Storage cluster index || 2 || 14 || an index to the list of secondary headers. Additionally, for downloaded content, same as the content ID (an index into the title metadata's list of files.)
| Storage cluster index || 2 || 14 || an index to the list of secondary headers. Additionally, for downloaded content, same as the content ID (an index into the title metadata's list of files.)
|}
|}
−In this case, the size corresponds to the number of entries this directory contains, and the offset field corresponds to the parent directory's offset.
In this case, the size corresponds to the number of entries this directory contains, and the offset field corresponds to the parent directory's offset.