OK, thank you for the explanation (and thanks to @dtgreene too). For the script, i don't really know... Goes to /proc directory and displays the kmem file before exiting ?

But here's the important thing : i've finally managed to install the game, using a weird trick. As said, i have a few installer files because i have downloaded it several times. Each installer has its own crash time. I began the install with one, and when it crashed, i made a copy of every single file installed so when the crashing installer erased them, i could put them back in their directory. Then i run the second installer and told him to never overwrite files. So it installed the files coming after the files installed. Then it crashed, so copy/paste, then run the 1st intaller until it crashes, rinse and repeat until the game's fully installed. And it works !! Had a lot of crashes at the beginning, but setting down the graphics options seemed to make it good.

But it might be the longer install i ever done !

No, it doesn't actually do that.

You see, the first line of the script is
#!/bin/cat

This line of the script is telling the kernel that the script is to be interpreted by the cat program. Therefore, when you try to execute it (via a command like "./script.sh" after setting the executable bit), the kernel will run the cat program on the script, which will just output the script without executing the commands in it.

So, the actual output of this script, when executed, is the same as the script. Or, in other words, the output is and it will exit successfully (despite the "exit 1" command).

Now, if you instead explicitly run it through the shell (like with "bash script.sh"), then it will try to display the /proc/kmem file, and will likely display an error message before ending in failure.

So are you trying to say that using that method we, or preferrably GOG, could force an installer to use bash instead of whatever else happens to come as standard on our distro?

I am pretty lost when it comes to programming.

Yes, that can be done with the first line, which is called the shebang. One just needs to put the proper path to the executable.

(Of course, said interpreter needs to exist on the system; if bash is not already installed, a script that specifies bash is not going to work.)

In any case, my example demonstrates that any program can be made to act as the interpreter, though admittedly this is only useful with some programs.

I'm glad you've managed to install the game. Enjoy it! I still wonder where these installer crashes come from.

When you still have these installer files, do their md5 sums differ?

Good idea. They're different... So even if the installer says the archive's ok, it's not necessarily true.

That's bad to hear. But at least it seems to be clear that corrupted installers were causing the problems.

It is. I'll try to make the info reach GOG's support.