>But what if I don't want to use Setup Wizard. This is a great tool but when You try to create setup for two different kind of instalations or to create instalation on different language then English what then. I use install-us Pro and also wnat to know what files must include to my installation.
>

VFP 6 includes a .DEP file in the DISTRIB.SRC directory that outlines the exact file requirements for installation; you can write your own install using that as the basis to roll your own, but from my POV it's inherently dangerous to do, since if you screw up, you're on your own, and since Setup Wizard does the runtime side of things correctly, there's little incentive to reinvent the wheel, at least for me.

In addition, there's a template .REG file that tells you how to p[ut 4 required registry keys in place for the runtime. You'll have to use it as a template for what you need to do. Again, Setup Wizard's placement of the runtime environment handles this aspect neatly.

I use InstallShield Pro; rather than deal with the details of the runtime install, I use a minimal Setup Wizard created installation to put the runtime and dependent files in place, fired silently as a step of my InstallShield script. This way, if (or in reality, when) the runtime changes, I just replace the Setup Wizard install in my InstallShield distribution with the new one, and I'm off to the races - I don't have to pay much attention at all to the things that Setup Wizard does well; instlal the VFP runtime. Everything else I put in my InstallShield scripting. or I use the Windows Scripting Host, after it has been installed by my install scripts.

This makes updated runtimes easy, too - in order to move my VFP6 users to SP3, all I had to do was send out a Setup Wizard runtime install, which updated their existing runtime files (I scripted it through WSH; I make WSH a part of my standard distribution, so that I can use it subsequent to the initial install of the product. The WSH works well as a lightweight install language, with native access to network, registry, shortcut maintenance, executable firing, and all the power and function of JScript or VBScript.)

In this case, it's a matter of the right tool for the right job; since Setup Wizard knows how to put the runtime in place, let it do that, and leave the rest of the work to a more capable product. I've already invested both time and money in learning to do things with InstallShield and the WSH. I can't help you with the particulars of the product you'd like to use, since I've never tried it, and frankly, I doubt that there's anything in it that would make me want to move away from InstallShield now that I'm familiar with IS Pro.