Check for write permissions in the Filesystem

[GoogleCodeExporter]

What do you want?
The updater should see if he has file-changing permissions before beginning
the update and telling the in case he hasnt that updating through the
updater is not possible.

Why do you want it?
I am surely not the only user having this program installed in c:\user\
under Windows 7 (should be a matter in Windows Vista as well) and hence the
updater is of no use anymore. With such a message it would be at least
possible to get rid of the exception window and maybe a lot of bug messages.

How do you suggest it's added?
The updater could write a dummy file. If it is created everything is fine,
if not.. well, in that case there are no permissions available for that.
Maybe there is a way to get root access, but i dont know how to do this.

Will it cause any incompatibility problems with previous versions?
None that i could think of.

Original issue reported on code.google.com by mamage...@gmail.com on 16 Oct 2009 at 8:17

[GoogleCodeExporter]

can you be more clear about what happened and at what stage? the last update i 
did
last night changed the updater so that it writes the downloaded file to your
application data folder instead, so file writing permission should not be a 
problem

Original comment by frank.zhao.main@gmail.com on 16 Oct 2009 at 12:42

[GoogleCodeExporter]

i mean shouldn't be a problem from build alpha 38 and up

will work on only having one updater run at once, checking for running 
processes, etc
on the next update

Original comment by frank.zhao.main@gmail.com on 16 Oct 2009 at 12:50

• Changed state: FixedInUpdate
• Added labels: Type-Defect

[GoogleCodeExporter]

ok, it happened from 35 to 38. If you already changed that it should be no 
longer a
problem i guess ;0)

Original comment by mamage...@gmail.com on 16 Oct 2009 at 1:41

[GoogleCodeExporter]

Original comment by frank.zhao.main@gmail.com on 16 Oct 2009 at 7:26

• Changed state: FixedOld

[GoogleCodeExporter]

Not exactly fixed. 
On windows 7 the update works like a charme, yet if the installation of the new 
paket
starts it starts without admin priveleges hence cannot install into the program 
files
folder. Maybe you can add a flag for the install file somewhere to run only with
admin priveleges..

Original comment by mamage...@gmail.com on 18 Oct 2009 at 2:23

[GoogleCodeExporter]

notes to self: suggested fix, reference RequestExecutionLevel in
http://nsis.sourceforge.net/Docs/Chapter4.html and use highest, if that doesn't 
work,
try admin

Original comment by frank.zhao.main@gmail.com on 18 Oct 2009 at 5:28

• Changed state: Started