Hi Ben,

> Le 26 mars 2018 à 17:21, Ben Coman <[email protected]> a écrit :
> 
> 2. Double-clicked it and got "Windows Defender SmartScreen prevented an 
> unrecognized app from starting." [1]
> (btw, I didn't get this with the msi-installer generated from Advanced 
> Installer which I linked above.  But maybe that was because the msi-installer 
> was created and installed on the same PC, so it was just trusting itself by 
> default.  The msi wasn't signed, so is the experience different on other 
> people's machine?)

For this, I can get a signed version with Inria. It just requires manual 
signing by some Inria security unit.
So I will only do this for release versions

> 3. Clicked "More Info" which allowed me to click "Run Anyway" and got...
>     "To continue, enter admin user name and password" [2]
> so this is not really suited to students doing a user-level install on locked 
> down lab machines.

agree but with app signed, the problem should be solved

> 4. After entering the password for user "Admin" (i.e. not Administrator, just 
> another account in Administrators group)
> the install location was (as expected) given as.... 
>      "C:\Users\Admin\AppData\Local\PharoLauncher" [3]

Ah, I missed that. Not what I expected.

> which again is not friendly to non-admin users. 
> But just for kicks, I changed the install location to...  
>       "C:\Users\Ben\AppData\Local\PharoLauncher"
> and clicking on the PharoLauncher icon in the Start Menu
> it opened okay, and downloaded a 60539 image and associated VM
> and that image ran okay.
> 
> So its a step in the right direction, however...
> the Start Menu shortcut entry is for All User per its location here...
>    C:\ProgramData\Microsoft\Windows\Start Menu\Programs\PharoLauncher
> and the target of the shortcut is... 
>    C:\Users\Ben\AppData\Local\PharoLauncher\Pharo.exe
> so it only worked coincidentally because I'm clicking the Start Menu icon as 
> user "Ben"
> and it would be broken for a second Standard User.
> 
> From my reading it will be a struggle to get NSIS working smoothly
> for multiple use cases at different privilege levels. i.e. both non-admin and 
> admin users.

I will probably give a change to AdvancedInstaller.

Thanks for the feedback.
Christophe

Reply via email to