I think the process object is what you are looking for.

While squeak does run several environment level threads, the interpriter
itself _IS NOT_. 

This doesn't matter much on single proc machines but sucks for dualies
and the new P4s...

Philip Metz wrote:
> 
> Has there been any discussion of a multithreaded Squeak, i.e.
> where messages can be sent and received asynchronously?
> It seems to me that some applications could benefit from such
> a capability, e.g. a user interface that needs to maintain near real-time
> response, while the applications does intense processing in the
> background.
> 
> Is this incompatible with the basic design of Smalltalk, or just
> very difficult to implement? Would it destroy some desirable properties
> of Squeak's architecture?
> 
> Philip Metz

-- 
pain (n): see Linux.
http://users.rcn.com/alangrimes/