Wow - thanks for the detail Ben. I'd forgotten about that windows virtual stuff. It's quite tricky...
I guess we might have to add this to the SmalltalkHub description on confirmation from Kilon. Tim P.s. I have another simple change queued up to let Launcher use a specified VM (not just the one you launched with). On the mac this gets around not being able to run Launcher again if it exits after launching an image (eg to launch a second one). It also has a nice side effect to let you test with a bleeding edge VM. Tim Sent from my iPhone > On 27 Aug 2014, at 06:42 pm, Ben Coman <[email protected]> wrote: > > kilon alios wrote: >> >> No dont talk to Damien if he is on holiday , I prefer to respect people free >> time / relaxation time. This can wait for when Damien will be back. Both >> Damien and I frequent the irc channel so we will talk , its not a problem. >> >> As I said in my original post I am downloading PharoLauncher from >> Smalltalkhub links that can be located here >> >> http://www.smalltalkhub.com/#!/~Pharo/PharoLauncher >> >> the link you posted is not contained in there , I used this >> >> https://ci.inria.fr/pharo-contribution/job/PharoLauncher-Win-Package/lastSuccessfulBuild/artifact/pharo-ci/pharo_installer.exe >> >> and this >> >> https://ci.inria.fr/pharo-contribution/job/PharoLauncherFinalUserImage/lastSuccessfulBuild/artifact/PharoLauncher.zip >> >> As I said my problem is on Windows, on MacOS its fine . >> >> >>> On Wed, Aug 27, 2014 at 5:49 PM, Tim Mackinnon <[email protected]> wrote: >>> Hmmm that sounds strange (it could be I messed something up) - but did you >>> get your zip file from: >>> https://ci.inria.fr/pharo-contribution/job/PharoLauncher/885/PHARO=30,VERSION=bleedingEdge,VM=vm/ >>> ?? >>> >>> I just tested that one (but on OSX) and it shows my change as well as >>> templates for Moose 5 and Pharo 4. >>> >>> I’ve just pushed another change (which would be 886), which also fixes a >>> bug Stef mentioned (if underlying files change, it used to terminate >>> instead of refreshing) - that should build shortly. >>> >>> However - the links on SmalltalkHub are still pointing to images from Jun >>> (the Hudson jobs aren’t triggered automatically it seems) - so I think you >>> might be running something other than what you think you are running. >>> >>> Anyway - let me know what happens, and I’ll try and talk to Damien (who is >>> on holiday) - and sort it out if I’ve broken it. >>> >>> Tim >>> >>>> On 27 Aug 2014, at 15:16, kilon alios <[email protected]> wrote: >>>> >>>> I mean PharoLauncher cannot download Pharo 4 because it displays no such >>>> option. No Moose 5 , etc etc. Its also the old GUI. So this must be the >>>> latest version, I am not near my window pc now at work so I will try >>>> tomorrow the developer mode to see exactly which version of PharoLauncher >>>> it is. >>>> >>>> Are you on windows ? >>>> >>>> >>>>> On Wed, Aug 27, 2014 at 5:07 PM, Tim Mackinnon <[email protected]> wrote: >>>>> What do you mean by Pharo 4 template? I just made a contribution >>>>> yesterday - watched it build the new zip file, and I just downloaded that >>>>> zip and I am seeing a “Pharo 4.0 (beta)” template tree? >>>>> >>>>> Just to check you are using the latest version, if you right click on a >>>>> template and choose “Create Image” - does it prefix the parent of the >>>>> template to the suggested name (e.g. Pharo 3.0-latest)? (this was the >>>>> change I made). >>>>> >>>>> It might be worth checking your settings as well (click on the icon lower >>>>> right) and check that you haven’t accidentally unticked the Pharo 4.0 >>>>> repository. >>>>> >>>>> Tim >>>>> >>>>>> On 27 Aug 2014, at 09:28, kilon alios <[email protected]> wrote: >>>>>> >>>>>> I also downloaded the zip file it still does not give me the same >>>>>> version as MacOSX, no Pharo 4 template >>>>>> >>>>>> >>>>>>> On Wed, Aug 27, 2014 at 11:04 AM, kilon alios <[email protected]> >>>>>>> wrote: >>>>>>> I downloaded PharoLauncher from smalltalkhub for Windows and it appears >>>>>>> is not the latest version for example it has no template for >>>>>>> downloading Pharo 4. > > Are you operating as a Standard(Limited) User ? Sounds like UAC File > Virtualization. I got hit by that. I believe that your new PharoLauncher > application with Pharo 4 template installed okay, but its being hidden by > your virtual copy of the old application. Two checks you can do: > 1. Run Launcher as an Administrator and check if you get different tempaltes. > 2. Check if you have a folder > C:\Users\YOURACCOUNT\AppData\Local\VirtualStore\Program Files (x86)\Pharo > > The hack fix is to delete that folder. > > I believe this problem will only occur if you go into development mode and > save the image, however this would be better to avoid this constraint. I see > a few options for a permanent solution, but I don't know which is best, so I > stalled in implementing it. > a. Install VM into C:\Program Files (x86) and Image & Changes files into > C:\ProgramData\Pharo > b. Install VM into C:\Program Files (x86) and Image & Changes files into > C:\Users\YOURACCOUNT\AppData\Roaming\pharo\bin > c. Install whole PharoLauncher app only per user (e.g. for "Just Me" ) VM & > Image & Changes into folder C:\Users\YOURACCOUNT\AppData\Roaming\pharo\bin > d. When run as admin, PharoLauncher Installer puts itself in the machine > folderC:\Program Files (x86) and when this is run as a Standard User, it > sets up per (b.). > > Actually reading around and finding [1], maybe (a.) is best. > > [1] http://www.experts-exchange.com/Programming/Installation/Q_28235986.html > > Background info... > https://decibel.ni.com/content/groups/windows-7/blog/2009/10/02/uac-virtualization-and-how-it-affects-your-installers > http://blogs.technet.com/b/mrsnrub/archive/2010/08/11/uac-virtualization-allowing-standard-users-to-update-a-system-protected-area.aspx > http://blogs.msdn.com/b/patricka/archive/2009/12/14/tales-of-application-compatibility-weirdness-demystifying-uac-virtualization.aspx > > HTH, cheers -ben
