ml> the problem may be the semaphores and exit errorlevels that you can
 ml> access and catch, though...

 SD> Max simply exits via an errorlevel and that's the end of its
 SD> involvement until it's called back to start again.

right... what i am/was looking at was having the ability of causing it/them
to exit with a specific errorlevel that can be caught and acted upon... 

 SD> What I've done is written a little Pascal program that will cause 
 SD> the node to "sleep" until the semaphore file that is specified 
 SD> when it's called is deleted.

that should work as well as what i suggested... as long as the nodes
release all files and reload them when called upon... i don't see any
problems with that ;)

 SD> Here's the program:

that look svery similar to my operation over here :)

)\/(ark