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

×
avatar
adamhm: Interesting, I just checked and the files appear to be the same between the classic + new entries for the other two games. It's probably a mistake so it might be worth contacting GOG support about it.
Thanks for ensuring that the download avaiable is outdated for the Classic FO2. I followed your suggestion and sent a ticket to support (let's hope they solve it). Meanwhile I did an installation through Wine without the wrapper, using the dll override and singlecore. It worked nicely! Again, thanks for pointing that and for making the wrappers (I have already used one for STALKER SoC)! That is why I love Linux community!
The support answered my issue:

Cycu93 (GOG.com)

May 17, 16:06 CEST
Hello,

Both versions of the game are nearly identical in content.
Unfortunately, non-classic release is published by Bethesda while now classic version was published by Interplay and we are unable to update classic installers to the latest version.
Could you please rename setup_fallout2_2.1.0.17.exe to setup_fallout2_2.1.0.18.exe and see if the script launches?
Please keep in mind that the game is only compatible with Windows(classic is compatible with Windows and Mac).
I apologise for inconvenience.

Regards,
Cycu,
GOG.com Support

---

tokisto

I was worried if the versions would be different (some patch or bug fix). I have tried to just rename the files, which did not work. I am aware there is no support for Linux, but this problem with the wrapper raised my attention to a possible outdated version. Since you say they are not different, I am fine with that. I do understand that they are supplied by different companies (Interṕlay and Bethesda). Nonetheless, I already figured a way to make the Classic version work properly with the mod and in a way that I was looking for. Again, I just was 'afraid' that the classic version would be crippled and/or outdated. Thanks for your attention and support.
avatar
tokisto: I was worried if the versions would be different (some patch or bug fix). I have tried to just rename the files, which did not work.
In addition to renaming the installer, you should comment the lines 90 to 92 in the 'fallout2_wine.sh' script.

-----

EDIT: This is not needed anymore, as adamhm updated the scripts to detect the classic version of the installers.
Post edited May 19, 2017 by vv221
avatar
tokisto: <snip>
Interesting, I was under the impression that they were supposed to be identical (although at a glance their contents do appear to be identical except for some GOG-specific files being renamed in the "classic" versions). Anyway I've now updated the build scripts to accept the classic installers as well.
Hi adamhm and thanks for your work!

Unfortunately, something went wrong during my installation. I followed all your instructions. At the end, I have a script called start.sh and I am able to use the script to create a shortcut for Fallout 2. But when I run the shortcut nothing happens. When I run the script again and choose "play" nothing happens again. The attached picture shows the message I get in the command line. Do you have any suggestions?
Attachments:
It looks like you're missing one or more of Wine's dependencies. Did you install the recommended packages as well when installing Wine?
Hi! I recently came across your wrappers from a comment you posted on gamingonlinux. Awesome work, looks like I'll finally get to play Fallout.

While Fallout 2 installed smoothly, I had some trouble when instaling Fallout 1. Looks like the sha256sum in the install script didn't match the file I download. After redownloading a few times I decided to try modifying the script and it worked (at the game installs and launches; haven't played yet).
The checksum I got is be9dd4025ef34117ddfb4fe8a015320b29c0fc9da33d9f0fa3dbcb1a844c7cb9.
avatar
Werzaz: While Fallout 2 installed smoothly, I had some trouble when instaling Fallout 1. Looks like the sha256sum in the install script didn't match the file I download. After redownloading a few times I decided to try modifying the script and it worked (at the game installs and launches; haven't played yet).
The checksum I got is be9dd4025ef34117ddfb4fe8a015320b29c0fc9da33d9f0fa3dbcb1a844c7cb9.
There are two versions of Fallout - one is the "classic" Interplay release and the other is the Bethesda re-release, both with identical filenames. If you have the "classic" version (the checksum you've provided indicates that you're using this version) run the fallout_classic_wine.sh script, otherwise use the fallout_wine.sh script
Post edited June 12, 2018 by adamhm
avatar
adamhm: There are two versions of Fallout - one is the "classic" Interplay release and the other is the Bethesda re-release, both with identical filenames. If you have the "classic" version (the checksum you've provided indicates that you're using this version) run the fallout_classic_wine.sh script, otherwise use the fallout_wine.sh script
Ah, I see. Totally missed that there two scripts. Shouldn't do stuff like that so late in the evening.
Did you get Fallout 2 Restoration Project working with your installation?

Edit:
Never mind, I get it to work already.
Post edited September 27, 2018 by melighos