5 replies to this topic

[gskgouse]

Hi,

We have generated a setup using Installshield 2010 Professional of our application. We have used the Aladdin HASP drivers in our application and we have put this run time msi file in our setup. When we are executing this setup it was working properly, but in some systems where the system has higher version of HASP driver it was prompting a message saying higher version of driver available and omitting the current driver of our application. After this the setup is roll-backing, But here we want to continue our setup forward. what is the way to do it? Guide us in this issue.

Thanks & Regards
Gouse Shaik

[Stefan Krueger]

Are you adding the HASP driver as a msm or as a msi?

[gskgouse]

Hi Stefan,

Thanks for your reply. We are adding the HASP Driver as a msm.

Thanks & Regards
Gouse Shaik

[Stefan Krueger]

In this case I guess there's a custom action (probably in the msm) which returns error in this case. To fix this, either condition the custom action to not run if a newer version already exists (recommended), or set it to ignore the exit code (not recommended).

[gskgouse]

Hi Stifen,

Thanks for your valuable reply. Could you please tell us how to implement the custom action on msm in InstallShield 2010 as you suggested, also provide us some links related to this.

Thanks & Regards
Gouse

[Stefan Krueger]

Did you identify the custom action which is causing the problem? A log file would help you to do this.
What is the condition on this custom action?