On Sun, Dec 09, 2001 at 02:58:45PM +0100, jhinsley at telinco.co.uk wrote:
> here insert explanation of what you were doing, suspect changes you've
> made and so forth.
> 
> 9 December 2001 2:56:47 pm
> 
> VM: unix - Squeak3.1alpha of 7 March 2001 [latest update: #4173]
> Image: Squeak3.2alpha [latest update: #4586]
> 
> UnixProcess class(Object)>>doesNotUnderstand:
> 	Receiver: UnixProcess
> 	Arguments and temporary variables: 
> 		aMessage: 	a Message with selector: #systemType and arguments: #()

<remainder of ghastly crash and burn stack dump snipped>

John, older versions of OSProcess (prior to version 2.4) used the
message #systemType, which has been eliminated in more recent versions.
My guess is that you were filing the new stuff into an image that had a
much older version loaded.  If you unload the old version (I posted a code
snippet for this, but I don't know if it works with a very out of
date OSProcess version, so do it by hand), and close any windows that
hold references to the singleton OSProcess>>thisOSProcess, then reload,
all should be well.

If that does not do the trick, please let me know exactly what you were
doing when this problem arose, and I'll try to reproduce it. I tried
loading a new OSProcess 2.6 into an image with OSProcess 2.3, and I got
lots of errors but no crash and burn, so I'll need a little more
background to reproduce the problem you saw.

Dave