Hi Ben, I've seen this (on Windows 10), 32 bit.
It wasn't happening last time I used Win10, some time in the last 4 months. Cheers, Alistair (From my phone) On 13 Jan. 2018 05:44, "Ben Coman" <[email protected]> wrote: > Before creating an Issue, can someone confirm the following behaviour on > Windows 10 ? > Downloaded and unzipped into the same folder... > * http://files.pharo.org/image/70/Pharo-7.0.0-alpha. > build.425.sha.eb0a6fb.arch.32bit.zip > * http://files.pharo.org/vm/pharo-spur32/win/pharo-win- > i386-201711262336-8879e2e.zip > > The directory contains... > Pharo7.0-32bit-eb0a6fb.image > Pharo7.0-32bit-eb0a6fb.changes > Pharo.exe > > Double-clicking Pharo.exe produces notification... > Information > Pharo cannot write to the changes file named > C:\Users\....\pharo\Pharo7.0-32bit-eb0a6fb.changes. > Please check that you have write permission for this file. > You won't be able to save this image correctly until you fix this. > > However if I edit to AST-Tests-Core > NumberParserTest >> testFail > to add "My Comment" > then close all windows, Save&Quit the Image, > restart Pharo by double-clicking on Pharo.exe, > and open System Browser on testFail > I can see my comment. > > I'm not clear on exactly how it works but I presume that restarting the > Image would require "My Comment" to be read from the changes file, > but notepad shows its not in the changes file. > So perhaps the error notification is part of a transition in-Image sources > and > nothing to worry about? > > cheers -ben >
