QUOTE(hwnd @ Jul 7 2006, 08:35 AM)

- Does the data from default.xbe (offset: 0x5B8AA8, len: 0x34) that's placed in installmarker1 and installmarker2 (offset: 0x3AAC, len: 0x34) play any role in validating the .CA2 files?
I didn't spend any time figuring out the installmarker stuff.
QUOTE(hwnd @ Jul 7 2006, 08:35 AM)

- CARS.CA2 and MEGA.CA2 each contain individually compressed segments of the CAB that need to be reconstructed to extract the contents; do the number, size, and offsets of the compressed segments need to be identical to the original when they are reinserted?
No, but they need to be correct. And the pointer or whatever it is (the value which is 0x0 for the first file and 0xfffffff or something for the last) in the inode needs to be identical as far as i know. What this means, is that I haven't made any progress to actually add cars to the game.
QUOTE(hwnd @ Jul 7 2006, 08:35 AM)

- Does DEFAULT.XBE need to be modified to load the updated .CA2 files?
You can hack the default.xbe to disregard the checksum, or you can crack the checksum and sign it yourself (which is the method I prefer).
If you look closely at the files, there is some bits between the filenames and the dnodes.
Happy hacking (IMG:
style_emoticons/default/smile.gif)
And btw. cabextractor is flawed, so I suggest you write your own, if you want anything to actually work.