So, today my newbie self embarked on creating an XDF using Tunerpro for my 06A906032HS file using a WinOLS definition and alt-tabbing back and forth between the two programs and entering the information as I went. Everything went fine until I took a break and came back to see that the values for my x and y-axis were wrong. I noticed that the "address step" had reverted back to -4. I changed it again, saved my XDF, and closed/reopened the program only to find that my changes aren't being saved.

I already tried filling out the bin size in the header (100000 is 1024kb in hex, right?) as suggested for other people with the same problem, but alas, no joy. I've searched high and low for a solution, but haven't come up with anything.

I'm attaching my .bin and the .xdf I'm working on in case someone needs it in order to figure out the problem. Thanks a ton in advance!

Also, I'm hoping this is the appropriate area to post this. If not, I apologize.

I'm still hunting around for a solution to this issue, but haven't found anything yet. However, I'm wondering if my problems are caused by the fact that I haven't entered any checksum information into the XDF header.

How does one find the proper checksums needed for an XDF? Again, I'm newbie here, and I'm learning a lot about everything still, but haven't found much info on finding checksums. All I can find are utilities to verify they are correct or to generate md5 checksums, which I don't think are used in the header (please please correct me if I'm wrong).