IExpress Packager
- InstallShield Example
Following is an example of how to re-package
the Sun Java 1.4.1.04 installation, using IExpress, in order to create a
silent, self installing package.
In this example, the file to be run from the package is an extracted
InstallShield Self installer. You may need to create or modify an .ISS file,
depending on the software to be re-packaged. In this example we will need ALL
of the files extracted from the original installer, including *.bin, *.exe,
*.ini, etc. In this example all files needed are found in a single directory.
At this point, I am unsure how to repackage installation files the require a
specific, non-flat installation directory structure.
Before proceeding:
1.
Download the installer to be repackaged (j2re-1_4_1_04-windows-i586-i.exe
in this example) and save to the desired directory ("D:\" in this
example).
2.
Start the installer.
3.
When prompted to accept an EULA, find and copy the installation
files from your TEMP directory. Finding the TEMP directory took some time,
because it wasn’t obvious where to find it.
However, I was able to find it finally by taking a “printscreen” when
first executing the standard java installation executable, because it writes
names of files it is unpacking to it’s TEMP area as it is unpacking them. So then I knew to look for a directory with
a file in it named “data1.cab” and “lang.dat” etc. so I did a search on these
filenames and found out that the TEMP directory referred to here is at c:\Documents
and Settings\pcsupport\Local Settings\Temp\pft32~tmp\disk1\* and then to confirm looked at the most
recent access data for that directory, which was the current time, so I knew
that was the one to which it was writing.
4.
Now if you stop the standard install at the licensing agreement
Yes/No choice dialog box, the files extracted from the executable are still
sitting in the above-mentioned tmp directory, and you can copy them to another
directory before cancelling the install.
Now that you have the files, you can begin the steps below, and when you
get to the step to select all the files, go to the place where you stored
your “data1.cab” and “lang.dat” and all
the others and select all of them.
IExpress Packager
- Welcome to IExpress 2.0
|
Start the Packager by
running IExpress from the command line: IExpress is, aparently, installed
with Internet Explorer, and is found on most recent versions of windows. |
|
IExpress Packager
- Package Purpose
|
Select the type of
package to be created. |
|
IExpress Packager
- Package Title
|
Give a name to the
package, This will show in the title bar, and perhaps other places. |
|
IExpress Packager
- Confirmation Prompt
|
This is for a silent
installation: we do not want a prompt. |
|
IExpress Packager
- License Agreement
|
This is for a silent
installation: we still do not want a prompt. |
|
IExpress Packager
- Packaged Files
|
Add all the files
that are to be included in this package. In this example we will need all the
files that come from the TEMP install directory. A partial list can be seen
in the screenshot. Here you navigate
to the directory where you copied all the files in the TEMP directory found
at the beginning of this article. |
|
IExpress Packager
- Install Program To Launch
|
In this example we
are repackaging the setup file itself, and here we will call that file with
the required switches. In this example the full command line is: setup.exe –s –a –s
–sms –f1setup.iss Here is the relevant
link and information: http://unattended.sourceforge.net/installers.html |
|
IExpress Packager
- Show Window
|
Select whether or not
to show the installation progress. I use, and have only tested, the default.
I like to have a little animation on the installation screen. |
|
IExpress Packager
- Finished Message
|
Again. we do not want
to be propted. |
|
IExpress Packager
- Package Name And options
|
Give a name and save
location to the package. If any of the components use long file names, select
that here. |
|
IExpress Packager
- Configure Restart
|
Designate the
"No Reboot" switch here. |
|
IExpress Packager
- Save Self Extracting Directive
|
In this example I
have not chosen to keep the SED, which contains the answers to the previous
questions for future use. |
|
IExpress Packager
- Create Package
|
Ready to go ... |
|
IExpress Packager
- Create Package Finished
|
Success! |
|
IExpress Packager
- Notes
Notes on creating Self Extracting Installers
from InstallShield Installers:
1.
Some applications are not intended to support silent switches.
2.
You may need to run the installation in record mode to create your
custom .ISS file.
3.
Install directories which are not flat, i.e. have sub-directories
are not supported (at least I don't know how...)