>> okay this was because I had another instance of Squeak already running 
>> using
>> the same image and changes image.
>
> Think about the issues here - two copies of the same image running,
> recording changes to the same changes file. You open the changes file
> for write from the first image to get to a point where it records a
> change. You try to open the changes file again for the second image.
> Does your OS allow opening a file multiple times to write? Does it even
> allow opening to read once it's already open for write?
>
> And if it _does_ allow multiple writers, is it sane about it? Is Squeak
> smart about it? Just for starters, imagine the confusion if you need to
> later look at the file to try to recover some work.
>
> All in all I think it's safest to recommend not trying to run the same
> image multiple times.

Thats my point, but an average user is not necessarily going to understand 
the error message or click on ok and end up not being able to save any 
changes at a later point.

Either disallow two uses of the same image or provide a second changes file.

Or leave things as they are...

Sorry I just flagged up the second image issue by accident due to running 
the two images and thinking something else was going on.

Please ignore me.

Aaron