InstallAware

Hi,
I have an installation which takes up 6 min to install. The software is 1.5gb (with 1426 files)
Most of the files are binary files.

Using installaware older tips
1) I have given the compression level to zero.(ie no compression)
2) I have also used MYAH_DISABLE_VISTA_RESTART_MANAGER: Initially FALSE. Indicates whether the Restart Manager on Windows Vista should be disabled. Set to TRUE to disable the Restart Manager and improve runtime performance;

Any other setup I can do to speed up ???
I want this to reduce to 2min.

Same setup with other installation tool is only 1.5min. I do not know why Installaware takes so much time and where.

kishorkk23 wrote: I do not know why Installaware takes so much time and where.

Hey,

i can only answer this question.

Use the debugging and go through your installation step-by-step. This way u'll see which steps are taking that much time.

Hi,
Thanks for replying. Well I see most of the time is taken during the progress. All the files gets copied during this. Which takes around 4 min.
How can I reduce this?

Dear user,

are you sure that this is caused by file copy?
Maybe could be another process causing it or probably it is the real time required by the copy operation.

I can only suggest you to try to isolate in separate steps your setup logic in order to indetify the possible cause (if any).
With this I mean, to create a test setup project where you add and test at steps, the different parts of your project logic.

Honestly, I never found any meaningful difference during file copy comparing with my previous IA version builds.

Regards.

Hi FrancesCot,
I have created a new project with similar setup on other machine. The issue remains same.
I would like to know how the installaware handles the binary files. And why does it takes so much time in copying the binary files?
The time taken is only during the PROGRESS . Other than that there are no issues.
Is this the limitation of IA ?

Dear user,

For what I know InstallAware doesn't use a different way to handle binary file copy.
All the file copy operations that are executed using InstallFile are managed by Windows Installer Engine directly.

Could you please tell me more about the way you use?

Regards

Well I am not getting? I do not do anything, its just Installaware install PROCESS.
If it was windows installer issue, it should have been there for the build with other software.

If you can provide me various methods to speed up install process that would be great.

Dear user,

what I meant (... and probably I was not very clear) is, if InstallAware is used with MSI engine just queues the various command to Windows installer database.
The effective copy process it is executed by MSI engine ones the Apply Install command is triggered.

So I was just curious to know, if you have tried ( ...as test) to verify what's happens using IA NATIVE ENGINE ... just to make a possible comparison.

Personally, I have found that sometimes the installation time (using MSI) can be different, over different OSs and / or different MSI engine versions.

I will try to contact our dev team to see if exist any possible information to share with you (... but I do not think so).

Regards

I have attached the settings I have made.
I tried with Native installer and no MSI option, but the build did not execute. Anyways I am attaching the complete settings Which i Have made.

The NATIVE ENGINE should be enabled only by setting the following code at the very beginning of your script.
The above statement could cause different behaviour in your setup process.
Please refer to IA documentation available for "NATIVE ENGINE" for more details.

Regards

Well then provide me some good tips, as I am asking from few days, from the kind of settings I have made...

Anyone in the forum can please reply....

Dear User,

I was probably unclear and I'll try to repeat what I meant.

Using the Windows Installer fuctionality with a setup package, the file copy command is managed directly by the MSI engine.
InstallAware only fills the database used by the engine with the operations required.
The queued commands in the database are executed by the MSI only ones an Apply Install command is triggered.

Using the NATIVE ENGINE IA capability all your setup flow is out of the Windows Installer engine and commands can be executed immediatelly.
Doing this each command that you have with your script is excuted by the IA engine.

You could create a test project that just copy some files to see the effect of NATIVE ENGINE.
To do this just place a at the very beginning of your script the following statement: There is also a pre-built Native Engine project template available, which illustrates how to perform 32 bit-64 bit hybrid installations using the new native code setup engine, including full support for uninstallation of old product versions and the modification of installed setup features during maintenance.

The IA engine capability can be also fine tuned using several possibility available with InstallAware.
For more information on NATIVE ENGINE possible settings please refer to IA documentation.

Hope this helps you.

Regards

Hi,
Well I understood the NAvtive engine usage. But that is not helping me out. It takes more time than MSI. What I am interested is with the N no of files, Why the copying of data taking so much time. Is there any any option were It can be reduced.
Like ignoring any verifier rules or something.