Thread: calibre 1.39.0 (Win32) - bad installer file?
View Single Post
Old 05-29-2014, 09:25 AM   #3
theducks
Well trained by Cats
theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.
 
theducks's Avatar
 
Posts: 31,104
Karma: 60406498
Join Date: Aug 2009
Location: The Central Coast of California
Device: Kobo Libra2,Kobo Aura2v1, K4NT(Fixed: New Bat.), Galaxy Tab A
Quote:
Originally Posted by Clovis Man View Post
Tonight I downloaded version 1.39.0 (Win32) from the main download page. When I tried to install this package, msiexec reported (paraphrased) an 'invalid installer file". The copy I downloaded from the alternate site worked as advertised.

The files carried the same name (calibre-1.39.0.msi) and were of identical size (56,011,264 bytes), but the SHA1 signatures were different.
5AED1344D85E22E269E731C2A4A6C41902DFDC3F calibre-1.39.0.msi.good
8BC0D73A7B32B7C55F131496630280F46D1FB15D calibre-1.39.0.msi.bad
(The ".bad" and ".good" extensions are my additions.)

It's possible, but extremely unlikely (almost a first, IIRC), that the bad copy got mangled in transit. Still, it would be a good idea to check the integrity of the copy hosted on the main site.
Kovid reissued 39 because of a wireless device issue. You may have simply gotten into the transition
theducks is offline   Reply With Quote