Downsizing irsetup.exe for overall smaller setups.

[NetSeeker]

During the install process there are several files expanded to the %TempLaunchDir% folder.

Remarkable is the file irsetup.exe witch has a size of 712 KB
that must be compressed about 400 KB - round about the size an empty setup has. There is the whole setup functionality located in.

if this file would be smaller, the whole setup would be smaller. this file is located in the Data Folder with the name w32wiz.da2. This file is so big, because it contains the whole functionality of the SUF6 runtime.

There are several easy ways to size this file down:
They are all based on the determination witch functionality is needet at design time (From Actions)

1. The simple way:
Provide several irsetup.exe files with reduced functionality and include the "right" one. Dhe Build of the several alternatives can be done with your compiler makefile or IDE Project

2. the more complex way:
Seperate the functionality in DLL's and include only the DLL's that are needed. (Link to the DLL's in a dynamic way with LoadLibrary and GetProcAdress)

3. The Hard way:
Dynamically build irsetup.exe with exactly the functionality needet for a particular setup

[Corey]

Interesting ideas Netseeker. Now *that's* my kind of suggestion, the kind which offers a list of solutions. We very much appreciate the thoughtful nature of your posts and I can guarantee you the right eyes are seeing this.

Corey Milner
Creative Director, Indigo Rose Software

[Ted Sullivan]

The amazing thing is that we've managed to fit that all into 400kb or so! Check out the size of the installshield runtime sometime (it's many times that size...) or worse yet, the Windows Installer runtime...

Anyhow, we're always looking to improve things! Thanks for the suggestions.

[NetSeeker]

This is only a suggestion. I've made a small setup today, and i recognized the size of the Setup.

In our configuration a master setup is containing several (about 4) additional setups (to manage the client /server software i'm developing). Then you will have the overhead 5 times (Master Setup / 4 Client Steups) (reduce the runtime 200K saves one MB in this configuration)

But in facht this is not a real problem. It would just be nice to get smaller ones th get shorter download times for our customers.