question for the pros:
While doing a capture of a vendor exe that has Installshield files (idriver etc.), should we be including them in the wise setup capture, or installing then separately out of our wsi/ msi?
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
As the InstallShield files are used during the vendor exe installation as their install-engine you don't need them as the MSI (after capture) will do this for you. Don't forgett to remove any IS related registry info.
Answered 10/24/2008 by: AngelD
Red Belt

Please log in to comment
0
ORIGINAL: AngelD
Don't forgett to remove any IS related registry info.
You'll find it easier to add the InstallShield stuff (files and registry entries) to your global exclusion list. Unless you want to memorise the CLSID, TypeLib, etc entries for IS drivers v6, 7, 8 ,9 10, 11 and 12, of course! :)
Answered 10/27/2008 by: VBScab
Red Belt

Please log in to comment
0
I have an vendor based application that needs the installshield idriver version 8 installed before executing the vendor msi.

I took a fresh packaging machine and installed the idriver8 installer. My packaging machine already has installsheild ver 9 and 10 files.

Then I installed the vendor msi to create a transform.

Now, in my setup.bat to be deployed via SMS, I have included 2 commands:
- the idriver8 install (msiexec /i isscript8.msi /qb) command
- the vendor msi TRANSFORMS = mst command with a /qb.

This install just hangs!

Why? I am pretty sure this is something to do with the idriver installation. Is anyone aware of how to better handle the idriver issues? Like any workarounds? again..this is not a setup capture, it is a vendor msi.
Answered 10/27/2008 by: aek
Purple Belt

Please log in to comment
0
ORIGINAL: aek
again..this is not a setup capture, it is a vendor msi.
Aaaahhhhh...so we must completely ignore the text in the 'Subject' line AND the text in your first post...a little more care in framing your question would save everyone some time, don't you agree?

Anyone's response to you will be pure guesswork without more information.

- Have you logged the installation? If so, at which point does it hang? If not, why not?
- Have you checked whether your InstallShield driver installation has been fixed to work around the 'RunAs/Interactive User' foul-up? I can't recall if v8 suffered from this but it's worth checking.
Answered 10/27/2008 by: VBScab
Red Belt

Please log in to comment
0
can't recall if v8 suffered from this but it's worth checking

Thanks to everyone for the answers.

Multiple packages, so multiple mix ups. But, both questions are definitely ongoing issues at my end ! I will try adding /l*V to the msi and see where does it hang.
Answered 10/27/2008 by: aek
Purple Belt

Please log in to comment
Answer this question or Comment on this question for clarity