DAT (Ever17): Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 31: | Line 31: | ||
2014/07/10 Currently looking into this with a dissembler and debugger. Found the sub-routine the is changing these bytes. It takes 1 byte number (depending on how you interrupt this), and subtracts it from the number at a specific location, between 4352 to 4608, in the JPG file that came from the archive that is loaded in memory. Once it does the operation on all 256 bytes, it will then write the file to disk. | 2014/07/10 Currently looking into this with a dissembler and debugger. Found the sub-routine the is changing these bytes. It takes 1 byte number (depending on how you interrupt this), and subtracts it from the number at a specific location, between 4352 to 4608, in the JPG file that came from the archive that is loaded in memory. Once it does the operation on all 256 bytes, it will then write the file to disk. | ||
Revision as of 08:01, 11 July 2014
Seen/used in the follow game(s):
- Ever17
Structure
| Header | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Size | Content | Description | ||||||||||||
| 4Bytes | Magic/ID | |||||||||||||
| 4Bytes | File Count | |||||||||||||
| 8Bytes | 0x00 Filler | |||||||||||||
| Index | ||||||||||||||
| Size | Content | Description | ||||||||||||
| 4Bytes | Offset | Starts from zero. | ||||||||||||
| 4Bytes | File Size | Stored value is actual size doubled | ||||||||||||
| 24Bytes | File name | |||||||||||||
Notes for 'wallpaper.dat' Extracting images straight from the container file will produce broken images. There is nothing wrong with the extraction process but rather the files themselves. Starting from offset 4352 and ending at 4608 in every single JPG, this 256 byte has been modified in some way.
2014/07/10 Currently looking into this with a dissembler and debugger. Found the sub-routine the is changing these bytes. It takes 1 byte number (depending on how you interrupt this), and subtracts it from the number at a specific location, between 4352 to 4608, in the JPG file that came from the archive that is loaded in memory. Once it does the operation on all 256 bytes, it will then write the file to disk.