It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
The current installer script on GNU/Linux is not executable on GNU/Linux and i can't tell that to Aren personally because the Tasharen server doesn't allow older game versions.
can other Debian/buntu/mint users please confirm this?
if any of you visit the tasharen server often can you please tell a dev-admin?


the error is:
Verifying archive integrity...Error in MD5 checksums: 7c0ec1c4e503d27c823611c74ad42206 is different from 083f467f5405321afc1e7c0da5a4193e

i tried downloading it with lgogdownloader and firefox a few times. faking the checksum didn't work either (and should never be done for security reasons).
i wouldn't mind if the game would get as many updates as before that problem occurred but this is not the case.
No posts in this topic were marked as the solution yet. If you can help, add your reply
This Issue persists even after I was told it was gonna be fixed. For anyone on GNU/Linux thinking about buying this game, wait until the next update is out, currently it is uninstallable.
avatar
Holzider: This Issue persists even after I was told it was gonna be fixed. For anyone on GNU/Linux thinking about buying this game, wait until the next update is out, currently it is uninstallable.
I am having the same issue with build 2.35.0.38 under Linux Mint 18. It says "Error in MD5 checksums: 7c0ec1c4e503d27c823611c74ad42206 is different from 083f467f5405321afc1e7c0da5a4193e".
avatar
ARC_Curunir: I am having the same issue with build 2.35.0.38 under Linux Mint 18. It says "Error in MD5 checksums: 7c0ec1c4e503d27c823611c74ad42206 is different from 083f467f5405321afc1e7c0da5a4193e".
What's the md5sum of the installer.sh file itself, e.g.$ md5sum --tag gog_windward_2.0.0.1.sh? Try downloading it again and see if it's any different from the first time. Otherwise, contact Support.
avatar
ARC_Curunir: I am having the same issue with build 2.35.0.38 under Linux Mint 18. It says "Error in MD5 checksums: 7c0ec1c4e503d27c823611c74ad42206 is different from 083f467f5405321afc1e7c0da5a4193e".
avatar
Gydion: What's the md5sum of the installer.sh file itself, e.g.$ md5sum --tag gog_windward_2.0.0.1.sh? Try downloading it again and see if it's any different from the first time. Otherwise, contact Support.
the md5sum for the installer is ee50588286bbbd24cb6ee5db476a3610 . the support told me they were gonna fix it some time ago but it is still the same file. maybe they just forgot.
Post edited August 09, 2016 by Holzider
avatar
Holzider: the md5sum for the installer is ee50588286bbbd24cb6ee5db476a3610 . the support told me they were gonna fix it some time ago but it is still the same file. maybe they just forgot.
I would shoot them another email about it. It's certainly been long enough. Is this with the German version? That is presuming the installer doesn't contain all the languages.

You can actually extract the installers:
$ unzip installer.sh
Though if the GOG upload itself is corrupt that very well may be incomplete or just not work.
avatar
Holzider: the md5sum for the installer is ee50588286bbbd24cb6ee5db476a3610 . the support told me they were gonna fix it some time ago but it is still the same file. maybe they just forgot.
avatar
Gydion: I would shoot them another email about it. It's certainly been long enough. Is this with the German version? That is presuming the installer doesn't contain all the languages.

You can actually extract the installers:

$ unzip installer.sh
avatar
Gydion: Though if the GOG upload itself is corrupt that very well may be incomplete or just not work.
nope, it"s corrupt.
"~$ > unzip gog_windward_2.35.0.38.sh
Archive: gog_windward_2.35.0.38.sh
warning [gog_windward_2.35.0.38.sh]: 642758 extra bytes at beginning or within zipfile
(attempting to process anyway)
error [gog_windward_2.35.0.38.sh]: start of central directory not found;
zipfile corrupt.
(please check that you have transferred or created the zipfile in the
appropriate BINARY mode and that you have compiled UnZip properly)"
Looks like it is resolved now, thanks.