>> To: [hidden email]
>> From: [hidden email]
>> Date: Sun, 31 Jan 2016 20:27:37 +0100
>> Subject: Re: [Pharo-users] Problem to open Pharo 50 on Windows
>>
>> On 31-01-16 18:55, Franck Warlouzet wrote:
>> > I tried to help Justine a bit, but I have the same OS, the same VM, the
>> > same image, the same sources and it works for me but not for her,
>>
>> Which OS & update version, in what directories is it installed?
>>
>> Stephan


> On 31 Jan 2016, at 22:05, Franck Warlouzet <[hidden email]>
> wrote:
>
> For my case, windows 10, latest I assume. Installed on the desktop (in
> several directories, I'm organized).
>
> Do you think it could be an admin rights issue if it is installed in
> protected directories in Justine's case ?

On Mon, Feb 1, 2016 at 5:44 PM, Esteban Lorenzano <[hidden email]> wrote:
>
> it has to be… otherwise I cannot imagine what it can be :(

One thing to consider...  if the Image was installed into a protected
folder by an administrator, and then opened and then saved by a
standard-user, Windows presents *very* strange and *misleading*
behaviour,
which I describe here...
http://forum.world.st/FEEDBACK-Install-Pharo-on-Windows-td4733900.html#a4740803

Basically, the files installed into Window's protected folders *must*
be read only, or all hell breaks loose :).  When the standard-user
tries to write to Pharo.image in the protected folder, Windows (ever
soooo helpful) doesn't complain but *silently* takes a shadow copy of
the protected folder into the standard-user's folder which can be
written to. It then *transparently* makes it seem like the file in the
original location was updated, for that user.  The same happens for
other users so that for a single file location (e.g.
"C:\..\protected\Pharo.image") each user sees different data.

Should the original file be *really* updated by an administrator
installing an upgrade, the standard-users don't see the change.  They
still see only their own custom unique shadow version of Pharo.image.
This is really *evil* behaviour, so its good to share from this info
from time to time, even if its not the cause in this case.

btw, you can easily confirm this yourself just using notepad to edit a
protected txt file while switching a few times between Admin and
Standard-User accounts.  Some things have to be seen to be believed.

cheers -ben