>As for 3rd party files, it is not a problem. I also had to tell VFP setup how to deal with those files.
The Setup Wizard probably did not get it right, especially if you had to send a shared .dll to \windows\system.
>About the platform consideration, how to you tell Install Shield to install specific files for Windows '95 and not for Windows NT? I tried Install Shield Express version and didn't find anything on that. Might it be possible that only the professional version will allow us to deal with multiple platforms?
I have no idea how InstallShield Express would handle this. I am using Professional, and there's a simple function call that handles this. I do not either like or trust automated systems - I want to write the code myself - more control, you know :).
>As for the list, yes I would be interested. Maybe the best way is that you can create a FAQ by clicking on the FAQ icon, the lower right one from the upper left frame.
The List:
\windows\system\foxpro.int
\windows\system\mfc40.dll
\windows\system\msvcrt20.dll
\windows\system\msvcrt40.dll
\windows\system\vfp500.dll
\windows\system\vfp5enu.dll
* (there I assume US English version - YMMV)
\windows\system\vfpole50.dll
\windows\system\oleaut32.dll (check MS Knowledge base for this one)
\windows\system\olepro32.dll
The following file has two versions - one for 95, one for NT.
\windows\system\ctl3d32.dll
Add to this any files needed by your .ocx files. Some of these files are considered shared. Some are self-registering.
This is only the beginning of the story - you must also replicate some registry settings to get this to work right, and these are dependent on your individual development environment.
Disclaimer: I gleaned this information from publicly readable Microsoft information. There was no reverse engineering involved. It is up to the individual reader to use or not use this information and they are solely responsible for the results. I warrant none of this.
----------------
David M. Stowell
D. M. Stowell Consulting
