The forum

[script] GOG.com - The Blackwell Epiphany

Gog installer gives runtime errors I can't find the cause of?

Author Replies
Okto Friday 14 November 2014 at 17:20
OktoAnonymous

The script actually works, the game installs and runs fine. However, right at the end of the gog installer, it creates three runtime errors. "Runtime error (at 56:445)" once, and then "Runtime error (at 186:799)" twice.

I'm finding similar problems with some other gog installers giving runtime errors right at the end, then finding the game is otherwise ok and playable. I've tried installing the visual basic and C++ redistributables before the gog installer launches, and several versions of wine, but nothing has changed.

Any ideas appreciated!

 #!/bin/bash
# Date : (2014-11-09 19-30)
# Wine version used : 1.6.2
# Distribution used to test : OpenSuse 13.2
# Author : Benjamin Hardy

[ "$PLAYONLINUX" = "" ] && exit 0
source "$PLAYONLINUX/lib/sources"
 
TITLE="GOG.com - The Blackwell Epiphany"
PREFIX="blackwell_epiphany"
WORKING_WINE_VERSION="1.6.2"
SHORTCUT_NAME="The Blackwell Epiphany"
GOGID="blackwell_epiphany_the"

POL_SetupWindow_Init
POL_Debug_Init

POL_SetupWindow_presentation "$TITLE" "Wadjet Eye Games" "http://www.gog.com/gamecard/$GOGID" "Benjamin Hardy" "$PREFIX" 

POL_Call POL_GoG_setup "$GOGID" "2b8f160c00c8de5ce316dbaa09bdb366"

POL_Wine_SelectPrefix "$PREFIX"
POL_Wine_PrefixCreate "$WORKING_WINE_VERSION"

POL_Call POL_GoG_install

POL_Wine_reboot

POL_Shortcut "epiphany.exe" "$SHORTCUT_NAME" "" "" "Game;AdventureGame;"

POL_SetupWindow_Close
 
exit 0

Edited by Okto

ghoust Friday 21 November 2014 at 13:55
ghoustAnonymous

How about /nogui option? (POL_Call POL_GoG_install /nogui)
Okto Sunday 23 November 2014 at 16:25
OktoAnonymous

How about /nogui option? (POL_Call POL_GoG_install /nogui)

Hi ghoust, thank you for your reply. I have tried this, but it caused different runtime errors. Actually more of them, and sooner! I know it has worked for others with similar problems though, so I will keep it in mind for the future.

I now think it's the gameux dll (or something it uses). The runtime errors coincide with messages relating to it. Swapping between the built in and native version does also change the runtime errors. As far as I can tell, gameux isn't at all important in this case however. So, I'm going to upload the installer later and add these runtime errors as a known issue in the description.

Edited by Okto

petch Sunday 23 November 2014 at 21:12
petch
Developer

Hi,

I noticed problems with some recent (2.1.x ?) GOG installers too, I asked GOG support about their policy for Wine compatibility of their Windows installers some days ago, still waiting for the reply.

The gameux.dll hypothesis is interesting, maybe something can be done there...

Okto Sunday 23 November 2014 at 22:10
OktoAnonymous

Hi,

I noticed problems with some recent (2.1.x ?) GOG installers too, I asked GOG support about their policy for Wine compatibility of their Windows installers some days ago, still waiting for the reply.

The gameux.dll hypothesis is interesting, maybe something can be done there...

Hi Petch, thank you for your reply. gameux.dll is my best idea at the moment, but it's hard to be sure right now. However, as well as the earlier observations, I find it likely that the gog installer would update Windows game explorer right at the end of the installation, explaining these runtime errors all happening at that time. It would also account for them seemingly not affecting the installation. These two behaviours have always been the case for me so far.
petch Sunday 23 November 2014 at 23:06
petch
Developer

I shall add

POL_Wine_OverrideDLL "" "gameux"
to my test script and see if it makes any difference...