Thanks for the response Ed,

>>I have an installation that I've created using the VFP setup wizard. In my setup I run a post-setup executable. The problem I'm having is that my setup and post-setup executable will run fine the first time it's launched. If I try to rerun the setup.exe again on the same machine, the setup runs through initial VFP setup, and begins to run my exe. It runs the main.prg (stuck a message in to verify) and then hangs up without the form showing. If I kill the setup exe, my form then shows and I can continue running form from there. This is the behavior any time I try to rerun the setup (even after a reboot or calling the setup from the applications setup directory). The exe that I'm running post-setup runs just fine if I run it stand-alone. It's only when I specify it in the setup wizard that I have a problem. I originally specified the post-setup exe as a file outside of my \distrib directory. When this didn't work I included the post-setup exe in the distrib folders. Neither works.
>
>Is the post-setup executable written in VFP? If it is, VFP may not be ready for use - it may have required some of the runtime files and .DLLs to rely on delayed copy and registration if any of the updated items were loaded before Setup. The result is that VFP doesn't work before you reboot.

Can you elaborate? I'm not sure I follow. The exe is written in VFP. If I am understanding your statement, this shouldn't be an issue. Both machines have VFP6 loaded and are used for development, and all needed VFP runtime/.Dlls would be in place.

>
>You may also need some other component which doesn't install from Setup Wizard - DCOM, or various OS SPs for example.
>>
>>I'm running NT4.0 with VFP6 sp3. I can duplicate this same install behavior on another machine running Win98
>>
>
>Try adding NT SP4, and installing DCOM on the Win98 box.

I may have to try your advice, however the exe is written in VFP and runs fine on both machines standalone (not called from the setup wizard). Both machines have VFP development environment and have had multiple installs of DCOM in the past. As it stands, there aren't any calls in the exe which would require DCOM. Again, I only have a problem when I'm running within setup. I've got a bad feeling like I'm doing something incorrectly within my main form. I'm not that comfortable with windows settings like Modal/Modeless, ShowWindow, Desktop, _screen=off, etc..etc..etc. And it sure smells like I have a related issue here.

>
>>This executable is a VFP exe with a main.prg which calls a single form that is modal and has showwindow as top level form. I've played with both properties to see if there would be a difference and to the best of my knowledge it didn't matter. I also have SCREEN=OFF in a config.fpw file compiled into the executable.
>>
>>Any thoughts on what I may be missing here? This is really frustrating. I've spend way too much time on this and now know that I should have invested the money on a real install program