#.BIG FILE EXTRACTOR ARCHIVE#
#.BIG FILE EXTRACTOR FREE#

As such the start address + the length of one file is typically the start address of the next. The rest of the file then should be raw file data, with each file entry in the header owning the data between its start addresses and its start address + it’s length, including the byte at the start address. As already stated there is no metadeta, and the files are typically lumped one after the other. After that it’s just null data for the rest of the header 8. After the last entry there is 4 bytes of text in the form of “LXXX”, where XXX is some number or other, usually 200 something. Immediately after the termination character of the string comes the next entry.

#.BIG FILE EXTRACTOR ARCHIVE#

These consist of 4 bytes for the address in the archive at which the file data starts 6, 4 bytes holding the length of the file 7, and a null terminated string for the file path. big file and the address at which the header ends.Īfter this come the individual file descriptors. 5 Next comes the number of files contained in the. All other numbers in the header are big-endian, e.g. The next 4 bytes are the size of the file as a little-endian 32-bit unsigned integer, e.g. At the moment I don’t know if there are any differences between the two. All this does is tell you that this is, in fact, a. The first 4 bytes of the header are really simple. These are just lumped on one after another with no metadeta in between, so the only part that is really of interest is the header. Second comes all the data contained in the files themselves. First comes the header, which identifies and enumerates all the files contained in the archive. Here is a screenshot of one of BFME2’s smaller. It is actually a rather simple format that doesn’t compress the files at all 4. BIG files are storage containers, sometimes holding gigabytes 3 of game assets.

#.BIG FILE EXTRACTOR FREE#

Please feel free to pitch in when such a situation arises. I intend to outline the structure of such files as I work on them so that anyone else interested doesn’t have to do it all over again and also because there will probably be some things that don’t make sense to me, or I simply can’t find the purpose of. In my endeavor to make an open source 1 RTS engine capable of playing EA SAGE engine games, such as The Battle for Middle Earth series, I will be reverse engineering the binary files involved 2.

.big file extractor