Let the installer set permissions for ProgramData\FAForever

[muellni]

Some people reported to have no write access to C:\ProgramData\FAForever and need to run the client as Administrator. The installer MUST fix it, since it introduced #401 . Could be fixed along with #470 once we figure out how to run admin scripts on installation. PR #484 tries that...

[duk3luk3]

Here is some information about setting permissions: http://msiworld.blogspot.de/2008/11/different-ways-of-giving-permissions-in.html

using any of those options probably means hacking up the bdist_msi module.

[GrotheFAF]

I run FAF 'as admin' (shows the mostly empty client), after that I could run FAF normal again. (all .log files are still owned by user) then I deleted forever.log and repeated it -> a forever.log was created under owner admin and FAF could not start as normal user after that. So I would guess (as normal user can't take that owner ship) log file creation/rotation should make sure that owner of forever.log is proper inherited. I used this to see the owner: > dir %ProgramData%\FAForever\logs /q

[GrotheFAF]

if it is just about forever.log, there should be something like this in log-rotation after log-rotation and new forever.log creation: if ctypes.windll.shell32.IsUserAnAdmin(): os.system("icacls %ProgramData%\FAForever\logs\forever.log /setowner %USERNAME%") os.system("icacls %ProgramData%\FAForever\logs\forever.log /reset") I tested this (with dosbox, not in client code) and it works.