Sometimes when I run an installation to upgrade a system, a target
file is in use. When the installation ends, it asks to restart the
machine, so that it can get exclusive rights to that file.

However, I can't always run the install on the server, in which case
the reboot trick won't work.

When I encounter this problem, I install it to a separate directory,
then copy the files in with Windows Explorer. It complains about the
specific files with access problems. This is a hassle. <g>

Is it possible to see a list of files that caused conflicts, so that I
can get a better idea of who's got what open? Then I can find them
and kick them out, so that I can rerun the install.

Mike Hanson
www.boxsoft.net