6,264
edits
Changes
Jump to navigation
Jump to search
Line 78:
Line 78: − + Line 169:
Line 169: − +
→Partitions
'''DISA'''
'''DISA'''
* If the uint32 @ 0x168 into the image in the DISA is a %1=1, then first table is is hashed, otherwise the second DIFI table is hashed.
* If the uint32 @ 0x168 into the image in the DISA(the low 8-bits) is non-zero, then first table is is hashed, otherwise the second DIFI table is hashed.
* If the table has more then 1 DIFI then the uint32 @ 0x168 is the offset from the DATA partition to the file base (masked with 0xFFFFFFFE).
* If the table has more then 1 DIFI then the uint32 @ 0x168 is the offset from the DATA partition to the file base (masked with 0xFFFFFFFE).
* At offset 0x0 in the image is the 0x100-byte "master hash-table", however normally only the first entry is used. This seems to hash the 0x100-byte DISA?
* At offset 0x0 in the image is the 0x100-byte "master hash-table", however normally only the first entry is used. This seems to hash the 0x100-byte DISA?
* Seems to be the [[extdata]] equivalent of DISA, this seems to start @ offset 0x100 in extdata using FS.(DIFF never seems to be used for regular savegames)
* Seems to be the [[extdata]] equivalent of DISA, this seems to start @ offset 0x100 in extdata using FS.(DIFF never seems to be used for regular savegames)
* When the active-table field is zero, the secondary partition table is used. Otherwise, the primary partition table is used.
* When the active-table field low 8-bits is non-zero, the primary partition is used. Otherwise, the secondary partition is used.
{| class="wikitable"
{| class="wikitable"