I'm already doing that, with a marker file that all the programs watch
for, and automatically exit when signalled. However, that doesn't seem
to have been enough. I'm trying to determine why, but our system is a
bit of a monster, with many cooks, and no "recipe" in dependable use.

What I may do is try to scan the entire directory of files, and see if
any are in use (except for the installer itself). If so, then refuse
to proceed.

Mike Hanson
www.boxsoft.net