Possible bug in parsing of LZX headers
Possible bug in parsing of LZX headers
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?
-
- Site Admin
- Posts: 473
- Joined: Sun Aug 02, 2015 10:31 pm
Re: Possible bug in parsing of LZX headers
What wimlib does is correct for WIM files. There could be other variants of LZX though.