Squeak3.2gamma3 has now been removed from the UIUC server, and 
replaced by Squeak3.2gamma4, which does not have the "What is this 
error?" bug.

Update 4905, now published to 3.2gamma and also to 3.3alpha, reverts 
the critical method and contains a do-it provided by Andreas that 
guards against conditions that could arise if one had earlier updated 
past 4897 and then had managed to snapshot successfully.

If you happen to have a 3.2gamma3 image around, it should be okay to 
use it provided that you load updates before you next make a snapshot.

   -- Scott


At 3:58 PM -0700 6/30/02, Scott Wallace wrote:
>It appears that the latest official 3.3alpha and 3.2gamma images 
>both have a significant, and perniciously dangerous, bug, which 
>seemingly arrived in update 4897.
>
>Until this bug is fixed, it is *very dangerous* to be using any 
>image that has update 4897 in it, because each time you try to 
>snapshot such an image ("save", "save and quit", etc.) you stand a 
>good chance of losing the image.
>
>Thus, ironically, the only way to assure that you won't lose such an 
>image is never to save it.  Which however makes development work 
>problematical.
>
>Anyone who has not recently updated 3.3alpha past 4889 or updated 
>3.2gamma2 past 4889 or started using 3.2gamma3 is advised to hold 
>off on doing so.  Up-to-date 3.3a and 3.2gammaX images will all be 
>in a very dangerous state in which to save them is potentially to 
>lose them.
>
>Stay tuned...
>
>   -- Scott
>
>
>
>PS:  Reverting method ProcessorScheduler class.idleProcess *appears* 
>to circumvent the problem.