Answers to the most common questions are given below. If you still can't find the answer you're looking for, you can e-mail us your questions.

 Which Windows platforms does InstallConstruct support?

You can run InstallConstruct 7.0 under Windows 2000, XP SP2 (Home, Media Center, and Pro Editions), 2003 SP1, and Windows Vista to create installer packages. All packages created with InstallConstruct 7.0 will run under Windows 95, 98 SE, ME, NT 4.0, 2000, XP SP2 (Home, Media Center, and Pro), 2003 SP1, and Windows Vista. Packages created with earlier versions of InstallConstruct will not run under Windows Vista.

All new licenses purchased after October 1, 2006 and current members of the Subscription plan will receive free upgrade to version 7.0.

 How is my package size created by InstallConstruct compared to Zip?

Your package size may vary depending on what you include in the package, e.g. splash screens, etc. In general, the size of the self-extracting package created by InstallConstruct is smaller than maximally compressed Zip of the same set of files. In other words, InstallConstruct not only doesn't increase the package size with "overhead", packages created by InstallConstruct are usually smaller with our internal compression algorithm. For example, the InstallConstruct program package itself is 12.63% smaller compared to maximally compressed Zip of the same set of files.

 How do I make my program to show up in Add/Remove Programs?

In the latest version, all you have to do is to click the Add Uninstaller button on the Target Systems, Setup Registry Items page .

 How do I register a self-registering program?

On the Setup Wizard page, check off the "Run self-registering program" option box will do it.

 Can I update or add to INI files?

On the Setup Wizard page, check off the "Create/Update INI file" option box. You will then be taken to a subsequent page to enter additional information to create, update, or add to INI file. Detailed Help is available via clicking the Help button on that page.

 I would like to use InstallConstruct to package and distribute my VB (Visual Basic) program with VB Runtime, which files should I include?

For VB6 Runtime, minimally you should include the following files: Msvbvm60.dll, Stdole2.tlb, Oleaut32.dll, Olepro32.dll, Comcat.dll, Asycfilt.dll, Ctl3d32.dll. You can use Microsoft Visual Studio 6.0, Tools, Visual Basic Package and Deployment Wizard to place all the required library files in the Support folder for you. Then, include that folder when you create your package using InstallConstruct.

 How do I install ADO/ODBC/MDAC support files?

You should include the mdac_typ.exe file in your InstallConstruct package and run it to install support for ODBC, OLE DB, ActiveX Data Objects (ADO), and Remote Data Services (RDS). You can download mdac_typ.exe from the following Microsoft Universal Data Access Web site:

http://www.microsoft.com/data/.

 How do I create an Auto Run (Autorun.inf) file to automatically run the package created by InstallConstruct from a CD?

An Autorun.inf file is an ascii text file using the OPEN command, e.g.:

[autorun]
OPEN=PATH\FILENAME.EXE

where path is the relative location of the package (FILENAME.EXE) to the Autorun.inf file.

 Can I run InstallConstruct scripts silently from the Scheduler?

Yes, you can run InstallConstruct scripts silently from the Scheduler by entering "InstallConstruct program file" -S "adx file" in the command line.

 I checked off the Create Uninstaller option. Where can I find it?

If you check off the Create Uninstaller option, the Uninstaller will be created online when your package is being extracted and installed. The Uninstaller will contain input information from the installer, such as the location of the installation foler, target platform, etc. After it is created, it will be placed in the <InstallFolder> folder on the target computer.

 I have paid for the Full Licensed copies of InstallConstruct. Do I need to purchase Distribution Licenses to distribute the target and uninstaller within and outside my organization?

InstallConstruct Full License includes free Distribution License for the package and uninstaller created by you. No additional Distribution License is required to distribute the package with your own contents, including the uninstaller.

 What is the difference between InstallConstruct and TurboSFX?

There are major differences. In short, InstallConstruct creates complete packages and stand alone setup routines, setup wizard, installer, uninstaller, and HTML-based Internet Component Downloads. It also runs setup routines created by others. InstallConstruct is a complete Installer program.

On the other hand, TurboSFX creates self-extractors as the file delivery front end, which can run multiple setup routines and programs, provide multiple-password protections, but it does not create setup wizard, installers, and uninstallers. TurboSFX will distribute single or multiple programs in the compressed self-extracting form and run the respective Installer routines.

For example, if you want to build a full installer, setup wizard, and unisntaller, you should use InstallConstruct to build it; if you have a program that already has a setup wizard created, you should use TurboSFX to create the distribution front end. If you have multiple programs, or a program with multiple versions, or multiple languages, you should use InstallConstruct to build each of the full installation routines, setup wizards, and uninstallers; then use TurboSFX to create the front end manager so your recipients can install only those components that are desired or permitted by the passwords provided.