Ok, i'm new to the packaging world and i've come to a block. I'm trying to install a utility SOTI Mobi Control 5.02, it is basically SMS for Mobile Devices for anyone that hasn't heard of it. The install is launched by 1 .exe. Using Wyse Snapshot tool did not work. I think it was because i was creating an MSI of an MSI. I then later found the install is split.

Install Contains:
  1. Crystal Reports as an MSI
  2. SOTI install as install shield

I tried creating an answer file for install shield, but it doesn't work because eventually the SOTI install calls the ODBC configuration in another window. Since this installation is outside of the SOTI window, the entries i am making are not being captured in the MSI. Any suggestions would be appreciated. I apologize if this has been asked/answered in another post, just point me in taht direction and i'll go find it. I did not see anything similar.

Thanks in advance
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
Hmmm...tricky....If it was me, I would:

- halt the installation immediately after CR gets installed
- find its MSI and copy it somewhere safe
- cancel the installation
- clean the box/restart the VM
- Run the CR MSI to install the required version of CR that the app requires
- Start your snapshot or answer file-creation, whichever route you decide to follow.
You *should* find that the CR installation part is skipped and either your snapshot will be free of its junk (hands up everyone who detests CR and its version agnosticism!) or that the answer file drives the IS installer correctly.
Answered 03/06/2008 by: VBScab
Red Belt

Please log in to comment
0
Hi Neville,
this seems to be a bit tricky.
This setup.exe looks like it has all command line switches from Installshield turned of.
My suggestion would be to capture the hole installation and exclude everything from the Crystal Package.
Then you bundle the MSI from Crystal with your installation as a prerequisite.
Regards, Nick
Answered 03/06/2008 by: nheim
Tenth Degree Black Belt

Please log in to comment
0
ORIGINAL: nheim
My suggestion would be to capture the hole installation and exclude everything from the Crystal Package.
Easier said than done, Nick. Neville would need to know, for example, that the U2*.DLL files belong to CR. He may well do, but that's a bit of an assumption. Much easier to 'extract' the CR MSI, install it and THEN capture.
Answered 03/06/2008 by: VBScab
Red Belt

Please log in to comment
0
Hi folks,
@Ian: good point.
But this: Much easier to 'extract' the CR MSI, install it and THEN capture.
applies only, if he is capable of extracting the MSI from the proprietary Installshield CAB file.

@Neville: Install it and watch for the call for the Crystal MSI (maybe you need ProcMon). Copy it away from its temp location.
Another possibility would be to use Installshields "ISCabVu" to extract it.
Regards, Nick
Answered 03/06/2008 by: nheim
Tenth Degree Black Belt

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