DrJones
Posts: 18
Joined: Wed Jun 28, 2006 10:00 pm

Installer for use in other installers

We would like to build an installer, that does a driver install, and places a few .dlls in the system directory. This installer will be used by other people who create their own installers who would like to install our components.

We have a few questions on how to go about doing this.

First, what do we have to do so that they can run our installer silently with no GUI?

If we want to specify a directory to place the .inf and .sys files (so there is somewhere on the system they can be found if needed) can we have that passed in with a silent (No GUI) install?

Should this be a normal .msi project or something else? Would leaving it as a .msi or making it into a .exe with the bootstrapper be best?

Thanks in advanced.
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Re: Installer for use in other installers

Hi,
First, what do we have to do so that they can run our installer silently with no GUI?
For this you can enable the "Limit to basic user interface (simple progress and error handling)" option in the Install Parameters page. With this option the installation will show only a progress bar. It is not recommended to use a completely silent installation (no UI) because the installation may appear to do nothing (when used separately) or to hang (when used by other installers) even if it runs correctly.
If we want to specify a directory to place the .inf and .sys files (so there is somewhere on the system they can be found if needed) can we have that passed in with a silent (No GUI) install?
Yes, this can be done by using a property-based folder:
- in the "Install Parameters" page create a new public property (for example "DRIVER_DIR")
- set its value to the default path you want to use (for example "C:\MyFiles")
- in the "Files and Folders" page create a new property-based folder by using your custom property
- place the INF and SYS files in it

When the MSI is launched, you can set installer properties through its command line. For example:

Code: Select all

msiexec /i "C:\MyPackage.msi" DRIVER_DIR = "D:\My New Files Folder"
Should this be a normal .msi project or something else?
Yes, you can use a Simple, Professional, Java Application or Enterprise project (whichever is more appropriate for your needs).
Would leaving it as a .msi or making it into a .exe with the bootstrapper be best?
This depends on your requirements. The installation package can be used either way.

Regards,
Cosmin
Cosmin Pirvu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”