Vista and 7 don't allow you to write to those folders (and their subfolders) without admin rights, so you'll either need to disable UAC (not recommended) or run ET as admin (not recommended).
Much easier to just install them under C:\Games\Enemy Territory\ or something like that.
There are other, more preferable solutions to that problem, such as turning admin control to the minimum so he can actually install anything in his C:\Program Files, at least I never had any problems with that.
Not unless you give a user rights to that area. Anyway its pretty useless for someone who's not only playing & using firefox to use a non-administrator account.
Wait, wait, wait... We are talking about PRIVATE computer, with your own PRIVATE account, since most people are using their private computer at home, they would like to have a full access to it. I think you mistake private computer + private os with computers used for companies.
ofc you have full access on your private computer but not all the time, that would be better since when you install some virus, the virus cant get at your system.
Most programs work fine from the default installation paths, only older ones, such as ET, have problems with Program Files.
Normally stuff installed under Program Files puts all its configuration files and such under the AppData directory in your user folder, but for some reason ET doesn't want to work too well with this implementation.
Disabling an important security feature because of a single old game is simply dumb.
Can't be arsed to reply to that comment chain, but the UAC stuff is a step into the UNIX direction by Windows, and honestly I think it's a welcome change.
Every other modern OS has it so why shouldn't Windows?
About the virus thing, that's actually exactly how it works (or at least should work). I haven't looked into the specifics of how well this is implemented, but I doubt it has security holes that allow you to elevate an user account into an administrative account.
It's pretty similiar to how Linux does this, actually, although it's usually even stricter on Linux. The basic idea is the same, though: non-administrators shouldn't be able to alter any important system files or anything that affects other users.
Anyway, everything using installers on Windows pretty much defeats the whole purpose of that system, as you need to grant administrator priviledges to even the smallest programs before you can use them. This isn't Microsoft's fault, though: it's a problem with Windows developers' mentality.
The installer problem can be solved by using something like UniExtract to skip the installer and just grab the binaries. Using this method also brings back the whole purpose of UAC.
K thanks ! So is that why I m issuing some troubles exec-ing my cfg ? Won't exec, sometimes, settings back to default, etc. ? OR is this something completely different ? :p
Just don't install them under C:\Program Files if you're on Vista or 7.
Much easier to just install them under C:\Games\Enemy Territory\ or something like that.
Right back at ya, bro...
a user should just be able to write in his user folder
Wait, wait, wait... We are talking about PRIVATE computer, with your own PRIVATE account, since most people are using their private computer at home, they would like to have a full access to it. I think you mistake private computer + private os with computers used for companies.
ofc you have full access on your private computer but not all the time, that would be better since when you install some virus, the virus cant get at your system.
Normally stuff installed under Program Files puts all its configuration files and such under the AppData directory in your user folder, but for some reason ET doesn't want to work too well with this implementation.
Disabling an important security feature because of a single old game is simply dumb.
Every other modern OS has it so why shouldn't Windows?
About the virus thing, that's actually exactly how it works (or at least should work). I haven't looked into the specifics of how well this is implemented, but I doubt it has security holes that allow you to elevate an user account into an administrative account.
It's pretty similiar to how Linux does this, actually, although it's usually even stricter on Linux. The basic idea is the same, though: non-administrators shouldn't be able to alter any important system files or anything that affects other users.
Anyway, everything using installers on Windows pretty much defeats the whole purpose of that system, as you need to grant administrator priviledges to even the smallest programs before you can use them. This isn't Microsoft's fault, though: it's a problem with Windows developers' mentality.
The installer problem can be solved by using something like UniExtract to skip the installer and just grab the binaries. Using this method also brings back the whole purpose of UAC.
SLAC