399
edits
Changes
Jump to navigation
Jump to search
Line 39:
Line 39: +
no edit summary
Hi Neimod, love your work! my question is: The extended header suppose to start right after the NCCH header so why there is twice the space? (extended header size is usually 1024 and plain region offset is usually 5*512 = 2560 -> 2048 after the end of the ncch) thanks. --[[User:Elisherer|Elisherer]] 11:46, 6 September 2011 (CEST)
Hi Neimod, love your work! my question is: The extended header suppose to start right after the NCCH header so why there is twice the space? (extended header size is usually 1024 and plain region offset is usually 5*512 = 2560 -> 2048 after the end of the ncch) thanks. --[[User:Elisherer|Elisherer]] 11:46, 6 September 2011 (CEST)
:I'm not sure I understand you. The extended header does come right exactly after the NCCH header. The only place where this does not hold is the NCCH header at offset 0x1000, but this one header should be ignored because this space does not exist on a real card. I suspect this is the plaintext header from command 0x82 that was injected into the ROM in post-processing by the dumpergroup. --[[User:Neimod|Neimod]] 17:40, 6 September 2011 (CEST)
:I'm not sure I understand you. The extended header does come right exactly after the NCCH header. The only place where this does not hold is the NCCH header at offset 0x1000, but this one header should be ignored because this space does not exist on a real card. I suspect this is the plaintext header from command 0x82 that was injected into the ROM in post-processing by the dumpergroup. --[[User:Neimod|Neimod]] 17:40, 6 September 2011 (CEST)
::Thanks for the answer, what I meant is that there is a block (of 2048 bytes) between the ncch header and the plain region. this is where the extended header should be, and it supposed to be 1024 bytes. So my question was what are the extra 1024 bytes for (they are not zeros...) --[[User:Elisherer|Elisherer]] 19:07, 6 September 2011 (CEST)
I have a simple question why Neimod are thinking the code is compressed? I think LZSS is not good for binary images.
I have a simple question why Neimod are thinking the code is compressed? I think LZSS is not good for binary images.
:Because they just are. --[[User:Neimod|Neimod]] 17:40, 6 September 2011 (CEST)
:Because they just are. --[[User:Neimod|Neimod]] 17:40, 6 September 2011 (CEST)
:Game editors want to fit their game in the smallest ROM chip size possible, to reduce manufacturing costs. Also, encrypting blocks of zeros/FF is bad practices, compression avoids it. --[[User:Luigi2us|Luigi2us]] 18:17, 6 September 2011 (CEST)
:Game editors want to fit their game in the smallest ROM chip size possible, to reduce manufacturing costs. Also, encrypting blocks of zeros/FF is bad practices, compression avoids it. --[[User:Luigi2us|Luigi2us]] 18:17, 6 September 2011 (CEST)