35s program checksums

[MarkHaysHarris777]

(01-21-2015 11:12 PM)Mark Hardman Wrote:  35s checksum problem

I keyed the example from above, and I get the checksums of the original author:
LBL G
1.4
LBL C
1.4

LBL G, LN= 9, CK= D23F
LBL C, LN= 9, CK= 18BC

These are consistent, and I cannot get them to change. I do notice another thing though... there are no RTN instructions. This problem may have to do with the branching calculation offset problem (which I do see often) because it can't figure out exactly which instructions to include in the checksum?
In my coding I always use labels, keep the labels in order, and make sure the GTO XEQ instructions don't change on editing. My checksums don't change.
The other thing I am wondering about is the build date. My unit was built in late november 2014. It still shows revision 0 2007--- but I'm wondering if they have made some subtle changes reflected in the new units, but forgot to bump up the revision level. (not likely)
Another thing that may affect this is that I reserve 101 indirect memories, which changes where the program code is located, which might make a difference on how the checksum is calculated.
By the way, my equation checksums and lengths are also very consistent. I have another HP35s on order for the purpose of cross development and experimentation; maybe I can get to the bottom of it.

Sorry about the font... I'm gonna blame my browser... the editing options are apparently not cooperating for me between my browsers. Hopefully this is better.

Thanks for the heads up! Nice to meet you Mark; have a great day.