/build/static/layout/Breadcrumb_cap_w.png

exe being called from MSI but don't know how !!

Hi All

I'm trying to deploy some software called Schlumberger DeXa.Badge SCUK 4.5 (I don't think it's very well known !!). I've managed to extract an MSI quiet easily and made an MST for the silent installation. However, after I click Install (using msiexec /i to test for now) it launchs another installer "on top" of the MSI which has a propt for a configuration file. Not an ideal scenario for a silent installation !!

The second installer seems to be an exe, not an MSI. Looking in task manager, it seemed to be called IDriver.exe - which doesn't exist anywhere in the installation source directory. So ... a bit bemused ... I done some searching and googling and found out that IDriver has something to do with Install Shield (I'm guessing it's for installing drivers or some kind, but that's just a guess). So I opened the MSI with orca in the hope that I could silently call IDriver - but when I search the MSI for it, it's nowhere to be found.

Can anybody help me find out how this exe is being called and how I can do it silently ? Any help would be greatly appreciated

Thanks in advance

0 Comments   [ + ] Show comments

Answers (5)

Posted by: AngelD 14 years ago
Red Belt
0
The IDriver.exe is part of the installshield legacy or COM-component installer.
Could be from the isscript.msi if the setup.exe launches this prior to the actual product MSI.
Posted by: y2k 14 years ago
Senior Yellow Belt
0
Thanks for the reply AngelD. Yea, after I posted I decided to have a look at the ISCRIPT8.msi file also. But searching for IDriver in there yields nothing either. Maybe I need to look in the streams of these two files ?
Posted by: anonymous_9363 14 years ago
Red Belt
0
Really?!? The version I have (ProductVersion 3.00.185) has a component called 'iDriver.exe', whose file is v8.1.0.293.
Posted by: y2k 14 years ago
Senior Yellow Belt
0
hmmm ... you sound quiet certain !! I'll have a closer look with Orca again tomorrow and post back
Posted by: anonymous_9363 14 years ago
Red Belt
0
If it turns out that there is a nested install, I suggest capturing that (if it's not an MSI), installing it separately in your eventual deployment and preventing the Custom Action which executes here by adding an impossible-to-meet condition.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ