I have had similar problems over the years with the setup wizard
* Minimal installations (runtime only)
- setup.exe/memory problems on NT
- desktop icon
* More Complex installations
- OCX registration
. version problems with Microsoft OCX's (comctl, comdlg)
. proper registration of third-party OCX's
- installing fonts

I know there are some workarounds, like using WSH and a post-install executable, but that seems kludgey to me. Has anyone had consistent success with any third-party solutions? I should have given up on the Setup Wizard a long time ago...
TIA,
- John Pinter

>>I am trying to make install for exe with Install_Us
>>
>>The program can register dll's and ocx's fonts and so on.
>>I get a problem with the VFP6R dll which does not like to be registered.
>>Has the VFP6R.reg file anything to do with it?
>>The problem was not there under VFP5.
>>In other words how to register this file properly so that the error 'runtimes not found' does not appear anymore.
>>
>>Any suggestions welcome,
>
>My guess would be that either you have not put all the necessary components in place to register the .DLL, or that other components that have to be registered must be registered before VFP6.DLL is registered. the best guideline for this is the VFP6R.DEP file, which outlines the requirements for registration of the VFP runtime components in detail.
>
>VFP6R.REG has nothing to do with the self-registration of the runtime - it seves as a template for some registry keys needed by the runtime that are not created by self-registration, and the file must be adjusted to fit the actual install environment you create. there are comments in the .REG file that describe what these keys should be. The Setup Wizard creates the keys properly using the .REG as a template for itself.