Sanjay

I have had messages like this when I inadvertently tried to start two copies
of the same image (in my case pharo 6.1). The first image was running
happily in the background, the second gave this message (but still seemed to
start OK). I am also on Windows 10, using 32-bit Pharo.

HTH

Peter Kenny

-----Original Message-----
From: Pharo-users [mailto:pharo-users-boun...@lists.pharo.org] On Behalf Of
Sanjay Minni
Sent: 13 January 2018 05:50
To: pharo-users@lists.pharo.org
Subject: Re: [Pharo-users] Pharo 7 image cannot write changes message on
starup

Hi Richard,

the path for the image/changes/sources is 

   C:\Users\Myself\Documents\DevArea\p7\Pharo7.0-32bit-eb0a6fb.changes.

in which I have all the rights (this is a desktop in which I have admin
rights)
the pharo image messages also shows the same path (in my earlier post I had
replaced with ...)

the VM is is a separate directory which is in the path

so what could be the issue here


Richard Sargent wrote
> Hi Sanjay,
> 
> It depends on where you installed Pharo. The ... in the path cited is 
> important. (And maybe Pharo elided the path.)
> 
> If the path involves either of the Program Files directories, they 
> cannot be written by an unprivileged user/program.
> 
> Check your access rights on each directory or file in the path via 
> their properties.
> 
> 
> On Jan 12, 2018 21:09, "Sanjay Minni" <

> sm@

> > wrote:
> 
>> Hi
>>
>> I get the following message when I try to startup the latest Pharo 7 
>> image
>> (32 bit VM in Windows).
>>
>>     "Information
>>      Pharo cannot write to the changes file named 
>> C:\...\Pharo7.0-32bit-eb0a6fb.changes.
>>      Please check that you have write permission for this file."
>>
>> This is a desktop and there is really no issues o permissions What is 
>> wrong here
>>
>> regards
>> Sanjay
>>
>>
>>
>> -----
>> ---
>> Regards, Sanjay
>> --
>> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
>>
>>





-----
---
Regards, Sanjay
--
Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html


Reply via email to