Freon wrote:Teacups, I am fully aware of what the Ecuflash write checksum is checking. That's exactly why I made my comments.
If you are going to open your ROM in Ecuflash and resave it to fix the checksum, you have completely negated the use of the checksum! It is doing you no good if you use it like that. I don't want people thinking that means they're any more secure doing it that way then if they just disabled it outright. The only thing the file checksum is saving you from is a file corruption from the time you save it in your editor to the time you open it with Ecuflash. That's it. So opening and resaving it in Ecuflash moments before you flash it makes the checksum useless. Might as well just disable it once and never bother with it again. People need to understand this...
Never said it was more secure - merely giving the OP all the different ways to avoid the checksum failure. The bottom line is to avoid the checksum failure. Both ways work - neither is better than the other. You can use the "disable" method that Enginuity uses (or with a hex editor) but this is not any better or worse than Ecuflash automatically updating the checksum when you save. The reason I mentioned using Ecuflash or Enginuity to fix the checksum is because the OP didn't seem to know how to set up the fix in Ecuedit and I wasn't sure either as I don't use Ecuedit (but I've seen a post somewhere about an auto update selection).