Originally Posted by
steveo
ok i've had a quick review and i agree that it's totally safe, if you know your bin hasn't been customized by any crazy patches that we don't know about, that you can just unset the 'verify patch regions against reference' parameter. that'll allow the thing to install.
the reason i do a strict compare by default is i'm fearful that someone else will try to upload a bin that has been customized in an unknown way, and our 'recovery' patch will somehow cause that bin to be unbootable or not enter programming mode. for that purpose it compares the comms code against a stock f-body bin.
i'll work on a workaround that allows it to work as designed while still protecting against such things. i thought for sure i had checked against eehack's patches but i guess thinking back, i never got around to doing that properly.....
by the way the new EEX xdf does have those eehack patches in it, so if you want speed logging or whatever in eehack in the future, that's how you get it.