On Windows, when SNAP was installed as Admin, SC can't change VM params
Description
Environment
Windows 7, 64 bits
Installation as Administration, on the Programs folder
GitHub Work
Activity
Nicolas Ducoin13 November 2015 at 08:56
Fixed by having a standalone application that asks for admin right.
Nicolas Ducoin6 October 2015 at 13:06
On the current implementation (release to come) the Smart Configurator can be launched as a standalone application and it is proposed to launch it on the last installation step. From the installer of by directly launching the application change of VM parameters will be possible if the user have the right to do so. From SNAP on Windows > Vista when SNAP was installed as an administrator it is possible to change these settings only if SNAP was launched as an administrator (right click + launch as administrator), otherwise it is clearly indicated the setting can't be changed (fields are greyed).
Marcus Engdahl6 October 2015 at 07:34
Currently I cannot change the toolbox settings via the toolbox - this *must *be fixed for the SNAP 2.0 release.
Nicolas Ducoin5 October 2015 at 07:16
The installer is already adapting the RAM settings according to the RAM available on the system. It is done in a simpler way than what the Smart Configurator is doing but is should still work without change. If you are aware of a problem on a specific low-RAM system we have to create a specific issue for this, specifying OS, RAM, and any detail that could help.
About the issue SNAP-250, there indeed has to be a fix asap.
Marcus Engdahl2 October 2015 at 13:28
I would mark this one "critical" as not being able to change the configuration can be fatal on low-RAM systems
Even if the user is administrator as snap was launched without administrator privileges SNAP can't change the snap.conf file.