I can't replicate the problem so far. Please note that you will not be able to open the same image multiple times without getting the warning about a 'missing' changes file. This is because Squeak keeps the changes file open for write during the entire session and this prevents another session to open the very same changes file.
In general, I always have VM/Sources separate from (multiple) image/changes and I never had any problems with it. I have some questions that may help me to clarify what's going on:
What does the title bar of the main window say? Does it display the actual image name correctly?
After starting, if you click away the warning and open up a file browser, what directory are you in? Is it the same as the image directory (which should be the case) and can you see the changes file from there?! Given that this is the case, when you're clicking on it, do you see the first n lines?!
What does the short cut look like?! Do you refer only to the image (assuming that you have associated the *right* VM with '.image') or do you explicitly specify the VM to use?!
Thanks for any information you can provide, Andreas -- +===== Andreas Raab ========= (andreasr@wdi.disney.com) ==+ | Walt Disney Imagineering Phone: +1 818 544 5016 I I Glendale, CA Fax: +1 818 544 4544 I +======< http://isgwww.cs.uni-magdeburg.de/~raab >========+
From: shaping@bigfoot.com Reply To: shaping@bigfoot.com Sent: Wednesday, April 28, 1999 9:51 PM To: squeak@cs.uiuc.edu Cc: recipient list not shown Subject: Separating virtual machine and image files on Windows NT
Hi folks:
I have my virtual machine and DLLs in one directory and my .image, .changes, and .sources files in another. I formed a shortcut to run squeak.exe with a full path to the .image file. I double clicked the shortcut. This caused Squeak to appear with a warning about not being able to find the .changes file.
Why would Squeak not look in the same directory where it was told to find (and actually found) an .image file? I don't want to duplicate my virtual machines unnecessarily by throwing each of several different images into separate directories with their own copy of a particular virtual machine. Does anyone know what to do here?
Regards.