On 28.06.2016, at 14:23, marcel.taeumel <Marcel.Taeumel at hpi.de> wrote:

> Max Leske wrote
>> Hi,
>> 
>> Opening the same image twice works fine as long as no writes to the
>> .changes file occur. When both images write to the .changes file however
>> it will be broken for both because the offsets for the changes are wrong.
>> This can lead to lost data and predominantly to invalid method source
>> code, which is a pain with Monticello.
>> 
>> I suggest that we implement a kind of lock mechanism to ensure that only
>> one image (the first one opened) can write to the .changes file.
>> 
>> 
>> I’ve opened an issue for Pharo here:
>> https://pharo.fogbugz.com/f/cases/18635/The-changes-file-should-be-bound-to-a-single-image
>> 
>> 
>> Cheers,
>> Max
> 
> Hi Max,
> 
> if I have a running VM in Windows 10, I cannot open a second one on the same
> image and also get write access to it. A warning appears. So, it never
> happens that two images write into the same changes file.

On Mac and Linux this is a problem, however.

Best
	-Tobias