Yes, it is clear now. I've never run into that as I've always done the installs and the second "install" has always been just creating a directory and copying the EXE. And then making the necessary shortcuts. And running the new EXE and setting-up the configuaration files on the first run. The advantage of being close to your users.

I don't think there is a real easy solution if you need to use the setup wizard. I guess you could create a batch file that checks to see if there is already a copy of the program on the system. If there isn't, run the regular setup program. If there is, run a custom setup program that just copies the necessary files to the desired directory as all the runtime files and registry settings will already be fine. Hopefully.

Sorry I couldn't be of more help.

Joe

>>I know there is an option to allow the installer to choose a different installation directory within the Setup Wizard. Does this not do what you want?
>>
>>I guess I'm not clear as to what happens when you try to install into a second directory; therefore, I don't know specifically what the problem is.
>>
>>Joe
>
>The second install detects the presence of the first install (it finds the setup.stf file in \dir1\setup) and proceeds as if we were wanting to add/remove to/from that directory. You no longer have the option of installing to a *new* directory. Your options are limited to Add/Remove, Reinstall (same dir), Uninstall. That's it. We have tried to remove the setup files in a Post-Setup EXE file .. but apparently, just before the setup wizard finished, it lays them down again. Hope this makes the problem a little clearer.
>
>-- Len