AdminStudio Repackager Error, "No INSTALLDIR definition was found in the options.ini file"?

Experts,

So, I'm trying to repackage a MATLAB MCR, which is a compressed file that unpacks before it installs, using AdminStudio Repackager. I'm getting this line in the conversion:
"No INSTALLDIR definition was found in the options.ini file" - which is true...
Which results in an unsuccessful build, in the end. From my research, it's something about building from/to root C (C:\), but I'm working out of C:\Packages.

Any ideas?
Michael LPr. SysadminAsked:
Who is Participating?
 
Vadim RappCommented:
...also, often setup.exe unpacks the msi wrapped inside, and launches it. In that case you can simply "steal" the msi from the %temp%, rather than repackage (unless the msi itself is bad and you can improve it).
0
 
Vadim RappCommented:
I did not understand this line:
"From my research, it's something about building from/to root C (C:\), but I'm working out of C:\Packages."

Anyways, after you have repackaged, the next step is to carefully review the result. Only the most trivial installations don't require any tuning after they have been produced by repackager. So open the resulting ism file and make it right.
0
 
Michael LPr. SysadminAuthor Commented:
I've never dug into the ism, but I did so just now with Notepad++

It looks like a bunch of gibberish [NUL][SOH] etc everywhere. Is there an Encoding or Language I'm supposed to be looking at it with?
0
Cloud Class® Course: Microsoft Exchange Server

The MCTS: Microsoft Exchange Server 2010 certification validates your skills in supporting the maintenance and administration of the Exchange servers in an enterprise environment. Learn everything you need to know with this course.

 
Vadim RappCommented:
ism is the "source" file of Installshield setup project. It's supposed to be opened by Installshield.

This is, assuming that your repackager has produced an .ism file. If it produced .msi, you can still open it with Installshield. But in any case, any editing of the installation you do with Installshield.
0
 
Michael LPr. SysadminAuthor Commented:
Thanks for this! I silly oversight... I just unzipped the damn file and packaged from that folder.
0
 
Vadim RappCommented:
Make sure it actually works. Sometimes msi file will have a condition inside that requires that it is run only from setup.exe.
0
 
Michael LPr. SysadminAuthor Commented:
There wasn't an msi in the unzipped file. It was a setup.exe.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.