Josh --

I followed your advice and ran the VFP Setup Wizard, and then had a look at SETUP.INF. This was extremely helpful...thank you for the tip.

I then went into Setup Specialist, set up the files I needed, created the setup diskettes, visited my client, and successfully installed the VFP app. All went well, until we booted the machine after the install. When Windows 95 came up, I was mystified by the fact that .DLLs -- MSVCRT.DLL and MSVCIRT.DLL -- were apparently missing. Neither of these files were part of the SETUP.EXE (however MSVCRT20.DLL and MSVCRT40.DLL were included).

This was not a major problem...I just copied these two .DLLs from another machine, re-booted, and all was fine. By the way, the VFP app ran fine, both before and after the re-boot.

Now, I am wondering -- did I somehow overlook or mess up something in my Setup Specialist project to cause these two .DLLs to get deleted? Thanks again for your assistance.

>Bill,
>
>Create an install set using the VFP setup wizard and take a look at the setup.inf file. It lists the system files and the application files it will install. Make sure you check the VFP Run-time box in the wizard.
>
>Setup Specialist has a watch feature that you can use. It will keep track of all the files opened by your app. I've found this of limited use because, for example, if I use my app's e-mail feature Setup Specialist includes all the files my e-mail system opens as well as the ones required for my app.
>