On Sun, Apr 30, 2000 at 06:25:20PM +0200, Torge Husfeldt wrote:
> Hi Michal,
> First of all, make a backup of anything left (.image .changes files).
> (No real data recovery specialist works with originals).
> Have you thougt about reading the image into a InterpreterSimulator and
> catching the exception that would surely be raised, to then inspect the
> 'lost' image?! I haven't worked much with that thing myself but I know that
> much: there are two versions and you have to work with the one matching the
> endianness (Smalltalk endianness<Cmd-P>) of your machine (the attached cs
> should make the right choice for you).
> Then, if you have an intact .changes file (and your notes weren't hidden in
> Workspaces) you could use the famous codeBrowser to browse it.
> 
> hope this helps,
> Torge
> ----- Original Message -----
> From: michal starke <miso.fastlist at auf.net>
> To: <squeak at cs.uiuc.edu>
> Sent: Sunday, April 30, 2000 11:50 AM
> Subject: help! hosed precious image: rescuable ?

I had some like that corrupted image, when i touch my HD cables in phase of
"Smalltalk condenseChanges" and machine was frozen.

Maybe it is not the correct way, but worked fine for me :

I first removed all starting huge noninteresting lines of code up to 
found interested start point of my code lines and found start signature of
----SNAPSHOT---- . Then I saved file to some new named rescue.st and than
i file in that code to found previous operatin image... so try also this
with copy of your changes and new image ...


Jan Barger

New Message Board + Project for collecting web links ->	http://www.barnett.sk

 "The best way to predict the future is to invent it."  - Alan Kay
 "The mind can only see what it is prepared to see.  " 	- Edward de Bono