VATS confusion

[hatchssv8]

Need some clarification on switching VATS of (ie Disabling VATS in selected bin)
I did a search and could not find out where I am going wrong, mind you I have successfully done it previously but that was about 2 years ago

so...... for a VS V8 Auto
I am reading stock holden bin BWFU0810 (downloaded from this site) with XDF $83 in TP5
KKKPGMID Prog ID is 83,,,,I change this to AA and save
KOPTFLG4 Bit 0 is SET (set box ticked)
I then save as BWFU0810 no VATS.bin
Then I burn to a EEPROM SST27SF512 with no offset

Have I disabled VATS???????

My brain feels like mush. Any help with this is much appreciated.

Thanks in advance

[The1]

yes just have to change the flag to disable vats.

Attached maybe a newer xdf than what you have by the sounds

[hatchssv8]

ok I will also use the xdf you attached (the file I am using is 83HoldenVS_V8_v2 (mask $83).xdf)

So I need to uncheck the box? (no tick means VATS disabled)

Gee I must sound so stupid

[The1]

that's correct if it's ticked untick it

[hatchssv8]

Cheers The1.

Many thanks.

[hatchssv8]

ok. did the change as described above.

so as a sanity check, I load both the original bin and the modified bin in TP5 compare
I run the difference tool and there are many changes. Not just two

Shouldn't there only be two differences?

[VL400]

You should get the two bytes you changed plus, depending on the XDF, it may have tried to update two other checksum bytes - it will get the calc wrong but setting program ID to AA fixes that problem. So should have only 2 or 4 bytes different.

[hatchssv8]

Thanks for the feedback so far.

I have redone this a few times and I am now only getting four bytes difference.

I only need clarification on the VATS checkbox
TP title = KOPTFLG4: Option Word 4 - Bit 0 - Bit 0
TP desc = Bit 0 1 = Disable anti-theft module control

So, if the checkbox is ticked, is the VATS disabled?
If so, then unticked= VATS enabled and ticked= VATS disabled

I am not disagreeing with The1 where he says to untick the checkbox, it just doesn't agree with the TP description.

Oh, as this is a VS V8 Auto bin @ 64k written originally on a 128k chip, I should file offset by 8000 as I am writing to a 512k?

Is there a table available which can be referenced with regard to file offsetting and stacking when burning chips?

Thanks again

[antus]

try whats in the description, it should be the opposite to how its set in the stock bin.

512k for an eprom is 512kbit, and there is 8 bits in a byte. so 512/8=64kbyte. So to put a 64k file on it there should be no offset. to calculate offsets, make sure all the numbers you have are in bytes and then subtract the bin size from the size of the storage. That is your offset and will position the bin so that it is aligned with the end of the chip, rather than the start.

[hatchssv8]

crystal clear antus.
thanks