check sum calculator

[Dave Zug]

would cause the prom to code. 52 I think. (bad CAL)

It may correct the CS,  but if the BIN that was LOADED had a bad CS, the
software may notify you of this (GME) or maybe refuse to load it <?>

If the package has an option for "mark experimental" then the checksum will
never fail, even if the chip really does have a checksum problem. good and
bad.

Look at the FTP docs for your cal if it exists, find the location of the
cksum and set it experimental if the package you have wont support it.

you can use your hex editor to calculate the cksum in some cases.

anyone got a handy program to enter start, and end byte, and chsum byte
location and "fix" a cksum? seems simple nuff and useful mebbe?


----- Original Message -----
From: Kevin R <KEReyn at gte.net>
To: GM ECM mailing list <gmecm at diy-efi.org>
Sent: Thursday, November 09, 2000 7:05 PM
Subject: check sum calculator


> In reading about the winbin updates I have what is probably a very basic
> question.
> If I load a stock bin and change something in winbin(old version) and then
> burn it to run in the car, can I assume the checksum will be wrong. What
> would this cause?
> Also I've been playing back and forth between winbin,TC, and a couple of
hex
> editors. Each offers it's own +s and -s. I believe TC already calculates
the
> CS.  If I changed a few items in winbin(that aren't listed in TC) or with
> and editor, then change say fuel table s or spark in TC would it correct
the
> CS?
>
> Kevin R
>
> --------------------------------------------------------------------------
--
> To unsubscribe from gmecm, send "unsubscribe gmecm" (without the quotes)
> in the body of a message (not the subject) to majordomo at lists.diy-efi.org
>
>

----------------------------------------------------------------------------
To unsubscribe from gmecm, send "unsubscribe gmecm" (without the quotes)
in the body of a message (not the subject) to majordomo at lists.diy-efi.org