Posted June 14, 2017
![avatar](http://images.gog.com/c2ff89ec8bace32653ee630ca0efeccac8ff344a94cc9946eeb3b39b26718369_avm.jpg)
So really, only completely new titles are "seriously" affected.
![avatar](http://images.gog.com/fc8ebd082c233822f091875ad36c1102a4a7d58be19b73e72c997de681aa40f1_avm.jpg)
To my knowledge F: NV is the first Steamworks only game we've had here. It relied on that steam.dll to run, and in the Gog version it has been replaced with a galaxy.dll.
For whatever reason the steam.dll still works on XP (and the game still runs sans Steam with it in place) while the Galaxy one doesn't (as Galaxy doesn't support XP anyway).
So I'd imagine the only games effected are those that previously were Steam only and have Steam features. Any old games released before the advent of Steam should be fine, and any newer games may or may not work depending on how reliant on Galaxy functions they are (but any brand new game isn't going to be guaranteed to work on XP anyway).
IMO, it makes it much worse that GOG couldn't be arsed to NOT break the Steam dependency, since it's an exception -- and a rare one, at that.