Post Install PreRequisites Question

[jimbradley]

Hi There,

I am using a trial version of Advanced Explorer Ver 9.9 to evaluate , and have built a project using the Enterprise Template.
The main install is simple and works as expected. I have 3 Prerequisites that are being run Postinstall , lets call them A , B and C.
The prerequisites are ordered to run A,B,C and they do launch in that order. However B launches before A has finished, and C launches before B has finished,
which leads to a confusing on-screen experience for the user. Is there a way of making each pre-requisite wait for the previous pre-requisite to finish ?

I am using AI Ver 9.9 on Windows 7 in this instance.
Any help would be much appreciated.

Jim Bradley

[Eusebiu]

Hi Jim and welcome to Advanced Installer forums.

Thank you for your interest in Advanced Installer.

When the A prerequisite is launched the B prerequisite is not launched until the A prerequisites returns an exit code. In your case, it is possible that the bootstrapper (in case you have an EXE file) of the A prerequisite to return the exit code before the installation of the prerequisite to be finished.

Are your prerequisites packages created with Advanced Installer also?

Best regards,
Eusebiu

[jimbradley]

Hi Eusebiu,

Thanks for your reply.
I find the Advanced Installer UI very intuitive to use by the way , have been a ******Shield user in a previous job and your product is much better.

Now some detail on my prequisites .......
A is a Dot Net 3.5 Installer supplied as an msi file
B is a Driver Package for some hardware supplied as an exe file
C is a National Instruments driver supplied as an exe file.

I put C last as it is the only prerequisite that requires a reboot.
So in this build none of the prerequisites were built using Advanced Installer.

But your reply gave me an idea to try , so I have done the following
Using EXE to MSI package projects I converted B and C to each have their own msi installer and saved these in their own folders
I then rebuilt my original project with B and C pointing to their new msi installers.
This gives an improved performance with B not launcing till A has finished, but with C launching near the end of the B install

If I am trying things that dont make sense to you please say .... I have previous Windows Installer experience but I am new to Advanced Installer.

Many thanks

Jim Bradley

[Daniel]

Hello Jim,

You can try to create separate MSI from EXE packages for both of your B and C prerequisites. So, you can convert the B package to a MSI package, convert the C package to another MSI package and, then add them to your main project and see if the behavior still persist.

Let us know if this helped.

All the best,
Daniel

[jimbradley]

Thanks Daniel,

Before I noticed your post I tried exactly what you suggested, and I am glad to say it solved the problem.
Thanks very much for your response.

Jim Bradley