Page 1 of 1

Possible bug in parsing of LZX headers

Posted: Mon May 18, 2020 2:46 pm
by PoroCYon
Hi, I've tried using the LZX decompressor from wimlib to parse XNB (XNA content container format) files, and noticed that it first reads the block type, and then the block size flag, while FNA, the open-source XNA reimplementation does it the other way around. Could this be a bug in the parser, or a nonstandard thing introduced by the makers of XNA?

Re: Possible bug in parsing of LZX headers

Posted: Fri May 22, 2020 6:00 am
by synchronicity
What wimlib does is correct for WIM files. There could be other variants of LZX though.