Post Reply 
HP 35s Checksum explained
02-09-2015, 12:21 PM
Post: #3
RE: HP 35s Checksum explained
Awesome! Thanks for working this out. I suspect the problem is that the bytes in a program are not position independent. In other words, the same program might contain different bytes depending on where it's located in memory. This would be true if, for example, a goto contains the address of the target instruction.
Find all posts by this user
Quote this message in a reply
Post Reply 


Messages In This Thread
HP 35s Checksum explained - Tugdual - 02-08-2015, 05:43 PM
RE: HP 35s Checksum explained - Tugdual - 02-09-2015, 09:20 AM
RE: HP 35s Checksum explained - Gerald H - 02-09-2015, 12:57 PM
RE: HP 35s Checksum explained - David Hayden - 02-09-2015 12:21 PM
RE: HP 35s Checksum explained - Tugdual - 02-09-2015, 04:07 PM
RE: HP 35s Checksum explained - Tugdual - 02-09-2015, 04:42 PM
RE: HP 35s Checksum explained - Tugdual - 02-09-2015, 10:36 PM
RE: HP 35s Checksum explained - Tugdual - 02-10-2015, 01:53 PM
RE: HP 35s Checksum explained - Paul Dale - 02-14-2015, 08:44 AM
RE: HP 35s Checksum explained - Tugdual - 02-14-2015, 08:57 AM
RE: HP 35s Checksum explained - Tugdual - 02-11-2015, 06:55 PM
RE: HP 35s Checksum explained - Tugdual - 02-11-2015, 08:45 PM
RE: HP 35s Checksum explained - Tugdual - 02-14-2015, 08:38 AM



User(s) browsing this thread: 1 Guest(s)