Hi Ben,

Le 13 oct. 2017 �� 06:20, Ben Coman <btc@openinworld.com> a ��crit :

On Thu, Oct 12, 2017 at 3:43 PM, Christophe Demarey <christophe.demarey@inria.fr> wrote:
Hi Vitor,

Le 11 oct. 2017 �� 13:44, Vitor Medina Cruz <vitormcruz@gmail.com> a ��crit :

Hi Christophe,

Yes, but:

1- I can���t execute it if I don���t have administrative rights

ok. That the point I missed.
I think I will add a zip file with PharoLauncher for windows for user like you not having admin rights.

Might this be a "portable" app, where downloaded images and VMs are stored next to the PharoLancher application, configured by a startup-setting file?


Alternatively...
searching around I found this...

Good catch. probably by using RequestExecutionLevel = highest should solve the problem.

Also, when PharoLauncher is installed by an administrator and later used by a standard user, I guess there may be problems with Pharo needing to write changes to a restricted location??   Maybe that can be dealt with by... when a new user runs PharoLauncher from the start menu, copy it to their user folder $LocalAppdata\Programs\PharoLauncher
and run PharoLauncher from there where they have privilege to write? 

Yes, you could have problems but I do not think that adding more complexity to the installer is the way to go. I would rather prefer, in preference order:
1/ Pharo Launcher do not need to write data,
2/ if files need to be written, they should go to a Pharo data folder (e.g. $LocalAppdata\Programs\PharoLauncher) or to the user apps setting folder.

What I would like is that a Pharo image writes data where it should


btw, where are the NSIS source files accessible? 

https://github.com/pharo-project/pharo-build-scripts/tree/master/windows-installer

Can they be dropped in the PharoLauncher git repo?

No because they are shared and used with other Pharo build scripts.

Thanks for the information.
Cheers,
Christophe