>>>Hello,
>>>We are using Visual FoxPro 6.0, and we are making Distribution CDs with the Setup Wizard.
>>>The customer has to install DCom98.exe before running the program. We want to automatisize this procedure in the post-setup executable in the Setup Wizard.
>>>There is an option to execute this program without asking the user for installing (Dcom98 /q) , but the setup Wizard does not accept this.
>>>Another problem with this executable is, which directory for the DCom98.EXE is to be defined in the setup Wizard, the current directory on the harddrive, or the setup directory of the CD? Setup Wizard always tries to fill in the current Directory.
>>>
>>>How can we solve this problem with the post-setup executable?
>>
>>First, don't make DCOM a part of a Setup Wizard install; it is not appropriate for use with WinNT (installing SP3 or SP4 is the correct action to take with NT) and can cause a reboot to occur. If you want to incorporate DCOM into an install, write the install with another tool that can handle a split install by writing a RunOnce key to restart the install process after DCOM compeltes installing and rebooting.
>>
>>I'd recommend that your application simply check for the Reigstry Key
HKEY_LOCAL_MACHINE\Software\Microsoft\OLE with a registry key value
EnableDCOM to determine if DCOM is present; if not, use a Messagebox to display a warning to your user without activating a top-level form or the VFP main window, and then shut down. This will avoid the C0000005 error that most people associate with missing DCOM support; do this before any splash screen has been run.
>
>
>I am interested in doing this . . . . but have never used the Registry . . . do you have an example to check the registry?
In VFP 6, there's an FFC for handling the registry that should be able to open and read from the registry; in the VFP6 samples take a look at
Samples\Vfp98\Solution\WinAPI\regfox.scx for a starting point. There's also a registry class that can be downloaded for older versions of VFP here on UT in the Files Section under Win32 APIs, which uses API calls.
>
>I would appreciate any input you may have.
>
>James
