Fosterinn: I am, in the process of building a gaming system for all of my GOG games that I have and want feedback on what version of Windows would be the best to use and why? I have access to copies of XP, Vista, 7, and 8 that I can use. Any suggestions would be greatly appreciated.
Is it only (mostly) just for running GOG games (and possibly older Windows retail games), kind of separate retro-gaming PC? As many have said, 32bit Windows XP has the very best compatibility with most GOG games.
BUT, if you are going to use that PC for normal PC use too, internet and such, XP starts to be rather insecure at this point compared to e.g. Win7/64bit. I say this just checking out systems of my friends/relatives who are casual users and know next to nothing about computers: their XP machines have quite often malware, while their Win7/64bit PCs remain mostly clean (in fact I don't even remember if I've detected malware on any of their Win7/64bit machines).
Win7/64bit in itself causes some extra quirks for many GOG games, but on the whole they can be run on it, one way or another. May require some extra steps, or some things may be a bit problematic, but not real game breaking issues I think.
Also, to me it seems that GOG games have much more often issues due to new hardware and/or their drivers, not necessarily due to Win7 itself (compared to XP). Like some games not liking quad core CPUs, or having issues because NVidia or AMD has dropped some legacy feature from their newer graphics drivers, or some game having an issue with high CPU speeds (at least Interstate'76) etc.
A couple of extra quirks that using Win7/64bit in itself may cause with GOG games, off the top of my head:
- Remembering to install GOG games outside the default Program Files (x86) directory, and/or running the game as an administrator (I install them under e.g. C:/Games/). You don't have to care about any of this in XP.
- Gorky 17 seems to have more issues on Win7 than on XP. Sometimes you may have to temporarily switch off 3D acceleration (even in XP) to go through some part of the game (for me there was one later battle where I had to do this, only once. After that I could switch on 3D acceleration again. But I've read some others can't run the game with 3D acceleration at all, but have to run it with software rendering all the time.).
But, switching off 3D acceleration can cause very bad audio stuttering inside the game, but in XP this can be fixed by going to Control Panel and disabling audio HW acceleration. In Win7, I don't think this is possible. Hence, if you have to run Gorky 17 without 3D acceleration in Win7, you may have quite scratchy audio which may make playing the game a PITA.
- In their eternal wisdom, Microsoft has made it harder to modify anything related to (General) MIDI settings in both Vista and Win7, compared to XP. For example, if you change the music to better sounding General MIDI in many GOG games, let's say Little Big Adventure, you may find the General MIDI music far too loud compared to the rest of the audio.
In WinXP you can change the MIDI volume separately. In Win7 (and probably Vista), this is not possible for some reason.
However, if you install some external MIDI software like BASSMIDI into Win7, it should allow you to change the MIDI volume. However, for some reason even that doesn't seem to always work, e.g. on my one Win7 machine it does change the MIDI volume (also for LBA), while in another Win7 PC it doesn't seem to have any effect at all. I don't know if this because in the PC where it works I'm using also a third party General MIDI soundfont ("Chorium Rev A"), while on the PC where the volume setting doesn't work, I'm trying to use the default "Microsoft GS wavetable synth" for General MIDI.
Also, setting up e.g. the Munt driver/utility (a Roland MT-32 MIDI emulator) that many older games, including GOG games, benefit from, is easier and more straightforward in WinXP than in Win7. But it is still possible also in Win7.
I'm sure there were more issues, but those for the start of those I've encountered. As said, there may be workarounds for many of them, and I don't consider any of them game-breaking issues.