Ah, I was wandering when this would come up, yes and no is the answer. Yes in that it throws up a fault code, but no it doesn't seem to have any adverse effects. I have managed to get TunerPro to generate a checksum for the whole EEPROM, but this is wrong. I.e. I cant get it to match an original map. I can only assume that there is multiple checksums, one for the code and one for the map data, at some stage I will get round to finding the EEPROM ranges for each checksum and post my findings. That is of course if anyone else doesn't beat me to it. This is only a side project of mine so I don't