Solutions to a SqueakMap problem everyone should know about!

goran at krampe.se goran at krampe.se
Mon Dec 12 07:07:52 UTC 2005


Hi!

If you get a dialog popping up saying "Reading an instance of
SMMaintainableObject. Which modern class should it translate to?" - then
you have a newer version 2.1 map on disk, but the image still contains
old SM code, making them incompatible. Press alt-. to get out of that.

Now, this is a tricky problem which I am unsure how to "solve"
conventiently. For now there are two ways out:

1. This manual do-it will make the pain go away (upgrading to 2.1
manually):

	SMSqueakMap bootStrap

You would do that in every image that this pops up in - in other words,
every image that has not been upgraded yet and sharing the same SM dir
(thus stumbling over a newer map imagesegment).

2. Another simple "way out" is of course to first delete the map files,
the latest will be re-fetched. The map files are called map.xxx.sgz in
the "sm" directory. Don't delete the cache directory. Then you should be
able to open SqueakMap Package Loader and it should detect that it needs
to upgraded and everything should hopefully go smooth from there.

This issue is in Mantis btw:
	http://bugs.impara.de/view.php?id=2340

regards, Göran



More information about the Squeak-dev mailing list