Dear Ben, On Sat, Feb 1, 2014 at 3:03 AM, <[email protected]> wrote: > So far it seems the options are: > > 1. Add a manifest to the installer such that UAC virtualization is turned > off (per Task #5 [3]). Saving the image will now fail but avoid submarine > problems later on. Can the VM be told the image is read-only and Save is > disabled. Or if a save fails, could is fall back to the Save As defaulting > to the folder where PharoLauncher is managing its other images. > > There might be other issues to deal with the files Pharo.ini, stderr & > stdout being prevented from being written to in the normal course of > operation. > > 2. Install "User Only" per [4]. This is probably easiest to do this close > to Pharo 3 release. > > [1] http://blogs.msdn.com/b/aaron_margosis/archive/2004/06/17/157962.aspx > [2] > https://blogs.windows.com/windows/archive/b/developers/archive/2009/08/04/user-account-control-data-redirection.aspx > [3] > http://www.klopfenstein.net/lorenz.aspx/simple-nsis-installer-with-user-execution-level > [4] > http://www.klopfenstein.net/lorenz.aspx/simple-nsis-installer-with-user-execution-level
sorry for answering so late.There are very few Microsoft Windows users that reported anything about the Pharo launcher on Windows, so I guess you are one of the only users on Windows. If you have time, please try the approach you like better and keep me informed. The fact that the Pharo 3 release is close is not relevant as the launcher is not part of Pharo 3. Best -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill
