Hello Alright, thanks for the answer, seems like a nice feature to have :) It would be even nicer, for the future, if it could optionally update already existing VMs to current stable ones (if there is more current stable one suitable for the image and user checked that he wants auto-updating VMs, download it and replace current one if it is not in use right now). Anyway, I will wait for your announcement then, thank you. There is one more problem (much less important though) I have for a very long time with Launcher on Windows so I will mention it now. Directories of Pharo images often contain quite deep structures of directories, like when I download a package from 'github://dalehenrich/filetree:pharo6.0_dev/repository' repository, it creates github-cache\dalehenrich\filetree\pharo6.0_dev\dalehenrich-filetree-8f6bc62\repository\MonticelloFileTree-Git.package\MCFileTreeGitRepository.class\instance\packageDescriptionsFromReadableFileNames.st inside the directory of the image. When I try to delete the github-cache directory manually using Windows file explorer (putting it into recycle bin), I get a dialog window which tells me that it does not fit into the bin and asks whether to remove it completely (yes, path lenght limitations even in most recent version of Windows). If I try to delete such image via Launcher, I get a FileDoesNotExist error for some file in such deep directory. If I remove that github-cache directory manually first (or just those too deep directories), Launcher then removes everything else just fine. It is no great problem to keep removing image folders manually outside of Launcher and there are certainly more important things to improve and fix, but if there was some relatively easy fix (probably there isn't), it would be great. Jan Dne 24.07.2017 v 10:22 demarey [via Smalltalk] napsal(a):

Hi Jan,

I’m currently updating the Pharo Launcher so that it can determine the right VM to use to launch an image and download it if not available on disk. It is almost finished but not yet ready! On Windows, there was indeed a bug in the executable name to find. It is now fixed on the latest build but I do not think the Launcher will work because the vm for 60 is buggy. OSProcess (used by the launcher) cannot work wit this VM. I’m waiting the publication of Pharo 6.1 with its VM (with OSProcess bug fixed) to publish and announce the new Launcher version. If you do not want to wait, you can replace the pharo 6.0 vm shipped with the Launcher with a Pharo 70 vm. It will work.

Regards, Christophe

Le 24 juil. 2017 à 00:28, Jan Blizničenko <[hidden email] </user/SendEmail.jtp?type=node&node=4956518&i=0>> a écrit :

...

Hello

It seems I am not able to open an image via new Launcher for Windows. I have downloaded new build of Pharo Launcher for Windows from https://ci.inria.fr/pharo/job/Launcher-Win/ (

pharo_installer-0.2.13.exe )

...

and it starts ok, downloads image ok, but I am unable to open it, although opening images works fine in older launcher ( pharo_installer-0.2.11.exe from 28. 2. 2017).

First time I tried opening the image (double clicking on it in the list), loading bar "Determining Image version" showed up and remained frozen like that without any progress shown in the bar. I gave it 10 minutes, but no change, still stuck like that. UI was not responding, so I terminated it via alt+.

Second time I tried opening the image via the Launcher, that "Determining" bar was there only for a second and then it was replaced by "Fetching VM to run Pharo 60 images" which seemed to be really fetching something, but after another second or two, it got stuck in the middle of the process and got an error "KeyNotFound: key '60' not found in Dictionary".

Well, it seemed like I got further, so third time is a charm. This time, instead of previous error, I got "FileExists: File @C:\Users\User\Documents\Pharo\vms\60.zip", which is quite understandable since previous process did not successfully cleaned up after itself.

I tried it repeatedly, tried it with both old (already existing) and new images (downloaded in new Launcher) and I tried removing whole Pharo folder in Documents, but every time I get stuck with one of those problems above.

There is a PharoDebug.log with logs of interrput and errors mentioned above: PharoDebug.log <http://forum.world.st/file/n4956495/PharoDebug.log>

Note that I can open those images just fine by opening them directly from Windows file explorer or via old Launcher, just not in the new Launcher.

Windows 10 Pro v1703 64bit.

Thank you Jan

-- View this message in context: http://forum.world.st/New-Launcher-not-working-Windows-tp4956495.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

------------------------------------------------------------------------ If you reply to this email, your message will be added to the discussion below: http://forum.world.st/New-Launcher-not-working-Windows-tp4956495p4956518.htm...

To unsubscribe from New Launcher not working (Windows), click here <http://forum.world.st/template/NamlServlet.jtp?macro=unsubscribe_by_code&nod...>. NAML <http://forum.world.st/template/NamlServlet.jtp?macro=macro_viewer&id=instant...>

-- View this message in context: http://forum.world.st/New-Launcher-not-working-Windows-tp4956495p4956532.htm... Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.