I popped over to Windows for a moment to try to make my CloudflareUn crossplatform,
and installed PharoLauncher from the downloads page...
I logged in as an Admin to do this, but when I open it I get an error...
�� ��"PrimitiveFailed: primitive #createDirectory: in WindowsStore failed"
where...
path ==>��"Path / 'C:' / 'Program Files (x86)' / 'Pharo' / 'pharo-local'"
encodedPath ==>��C:\Program Files (x86)\Pharo\pharo-local
(self isDirectory: parent)�� ==> true
in...
WindowsStore(DiskStore) >> createDirectory: path
| parent encodedPathString pathString result |
pathString := self stringFromPath: path.
encodedPathString := Primitives encode: pathString.
result := Primitives createDirectory: encodedPathString.
result
ifNil: [��
parent := path parent.
(self exists: path)
ifTrue: [��
(self isFile: path)
ifTrue: [ self signalFileExists: path ]
ifFalse: [ self signalDirectoryExists: path ] ].
(self isDirectory: parent)
ifFalse: [ ^ self signalDirectoryDoesNotExist: parent ].
self primitiveFailed ].
^ self
A few calls down the stack is�� OmSessioNStore>>resetWithStoreNamed:��
Does this happen for anyone else?
Version Info...
OS��
-----
Windows 10
Image
-----
C:\Program Files (x86)\Pharo\Pharo.image
Pharo6.0
Latest update: #60528
Unnamed
Virtual Machine
---------------
C:\Program Files (x86)\Pharo\Pharo.exe
CoInterpreter VMMaker.oscog-eem.2254 uuid: 4f2c2cce-f4a2-469a-93f1-97ed941df0ad Jul 20 2017
StackToRegisterMappingCogit VMMaker.oscog-eem.2252 uuid: 2f3e9b0e-ecd3-4adf-b092-cce2e2587a5c Jul 20 2017
Win32 built on Jul 20 2017 20:21:26 GMT Compiler: 5.4.0
CoInterpreter VMMaker.oscog-eem.2254 uuid: 4f2c2cce-f4a2-469a-93f1-97ed941df0ad Jul 20 2017
StackToRegisterMappingCogit VMMaker.oscog-eem.2252 uuid: 2f3e9b0e-ecd3-4adf-b092-cce2e2587a5c Jul 20 2017
Also, I would expect trouble for Non-Admin users trying to use the Admin installed Pharo Launcher.trying to write to "pharo-local" under "Program Files".�� �� Does PharoLauncher have its own CI testing to ensure it can open okay and run an image?�� ��I'm glad to see it promoted in importance but with this it probably needs such CI testing of its own separate to the usual Pharo CI testing.�� On Windows such CI testing *should* run as a Non-Admin user.
btw, requiring Administrative privileges to install PharoLauncher is going to lock out people who don't have administrative control over their PCs e.g. University student labs. Wanting to run a quick demo for someone in a corporate office.�� Why don't we make it the same as OSX and Linux and be usable without Admin privileges.�� ��That would lower a barrier to entry.
cheers -ben