>> There may be registry entries necessary that are not built by the self-registration of the help components. We see this frequently in other places installing VFP6; in fact, as a part of the VFP6 distribution, there's a small .REG file that contains a template for building some registry keys needed to launch VFP6 applications by file association, that aren't a part of the self-registration process for the VFP6 runtime files. You're told what needs to be done (you have to look very hard for it, just like you have to actually read and understand the VFP6R.DEP file correctly to not rely on Setup Wizard to do the runtime install), and Setup Wizard incorporated the necessary functions in its install, but if you choose not to use Setup Wizard, it's your responsibility to build the keys and understand the dependencies. Microsoft isn't responsible for supporting some other vendor's tools for you.
>
>? As I've mentioned elsewhere, the decision to use a third-party installer is not one to be taken up trivially, and if your installer doesn't do the job right, I'd take it up with your install tool vendor. It's not Microsoft's responsibility if your vendor doesn't provide a capability that they do in Setup Wizard!
>
>> Remember what I've said in the past; not understanding the install process and your install tool makes you better than even money to screw up installation. Sounds like that's the problem here.
>
>
>
>Yes Ed,
>I agree with You that the Microsoft not responsible for my vendor product, but I bought the VFP to develop and sell my application to other people. They want instalation process to be on Bulgarian. So I think Microsoft is responsible to document somehow what files are needed to run VFP, what changes are needed to be done in registry to run everything OK. I search in documentation - there is no such explanation. How I can create my own instalation without I know the full information about this process. I think Microsoft is responsible to give me this information.
>
They gave you a tool capable of installing the necesary files (Setup Wizard) which you should be able to incorporate into your third-party installer without having to tell you how the thoird-party installer could od it itself. They provide documentation in the MSDN on all the help system requirements, and you can access that on-line at msdn.microsoft.com if you don't have your own MSDN subscription.

They also don't give you the source to the multitude of ActiveX controls they supply, or to VFP itself. I guess that they just don't give you everything you might want to have...

Use Setup Wizard to put the runtime and help file system in place, or use a trool that knows how to do this like InstallShield Express. It sounds like the problem lies with Install-us, not Microsoft.