timppu: Do the installers you downloaded first have the "(g)" in the filename, meaning they are the Galaxy-embedded versions?
PetrusOctavianus: Yes.
Do you still see this issue, or does it seem "fixed"? As I mentioned, at least I don't see the same problem on the BG EE download page (with the latest Windows Firefox).
EDIT: Ok I see this is being investigated already with e.g. JMich.
madth3: Should GOG offer an installer without absolutely any trace of Galaxy?
I'd like but I never expected it based on their communications.
I couldn't care less, as long as this "trace of Galaxy" doesn't increase the size of the installers a lot (like the embedded Galaxy-installer does), and does not affect the usage of the installer without Galaxy. My main concern with the Galaxy-embedded installers all along has been the increased size, extra 120MB per game, not cool. Plus, how are they going to keep all those embedded Galaxy installers up to date, ie. will they keep changing all the game installers every time the Galaxy client receives an update, or what? (that would trigger e.g. gogrepo.py to redownload all those installers, all over again, as it detects they have changed).
If these small Galaxy stuff (dll?) in the current classic installer is stuff that e.g. makes it easier to import one's installed GOG games to Galaxy, then I can fully understand why GOG wants to make their offline installers Galaxy-compatible in that way. I recall seeing complaints in the forums why Galaxy import doesn't detect the installed GOG games, so I presume these "Galaxy changes" are related to those.
Who knows, I might need to use it at some point as well, e.g. I've been playing the single-player part of some game without Galaxy, but then decide I want to try the online multiplayer part of it as well (which needs Galaxy). I certainly would hope that Galaxy would detect that game at that point.
