>>>>This is a popular new bug, a couple cases a day now :) The fix seems to be to download dcom95 or 98.dll from the MS site and install that with your app. Usually, it's because users don't have IE4...
>>>
>>>Bruce does this mean we have to include this dcom95.dll in our setup or do we have to run the dcom95 update before setting up our applications. How have you handled this issue when you had to distribute your exe.
>>
>>No, I haven't tried it included with setup yet, but I think it should work, and that would be the best way to do it...maybe someone else has tried it?
>
>I downloaded the file from microsoft and it is not a dll it is an exe that will update your system, so I dont think we can include it in the setup, but we have to somehow fire it off after the setup.exe has completed. I hope someone else has overcome this problem already in a more automated fashion.

You can invoke the DCOM .EXE file by copying it to the target system and firing it as a post-setup executable in the Setup Wizard, or better, if the target system is known to support the Windows Scripting Host, to create a WScript and fire the Wscript as your post setup executable.

If you're a brave soul, you can hack the SETUP.STF created by the Setup Wizard to add custom actions, too. The format and syntax of the .STF is more than a little ugly, and you end up having to hack the STF file every time the setup is recreated.

You could also wrap your Setup Wizard install with an InstallShield script; have the InstallShield script run your Setup Wizard install, and if that finishes, write some InstallShield script to check to see if DCOM is needed, and if so, to run the DCOM .EXE after the Setup Wizard has completed, but before allowing your app to run. If you use a VFP-based post-setup executable to complete your installation procedure now, you would need to remove the post-setup executable from the Setup Wizard install, and then call it after the InstallShield script runs the Setup Wizard install and any follow-on DCOM install that might be needed.

InstallShield is not the only thing that could host your install; certainly Wscript, or even a batch file, could be used as a wrapper