Can you unpack the game with innoextract and use it without the installer altogether? That can bypass all the clutter installation.

Yes I can, but what do I do with the .bin files? Just "run" them one after the other?

No, innoextract unpacks all the files from the archive. All those .bin are part of it. Run it like this: While all the .bin are in the same directory. That would unpack everything.

For more details, see

Okay, innoextract dumps 2 Folders. /app and /tmp. /app includes one dll and s .ico, while /tmp contains a lot of .pngs and .txts for the gog installer. Nothing else was extracted.

Forget that, the GOG installer seems to be running fine now...

/tmp can be ignored.

Does "/app" have any subdirectories? What version of innoextract did you use?

Version is 1.4 (in the AUR of Archlinux), both have no subdirectories. Its like it doesn' know that the .bin files are their. But the GOG installer finds them (they're in the same directory).

The GOG installer now almost completes before it wants to install the framework (before that was after one third). Then, the framework installer almost finishes before detecting a error (Runtime error) and the GOG setup then says "Invalid Opcode".

Now, after the install I can "start" the game, but it only opens a window, which is my frozen desktop. But I can alt-tab away from that and the cursor switches to game cursor and back :D

That's strange. May be GOG started using a different version of installer recently? What is the version in the game instalelr file name? Before it was something like 2.0.

You can report this bug to the innoextract bug tracker: https://github.com/dscharrer/innoextract/issues

Files are:
setup_divinity_original_sin_2.5.0.11.exe
setup_divinity_original_sin_2.5.0.11-1.bin
setup_divinity_original_sin_2.5.0.11-2.bin
setup_divinity_original_sin_2.5.0.11-3.bin

Not sure, sometimes that version is just random. But 2.5 sounds like a newer installer than usual. Reporting that to innoextract project would be useful.

The game doesn't need net. That is for the editor i think. Just let it install until the end (if, in fact you can, there was a Gog installshield bug that was recently fixed in wine that required a source patch to work around, but it was only cosmetic - the ui appeared to freeze, but you could wait until you saw that nothing was being written to disc and force close the installer).

Yes, regardless of this other bug, the installer will fail to install net, directx and possibly vcrun2008. But it doesn't matter. Just install it, maybe force terminate, or 'cancel' directx, vrun etc popups. Then install the patches (needs functional registry). Then move the game folder outside of the prefix, delete the prefix (to remove all the crap that may prevent things running), then use

winetricks vrun2008 d3dx9_36

Then start the game (make sure that your charset is en(US) if it freezes at the start).

And it works. You might want to use a custom prefix so that the foreign dlls you just imported with winetricks don't break other applications you run. Or maybe, just because you have things installed already and i just told you to delete the prefix. Just check the wine wiki howto. Also, if you do this, use the WINEPREFIX=~/yourprefix for winetricks too obviously.

PlayOnLinux is good for managing Wine prefixes. It's quite helpful. I simply install each game in its own prefix with PlayOnLinux which makes deleting them quite easy (just delete the whole prefix and that's it).

I don't need to use paid services for making scripts since it's really easy, here let me make you a complete 'DOS run after install' script

export WINEPREFIX=$HOME/.local/share/wineprefixes/DOS
mkdir -p "$WINEPREFIX"
SCRIPT_DIR=$(dirname "$(readlink -f "$0")") #script is one dir above the DOS directory
cd "$SCRIPT_DIR/DOS/Shipping"
winetricks vcrun2008 d3dx9_36
wine EoCApp.exe

Happily, DOS is not like the older Larian games that required physx, where to make the game portable you needed to hack around the physx libraries since they installed systemwide on another directory than the game and depend on a registry entry for dll loading (horrid).
The only nit is that you might want to save the registry entries and apply them in the script too (for patches to continue working even if you delete the prefix where you installed or move the game dir around, because GoG is rather dumb about patches).

Oh and change the keymap if you're hit by that hang bug at startup. I don't know how to do that from the command line because frankly, i'm just changing it from the gnome top bar for now, maybe patches will fix it.

PlayOnLinux is a free software project, and they don't charge for using it. Without it you are bound to either install Wine manually, or to using distro packaged version which can be updated very rarely.