I have an EXE from a vendor. This EXE is an InstallShield installer. When you double click on the EXE it will explode out all needed files to my %TEMP% folder. Once I have the exploded out files I of course see the Setup.exe and the rest of the source files. But, here is my issue. When I run the Setup.exe it starts up and runs fine until about half way through and then I am prompted to point the installer to data2.cab. There is no data2.cab file. When you look in %TEMP% at all of the exploded out files there is only 1 cab file called data1.cab.

Has anyone seen this type of behavior with an InstallShield installer before and if so what was the work around?

Thank you.
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
ok, first question, why are you using the files from %temp% if your just going to use setup.EXE, and its not an MSI ?
Why not just use the original setup.EXE ?
Im guessing data2.cab is embedded in the original setup.exe stub.
Answered 04/23/2009 by: reds4eva
Second Degree Blue Belt

Please log in to comment
0
If you are trying to repackage this app. then you dont't need to extract the setup
Using AdminStudio - Repackaging Wizard can even read the installation for you and recreate the installation as a .ISM/.MSI
Answered 04/24/2009 by: jaybee96
Red Belt

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