11-30-2021, 02:16 PM
(11-30-2021, 12:03 PM)JereMiami Wrote:(11-30-2021, 11:12 AM)stamatis Wrote: I have had slight checksum issues when upgrading libraries - i now always keep backups of both older libraries and scripts before any upgrade.
Looking at a current app i'm working with:
The most current version of the LiveCloud library files was released 29 November; the latest version of my existing library files was copied into place on 27 November meaning that mine are now out of date.
However the checksums in the LCM stack script are identical to my existing ones, meaning i too would run into checksum errors if/when upgrading.
I know Mark and the team are very responsive and should have the script updated soon.
In the mean time, you could generate your own checksum to put in the stack script if you trust the source of your download, which i guess you should if directly downloading via LCM - for example to put the checksum into the message box just create a button with the script:
Code:on mouseUp
answer file "Select a file to get it's checksum"
if it is not empty then put base64Encode(md5Digest(url ("binfile:" & it)))
end mouseUp
Use this to get the checksums of the new cdb_header.lib and cdb_starter.lib files and then just put those in your script. This should sort your checksum error issue.
I'll be doing the same
Stam
Thank so much. It worked for me. Very clever!