I have been comparing locations between 12587603 and 12592618. I found the parameters I wanted to change in 12592618. I modified the 12587603 XDF for the new parameter memory locations in 12592618. Are the checksums the same between versions or do I need to find the new checksum locations is 12592618 to modify the XDF?
If I need to modify the checksum definitions from 12587603 to match 12592618, is there information out there about calculating the checksums for the segments? Thanks.
Checksum locations and various OS XDFs
-
- Posts: 583
- Joined: Thu Feb 13, 2020 11:32 pm
- cars: Mainly GM trucks, a Cruze and an Equinox for dailys..
Re: Checksum locations and various OS XDFs
Have you tried using the universal patcher yet???
https://github.com/joukoy/UniversalPatcher you can see what the checksums are, change the file and then look at the checksums again..
https://github.com/joukoy/UniversalPatcher you can see what the checksums are, change the file and then look at the checksums again..
Re: Checksum locations and various OS XDFs
Deleted
Last edited by ColPaul on Thu Jun 11, 2020 9:58 am, edited 1 time in total.
Re: Checksum locations and various OS XDFs
I love learning. I didn't get an answer so I'll answer myself in case anyone else has the same questions.
I didn't use the universal patcher but I did learn that the checksum location and ranges are included in the P59 binaries starting around 0x500. Attached are the specifics values for 12592618 but evidently the locations are the same for all P59's. Pulled the data from Ghidra.
I didn't use the universal patcher but I did learn that the checksum location and ranges are included in the P59 binaries starting around 0x500. Attached are the specifics values for 12592618 but evidently the locations are the same for all P59's. Pulled the data from Ghidra.