![]() ![]() ![]() This is a single block, and padded at the end # padding 16 << this is what i should have used Goto 0x20 # This skips to the end padding I don't read the last because I don't know what it is. Get EOH long # Then I read 3 of the 4 integers which follow. ![]() Ok, at least this is clear now.Ĭode: Select all idstring "RTDP" # The identifier (quickBMS will close if the first 4 bytes aren't "RTDF") Looks more like a school lesson now.ĮDIT: Ah, I found out about the 32 I thought its hex but its not. Where does the 0x55 comes from and (question to chrrox) how do you found out that the data is xored? Does filexor xors everything behind a given offset? Why is the FILEOFFSET = FILEOFFSET + EOH? What I don't understand is how we get to the offsets of the FILESIZE? Jumping to 0x20 and adding 32 bytes is a way to far. Looking at the btl_auto_demo.vol for example I guess the FILESIZE should be 389152byte for the first and 19488byte for the second file and right after that there is the FILEOFFSET. I got that much: You get the FILENAME with "getdstring FILENAME 32" but what does the 32 stands for (a 32 bytes string)? After that you get FILESIZE and FILEOFFSET. Thanks for the fast reply everyone Looks like I dont put enough thought in to this.Ĭould you explain the BMS-script a bit WRS, please?
0 Comments
Leave a Reply. |