Has GOG decided anything about Windows 7 compatibility? A large attraction with GOG is the promise of Vista compatibility, and I certainly understand that everything I have purchased to date is specifically represented as XP and Vista compatible, but Windows 7 is definitely shaping up to be a big release.
Our experience with the RC has been very solid indeed. Add in DirectX 11 compatibility, speed, new features, improved ... well, everything it would seem(!)... and it's shaping up to be the gaming platform of choice. So Win 7 compatibility is at this point an issue for purchases, which is why I'm wondering what the party line will be? [I have had few issues with Win 7 tests of GOG installs to date]
Along the same lines, what is the GOG position on 64-bit support? With XP 64-bit was an experiment, with Vista it was an RC, but Windows 7 could easily be the nail in the 32-bit coffin. 64-bit works for the majority of apps, and works well - it's time to switch. Formally speaking, backwards compatibility is Microsoft's problem. Realistically speaking, MS probably could care less about classics that don't move more copies of Halo, and we're still looking for a "GOG experience."
So generally, I'm just wondering if GOG is planning, evaluating, promising or what in regards to the upcoming platform changeover?

Windows 7 isn't that much different to Vista or XP. The changes people keep talking about are way overexaggerated.
And besides, it's not even out yet. What Microsoft does from now until August (when it's released) can make the OS significantly different.

I've yet to find a single game I can't run in Windows 7 RC 1. Playing Tex Murphy, Simon the Sorcerer, Original War, and Neighbor from Hell w/ zero issues.
I think if it runs of Vista it'll run on Windows 7 pretty much (if Windows 7 isn't even more compatible).

It just about is. From what I've read it's the last 32-bit OS release they're doing. I've done limited testing and found that several of my GOG games work fine on 32-bit XP, Vista and on 64-bit Windows 7.

It's coming October 22 -- my understanding is it's been pretty much done since the release candidate, now we're at the finalizing stage, getting it ready for retail, etc (link)
To answer the question, GOG has previously stated they will be working to make sure the games are compatible with Win7 (can't seem to find the thread now, but I asked the question and that was their answer).

Indeed, I've been using the RC for about a month now and its not bad. I would not expect much of anything beyond security updates and maybe a little driver tweaking between now and the final release.
As for GOG support, the changes from Vista to 7 are mostly cosmetic... in that the basic functionality of the OS is not really any different, it just doesn't do quite as many stupid things as Vista does. I have yet to find a GOG game (or any other post-XP era game) that doesn't work on it yet. In fact, a few of my non-GOG games that did not work on Vista, but did on XP, now work fine in 7. So far, it looks like Win 7 will be to Vista what XP was to Win ME.

Please consider implementing the feature request that shows when the installer was last updated. :)

I
Yes, it seems inno setup doesn't supply built-in functionality for game explorer, if you look for it you can see that it isn't correct in vista either. Right-click a non-gog game (GFW or "legacy" game identified automatically by Windows) and you'll find a "hide this game" entry, it's not there on gog games and games you've added yourself by drag-and-drop. My guess is that the games aren't correctly registered as games (they show up as "undefined" in 7, not to mention the duplicate entries that Windows itself adds for some games, suggesting that some ID differs somewhere).
eDiTs: speling, Windows phone's handwriting recognition isn't as good as the old Apple Newton.

No registration is required; Microsoft includes all necessary tools in the DirectX SDK.
Games Explorer entries are defined by GDF data files created with the Game Definition File Editor. This editor can define all supported metadata, including Windows Experience Index recommendations and custom context menu items. The installer simply needs to pass the compiled file to the OS in the correct manner during installation for the game to show up as a proper Games Explorer entry (and override Windows' own recognition of that game, if any) and take similar steps when uninstalling. See Windows Games Explorer for Game Developers for more details.
I'm no programmer, but this all seems to be very straightforward.

Woot! At last I can use WGE fully, most of my games are GOGs.