It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
avatar
Miaghstir: No, the "problem" is two things.
First, GOG's installer registers the game with Game Explorer using a GUID of their choosing (like any modern game labelled with "Games For Windows" does). The way to register in 7 works just as well in Vista (and has always been the official way, only Vista was more relaxed in what it accepted [not fully finalised, I believe] so GOG and others did it in a lazier way which is no longer accepted and produces the unusable icons under "Unspecified")
Second, Windows Vista's or 7's built-in "Legacy Games Detection" finds the game and sees that it is not registered in GE - because the GUID it expects is not present - so it registers the game with the GUID it does expect. Because it is a legacy game - created before there ever was a game explorer, much less have he installer use hooks for it - it surely can't be registered, right?
There may be more to it that just GUID matching, so something may get severely messed up if GOG just changed the GUIDs they use to whatever Windows expects for each game. I assume there is a pretty good reason they have not done so.
avatar
Elideb: Wow! Thanks for the in depth answer. I had no idea such a thing as "Legacy Games Detection" in Win 7.

both windows vista and 7 have a legacy game scanner if it sees an exe with a certain checksum it loads a simple profile for it. gog.com loads a different profile with the shelf art and there contact info the one windows makes has the allgames.com info. gog.com should talk with Microsoft about getting proper guid codes done for the titles or only do ones for games who do not have ones to begin with like the Dos titles that all have the same checksum.
avatar
StingingVelvet: And everyone move to Win7, seriously. It's an amazing OS.

I agree. Best Windows OS ever.
avatar
Elideb: Wow! Thanks for the in depth answer. I had no idea such a thing as "Legacy Games Detection" in Win 7.
avatar
Jeffpiatt: both windows vista and 7 have a legacy game scanner if it sees an exe with a certain checksum it loads a simple profile for it. gog.com loads a different profile with the shelf art and there contact info the one windows makes has the allgames.com info. gog.com should talk with Microsoft about getting proper guid codes done for the titles or only do ones for games who do not have ones to begin with like the Dos titles that all have the same checksum.

Your right, Microsoft says to contact 'Microsoft Windows Gaming and Graphics Developer Relations Group' (I remember seeing it on MSDN at some point) to retrieve info for legacy games if you wish to replace the legacy support in the Games Explorer.
Post edited January 17, 2010 by slake_jones
Any update on this situation?
Don't think it is so much a Win 7 problem, as it is a 32 vs 64 bit problem, and even the Win 7-64 doesn't know what to think....
Have tried to install several games using the compatability system, and it really fails. Sometimes even comes and tries to install again a full day later out of nowhere!
Hope the GOG people do list the Win7-64 compatables soon...
KH

They tried "Dune" from 1992. It's a DOS game and should run fine with DOSBOX.
They say Gothic 3 does not run because of the TAGES copy protection but copy protection is removed by the latest patch for G3.
So not a very reliable source.
NOLF is a tricky one. The Installer does not run on a 64-bit system but there is a workaround:
1. Copy the "Game" directory from your CD1 onto your hard drive. Rename it something life "NOLF" or whatever you want.
2. Copy NOLF.REZ from the "Data" directory into the same directory.
3. Insert CD2 and copy the .REZ files and language folders from the Data directory into that same directory.
4. Copy all files from the "English" (or whatever language version you want)subdirectory into your game directory.
Apply Patch 1.003: Unzip. Copy all files and foldes from the game subdirectory into your NOLF folder.
Apply Patch 1.004: unzip and start it within your NOLF folder.
5. Insert CD1 and run NOLF.EXE to play.
Post edited January 27, 2010 by Alfheira
Until now all my games bought here did not have any problems under Win7 Prof 64-Bit :)
I hope I don't bump into one that has poblems.
I haz ♥ for gog ^^
avatar
divemaster: Don't think it is so much a Win 7 problem, as it is a 32 vs 64 bit problem, and even the Win 7-64 doesn't know what to think....
Have tried to install several games using the compatability system, and it really fails. Sometimes even comes and tries to install again a full day later out of nowhere!
Hope the GOG people do list the Win7-64 compatables soon...
KH

Hmm... I am using x64 version of Windows 7 and have never had any problems running any game from GOG, but the Games Explorer is messed up because of the compatibility issues.
That's fantastic news. I was hoping for compatibility some time soon. Especially since i'm using Windows 7 now. Keep up the good work guys.
avatar
Navagon: Good to hear! Messiah completely fell apart on me in Windows 7. That's the only one so far though.

Ask Nvidia about that one. It's the same problem that I had with Gothic 1 and 2 and they finally acknowledged it in their release notes on the latest driver in the unresolved issues. Apparently it's only an issue with Nvidia cards.
Makes me glad I bought the ATI 4870 ;-) (Flame On)
Since we all don't know each other that well (years of DOS/Windows + experience), I would generally remind some of us and tell the younger kids 2-3 common sense things about old games and windows, if you older Dudes and GOG-Staffers would kindly forgive me this hybris:
1. Keep your old Windows OS CDs/DVDs (and FloppyDisks - ok, maybe not the 5.25'' ones)
2. Outside the 32-bit world, playing those old games is a stretch - be greatful if some cats make the magic happen - don't expect anything to work = always keep a 32-bit Windows OS on a harddrive just for playing old games - saves a lot of trouble in the first place?
3. Installers, sound and video drivers, old directx api, 'game patches' (dirty coding tricks) especially the workarounds for driver issues post game release... make this effort by the GOG-guys a real challenge. I salute them for what they try to achieve: making old games spaghetti code work on new hardware, so the next-gen gamers can experience the classics (outside XBOX LIVE, Steam etc )
4. On multicore systems I had great success by dedicating the old post-dosbox pc games to one cpu (task-manager settings) and also by using the "Compatibility Mode". This does not solve all problems above, but it is fun to check out and see what works and how.
5. Thanks GOG for carrying the torch! :)
Fallout and Fallout 2 is running slow on Windows 7 32-Bit but with compatibility option they are working fine.
I believe Windows 7 uses the same kernel structure as vista, so the games that work under vista should work under 7 with only minor differences.
I am running Win7 Pro 64bit on my gaming machine with only a few minor difficulties, resolved through use of compatibility tab or 'run as administrator' option
I just got into GOG...and of course...I just got into Windows 7 32 bit and 64 bit. Home Premium both which doesn't seem to work well...ugh!!