>...and when you run the setup, it will extract VFP300.EXE and a .DLL or two from compressed files and put it in the system directory. Until then, you won't see it.
>
>By the way, I've never used third party tools for installing fox apps. Whaddoyoudo, guys...run a fox setup in order to extract VFP300.EXE and some .DLLs, then use the other product to copy them somewhere?

Rather serious oversimplification, there. But that's a start.

I'm using version 5.0, and it is a process of installing (not copying) a set of shared .dll files, making Registry adjustments, installing the application itself, and so on. I've documented this process on the Thread - check the archives.

One difference you've noticed - in version 3.0, vfp300.esl only exists on the development machine in compressed and segmented form - you'll need to run a dummy install to get the file in one piece. They dropped that silliness in version 5.0 - vfp500.dll is in one piece on the development machine.