Basically it is really rare that you lose your code in smalltalk (may  
if you disc is totally full).
never throw away an image and its change file after a crash. You can
do a recover from last changes or I never remeber the item name in  
the changes menu.
The changes is a log of all the actions you performed.

In addtion I suggest you to sue monticello so that you publish you  
code on a remote server (and you house can burn
and the code is still saved) and also automatically backed up on your  
local disc.

So with changes + MC
normally you should never lose code

Stef

Could you let us know what exactly crahsed your system because  
normally squeak is quite robust.


On 26 août 06, at 10:36, Rich Warren wrote:

> I was trying to run test cases for a project I'm working on, when I  
> started getting a lot of errors (Unwind errors, or something like  
> that). I eventually got them to stop, but a few seconds later the  
> entire squeak environment went black. I had to force quit (working  
> on a mac here), and when I tried to restart squeak, it appears to  
> load, but nothing shows up.
>
> Is there any way to recover from something like this, or will I  
> need to go back to a fresh image? I have a fair bit of code already  
> written, and I'd rather not lose it.
>
> I've had intermittent trouble with squeak locking up (usually as a  
> result of something I've done--but sometimes command-. doesn't fix  
> things and I have to force quit). Are there any steps I can take to  
> make squeak more stable?
>
> Thanks,
>
> -Rich-
>