Posted January 08, 2015

For example:
1. Using the Duke Nukem 3D data files on Windows but with the massively enhanced EDuke32 engine rather than the original one.
2. Playing ScummVM-compatible games on Android
3. Unpacking a DOSBox-wrapped game so it can be used with a native Linux or MacOS version of DOSBox without waiting for GOG to renegotiate the list of platforms they're allowed to release it for.
Under those circumstances, the installer's insistence on a working install is detrimental because we have to do the install, copy the files we actually want out, and then immediately uninstall.
Also, that assumes that the GOG installer will actually run. Microsoft has made noises about dropping 32-bit compatibility in Windows 9 but Wine on OSX can't run 64-bit Windows apps because Win64 and 64-bit OSX have different, incompatible rules for which processor registers are clobbered in a context switch.
(And, for many early 32-bit Windows apps, the only reason their original installers work on modern Windows is that Windows detects 16-bit InstallShield launcher stubs and transparently swaps in 32-bit replacements that they got a license to bundle with Windows.)


Have GOG.com Team noticed it? They haven't mentioned it (and checking the thread - haven't yet made a post there). Maybe they can make it the Official Suggestions Thread then? And raise more awareness of it (including through their posts)? The thread was active just 4 days.
Post edited January 08, 2015 by ssokolow