> I ran into a similar problem in VAST that I got around by extending Block and
> Process.  I extended Block with #forkReady, #forkReadyAt: and some others and
> Process with #ready.  The #forkReady extension to Block basically does what it
> says, it creates a new fork or process in the ready state by does not start it
> immediately.  The new process will wait for its normal turn to start.  The
> #ready extension to Process makes the process ready without running it
> immediately and is used by #forkReady.

I bet that your #forkReady has the same race condition problem that 
Andreas is trying to solve in Squeak's #fork.  :-(

Paolo