User talk:Calvero

From ModdingWiki
Jump to navigation Jump to search

EPF format

Hi Calvero - on EPF Format your description differs to the file I have. Do you have a file in the format you described I could examine? Also, did you reverse engineer this format yourself or did it come from elsewhere? Thanks! -- Malvineous 12:41, 25 April 2010 (GMT)

I reverse engineered this format myself. The main difference between my description of this file format and your description is that, if I understand your description correctly, you're saying the header consists of two fields (BYTE signature[4] and UINT32LE fatOffset) and the first file starts at offset 8, while I'm saying the header consists of
Data type Description
BYTE signature[4] "EPFS"
UINT32LE fatOffset Offset of the FAT
BYTE zero this byte is always zero
UINT16LE iFileCount number of files
BYTE unknown[8] 8 bytes with an unknown meaning
and the first file starts at offset 0x13. I can't remember why I said there are 8 bytes with an unknown meaning in the header and I can't remember why I said UINT16LE iNumberOfFiles is zero based, so I'm probably wrong and you're right :). Do you still want a file in the format I described? I probably investigated the data file of the Smurfs game the most, because in 2008 the Smurfs celebrated their 50th anniversary. Calvero 20:32, 1 May 2010 (GMT)
Hmm, well I found a copy of The Smurfs and you're right, iFileCount is equal to the number of files, and revisiting The Lion King that is indeed the case there as well, I think what got me is that you don't need to know those values to read the file. Looks like I have to make some revisions! I think the only way to figure this out for sure is to work backwards, starting at the FAT offset and subtracting the size of each file until you get to the offset of the first file, which will probably be 0x13, but I will check now just to be sure :-) -- Malvineous 00:42, 2 May 2010 (GMT)
Ok, well if I start at the FAT offset and work my way backwards using each file's size, I end up finishing at offset 0x0B, which means your structure above is correct except for BYTE unknown[8], which is actually the first eight bytes of the first file. I've updated the EPF page with this info. -- Malvineous 03:33, 2 May 2010 (GMT)