melmovano: Ok I've tried with flushing DNS.
Results:
- Adapter OFF ==> Game won't start, oblivion.exe starts and starts rundll32.exe, but only the launcher appears, clicking play presumably launches the game, but the only thing which happens is that the rundll32.exe causes 50 % CPU, nothing else
- Adapter ON but router off ==> Same as before
- Adapter ON, connected to router, but internet access off ==> Same as before
- Adapter ON, connected to router, internet access on ==> Game launches.
Looks all pretty clear to me.
. Thank you for the thorough testing and step-by-step description of events, as they had transpired. I updated my original post with the following that may be useful:
Palestine: Update #2 (7th of June clarification edit with specificities): Today (the 5th of the month of June), I tested a completely different computer, in a completely different home (this time, a friend's MacBook with Linux). I re-downloaded the game's installation files from GOG, in order to determine as to whether or not the files had been updated (they had not). With
Static/Manual IP settings and without a DNS-cache (the same method used by the previously-tested desktop-oriented Linux-based computer), the game refused to start while the wireless network adapter was unlinked/disconnected from the router. Just as before, the game launched immediately once the link/connection was re-established with the internet-connected router. So, no news on that front...
Then, I attempted the same with
DHCP/Automatic IP settings (still, without a DNS-caching mechanism), and the game launched
without fail, regardless of connectivity-status (both, connected to the router, and disconnected). It would be safe to conclude that DHCP has some sort of fallback function (which leads to graceful failure) when
galaxy-log.gog.com is requested by 'Galaxy.dll' (through the execution of 'FalloutNV.exe'). An extremely high percentage of setups use DHCP, by default (for convenience); So, it is not at all surprising that this would cause the affected amount of users to be minimal...
So, if anyone is experiencing this issue, it
seems to be related to
not using DHCP/Automatic settings for IP connectivity, along with either:
not having a DNS-caching mechanism, or
having a recently-flushed DNS-cache (where the IP address associated with
galaxy-log.gog.com previously-resided), or simply having never had any contact with galaxy-log.gog.com (for whichever reason), when attempting to
launch the game while being
disconnected from the internet. I will still choose to use a static/manual IP configuration, as well as run without a DNS-caching mechanism, and play
offline (since none of my other games/applications have ever been this finicky). If you feel the same, either of the previously-mentioned work-arounds should be enough to treat the symptoms.
This seems to be the answer to the question of: "Why is it that so many are unaffected, and can launch the game regardless of internet-connectivity status?" Still, this is something that GOG can
fix (if they so desire).