Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Distributing using 3rd party installer
Message
General information
Forum:
Visual FoxPro
Category:
Other
Miscellaneous
Thread ID:
00318885
Message ID:
00332599
Views:
15
>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...

I use InstallShield Pro, probably overkill for most people. InstallShield Express and Wise both offer lower-cost alternatives (under the $250 mark) with a great deal more functionality than Setup Wizard, and the Visual Studio Installer can be used (download from msdn.microsoft.com/vfoxpro) if you have VFP6 and is available to VFP6 owners for free; it's a transactional installer, so as long as you don't have a dependency on a post-setup executable.

As to the issue of installation of third-party OCXs, you're going to have to know the requirements of the third-party control regardless of the solution you use. NT and Win2K present problems of their own simply because not all users have the necessary privileges to write into system directories or update all segments of the registry, which can prevent proper installation from being done by non-admin accounts, and because each account can have it's own Start menu and Desktop.
EMail: EdR@edrauh.com
"See, the sun is going down..."
"No, the horizon is moving up!"
- Firesign Theater


NT and Win2K FAQ .. cWashington WSH/ADSI/WMI site
MS WSH site ........... WSH FAQ Site
Wrox Press .............. Win32 Scripting Journal
eSolutions Services, LLC

The Surgeon General has determined that prolonged exposure to the Windows Script Host may be addictive to laboratory mice and codemonkeys
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform