Thanks! OK. This appears to have worked> .\fciv.exe -sha1 .\chirp-daily-20191123-installer.exe // // File Checksum Integrity Verifier version 2.05. // 35d7819e52f7e5e0547e63f14d893146acae900d .\chirp-daily-20191123-installer.exe
On Sun, Nov 24, 2019 at 2:27 AM Peter Lambert <[email protected]> wrote: > That output from Microsoft File Checksum Integrity Verifier is too short > to be an SHA1 hash. It's actually the MD5 hash for the file and is also > correct. > > On Windows I am using HashCheck Shell Extension which is far more useful: > > https://github.com/gurnec/HashCheck > > HTH... > > On 11/23/2019 11:55 PM, Benjamin Denio wrote: > > .\fciv.exe .\chirp-daily-20191123-installer.exe > // > // File Checksum Integrity Verifier version 2.05. > // > 66e28f7e024b40f8b9cf08fa8400c373 .\chirp-daily-20191123-installer.exe > > but posted hash says it should be: > > 35d7819e52f7e5e0547e63f14d893146acae900d chirp-daily-20191123-installer.exe > > > > _______________________________________________ > chirp_users mailing > [email protected]http://intrepid.danplanet.com/mailman/listinfo/chirp_users > This message was sent to Peter KM6WXN at [email protected] > To unsubscribe, send an email to > [email protected] > > > _______________________________________________ > chirp_users mailing list > [email protected] > http://intrepid.danplanet.com/mailman/listinfo/chirp_users > This message was sent to Benjamin William Denio at [email protected] > To unsubscribe, send an email to > [email protected]
_______________________________________________ chirp_users mailing list [email protected] http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to [email protected] at [email protected] To unsubscribe, send an email to [email protected]
