We are polishing off an app (VFP 6.0SP3) that will have a demo distributed on the web and needs to be able to install and run on any 32 bit Windows machine.

Which run-time files should I distribute with the app?

We have done MUCH testing. Originally, we only distributed the VFP6*.* files in the Windows\System folder. But we ran across a machine that needed MSVCRT.DLL.

We searched the UT and consulted the KB and found an article with the "magic list" of files to distribute. We happily included all of those files in our installation. (We are using Installshield Express)

Flew out to Atlanta and installed the system at a client. He was running NT4.0 SP4. After our install completed, the system told us to restart (raised eyebrow). Then when booting back up, proceeded to lock up. No keyboard lights, no mouse, nothing. We noticed that it seemed fine until Office 2000 started to load from his startup group. We restarted, held shift, got control, uninstalled our program, and everything was OK. We manually installed it with only what we needed and the VFP6* in the system folder. It worked fine. Scared the heck out of us.

So, I've been looking, but can't find the right list of files to include. I let VFP's installer create an install and looked at the dependencies. Here are the files it wanted:

Regsvr32.exe
Msvcrt.dll
Msvcrt40.dll
Stdole2.tlb
Asycfilt.dll
Oleaut32.dll
Olepro32.dll
Vfp6r.dll
Vfp6renu.dll
Vfp6run.exe

We made this our list and have had several successful installations, but we still aren't comfortable. We've had a couple systems request restarts with no problems.

I look at that list and see Asyncfilt, Oleaut32, Olepro32, Stdole2 all having to do with OLE. Do I need it? Not using drag and drop, not using OLE automation, not an OLE automation server. I can see regsvr32, the MS C run-time, and the VFP stuff.

Can anyone lend a hand or point me to the right reference materials?