So, what is up with these new GOG installers that will not allow you to install into Program Files (x86) -- which used to be the DEFAULT location. ALL my other games are already installed there.

Just when I thought I couldn't be more annoyed by GOG's ever-changing, inconsistent custom installers. Is there any good reason they can't use a normal installer?

This is already more of a hassle than some forms of DRM, honestly.

Tons of known compatibility issues installing into the Program Files directory, its for stability. Kind goes back to user type and permissions, and OS you are running. EG windows 2000^ only admins have rights to use/modify files in program files. from 98->xp all users could and for admins in vista->8 can as well but standard users cannot. You'll pop warnings from vista onward for file modification events in Program Files, unless you disabled them.

%appdata% is where changeable files go. as an example look at how dragon age installs and keeps config files. another example is Steam, the majority move their configs outside of the steam install folder since it resides in program files by default.

C:\Games...

No compatibility issues and easier to keep track of your games IMO.

still annoying, though

Great. Just great.

People install into Program Files (x86), people complain about games not working.

People can't install into Program Files (x86), people complain about preference issues.

I guess the next logical step is for GOG to disable UAC automatically with the installer. Oh, I can just see the virus alert topics sprouting up.

It's a bit of a blunt tool though isn't it? If they wanted to block that path, then they could have done so (and fairly informed the user why). I think this is a more general blunder.

About the informing part? Yes, it could be a bit more explanatory than just a "stick to the hands when you do something wrong". But the brackets thing might have been the simplest way to do it. Might be just a transitional thing anyway. And if it's a blunder, then it's a weird one at that.

How about warning people when they try to install there instead of blocking it off completely. The problem isn't even the program files folder its the ( which is blocked because it can cause problems just like . is which blocks the use of the gog.com folder.

In all fairness, I've encountered several games over the years that ONLY work when installed to Program Files. So if GOG were to start selling such a game and you couldn't install into that directory, then it's a bit of a problem.

For example, on some non-English language versions of Windows, Spore could only patch correctly when installed to Program Files. When installed anywhere else, it had the tendency to bugger up.

Blocking ( and ) does not prevent you from installing into Program Files, which would pose all of the same alleged problems as installing into Program Files (x86), so your entirely theory is nonsense. Unless the programmer is as foolish as you . . . which is entirely possible.

I never liked GOG's clunky custom adware installers in the first place, and this may be the last straw for me. What's it going to be next? Are they just going to force you to install into C:\Gog.com - Your Home for the Best DRM-Free Games\ ?

I actually have to commend GOG on this. Program Files has to be pretty much the worst place to install games and is the reason save games, config data and other regularly altered files are usually stored GOG knows where.

That was a bit of generalization on my part, and I thought the last two sentences would clearly show the nonsensical nature of the rant.

But anyway... don't install much anything into Program Files unless absolutely necessary. Make it neat and tidy with various other folders and sub-groups and many issues can be avoided.

I actually remember Sierra (and many others) doing this. One time I couldn't even install a game if I deleted the "sierra" part of the path.

Windows is a clusterfuck anyway, I would like everyone to agree on a clear location for userland apps, right now. I'm waiting... where is it?

-.-

Actually, as far as I'm aware, only some GOG installers prevent you from using special characters, and those are installers for games where special characters in the path would cause issues, like Dungeon Keeper 2 for example. After all, these are old games, and old software often has issues with special characters in install paths.