Every time that I start Pharo 7.0.1 32-bit image (it's name is "Pharo 7.0 -
32bit" and it resides in the directory of the same name), a new directory is
created under images directory, with the name "Pharo 7.0 - 64bit
(development version)-01". Within it, Pharo is using directories
"ombu-sessions", "play-cache" to store its run-time information.
I'm using PharoLauncher version: 1.5.1.
The situation is the same if I do this with a fresh 7.0.1 image. System
reporter shows:
Image
-----
C:\Users\eftomi.MISKOTI\EFTOMI\PHARO\images\Pharo 7.0 - 32bit\Pharo 7.0 -
32bit.image
Pharo7.0.1
Build information:
Pharo-7.0.1+build.143.sha.eca26da119bccd95e463c7717a44b814453df4e8 (32 Bit)
Unnamed
Virtual Machine
---------------
C:\Users\eftomi.MISKOTI\EFTOMI\PHARO\vms\70-x86\Pharo.exe
CoInterpreter VMMaker.oscog-eem.2504 uuid:
a00b0fad-c04c-47a6-8a11-5dbff110ac11 Jan 5 2019
StackToRegisterMappingCogit VMMaker.oscog-eem.2504 uuid:
a00b0fad-c04c-47a6-8a11-5dbff110ac11 Jan 5 2019
VM: 201901051900
https://github.com/OpenSmalltalk/opensmalltalk-vm.git Date:
Sat Jan 5 20:00:11 2019 CommitHash: 7a3c6b6 Plugins: 201901051900
https://github.com/OpenSmalltalk/opensmalltalk-vm.gitWin32 built on Jan 5 2019 20:12:30 GMT Compiler: 7.4.0
VMMaker versionString VM: 201901051900
https://github.com/OpenSmalltalk/opensmalltalk-vm.git Date: Sat Jan 5
20:00:11 2019 CommitHash: 7a3c6b6 Plugins: 201901051900
https://github.com/OpenSmalltalk/opensmalltalk-vm.gitCoInterpreter VMMaker.oscog-eem.2504 uuid:
a00b0fad-c04c-47a6-8a11-5dbff110ac11 Jan 5 2019
StackToRegisterMappingCogit VMMaker.oscog-eem.2504 uuid:
a00b0fad-c04c-47a6-8a11-5dbff110ac11 Jan 5 2019
--
Sent from:
http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html