Repacking nsp->nsz->nsp

[64ghost]

After translating nsp->nsz and back nsz->nsp. The resulting nsp is larger. The reason is that the data starts at address 0x8000. Up to address 0x8000 filled with zeros. Is it possible to reduce the void to a minimum.

[blawar]

edit: you are talking about the NSP padding. The NSP padding exists to allow operations on existing NSP containers (such as adding and deleting files. This space is small (less than 32kb). You could repack the NSP with a different tool if you really wanted to reclaim less than 32kb of space.

[nicoboss]

@64ghost This is fixed in the latest NSZ v4.3.0 release. The padding of the source NSP is now kept during compression/decompression making them always bit-identical (especially if --keep-delta is specified). The option --remove-padding was added to remove the padding of existing NSP/NSZ files to make them nxdumptool/no-intro compliant.