Decompiler Installshield Wizard

Some program installations use InstallShield, and the program files are compressed into Data .cab files. But InstallShield decided to be cute, and use their own propriety format with older versions of the Data .cab file. They could have used a standard compression algorithm like .ZIP, but did not.

Fix software and app installation error in windows pcClick here for more detail.http://www.bsocialshine.com/2017/01/how-to-fix-software-installation-error.h. I think I used a tool called ISDCC (installshield decompiler), installshield compilers (i5comp or i6comp) and some hacking skills to create a new package. Anyway, the highest version my TLA704 supports is 4.4 which is already a major improvement over version 3.3.

My guess is that they didn't want people fiddling with the raw files.

Installshield Wizard Downloads Setup

That's a bummer for those of us who need to get at the files, such as Application Packagers. I discussed this a little in the InstallShield Temp Directory Trick.

So it's a good thing that CDMediaWorld has utilities, such as i6Comp to extract the files. Just download it (I picked i6comp02.zip) and then run i6comp. This is what i6Comp looks like when listing files from the data.cab file:

C:tempInstallShield>i6comp l -v -r data1.cab
InstallShield 6.x Cabinet Util
Version 0.2 -] fOSSiL & Morlac - 2000 [-

Date Time OrigSize Attr CompSize Ind FileName
12-16-1999 10:24 28529 ____ 5841 0 corecomp.ini
09-05-2001 04:18 77824 A___ 29916 1 ctor.dll
09-05-2001 04:13 32768 A___ 4483 2 objectps.dll
...
08-22-2003 17:27 278190 A___ 264385 180 PowerDVD.CHM
09-05-2003 16:16 65536 A___ 30014 342 AudioFilterclds.dll
09-05-2003 16:16 45056 A___ 8203 343 AudioFilterclwo.dll
09-05-2003 16:16 245760 A___ 81241 344 AudioFilterCLADR.ax
09-05-2003 16:16 126976 A___ 43046 347 AudioFilterCLAuTS.ax
09-05-2003 16:25 73728 A___ 27800 348 AudioFilterCLAudioCD.ax
09-05-2003 16:25 503808 A___ 239856 349 NavFilterCLNAVX.ax
09-12-2003 18:38 520192 A___ 205346 350 VideoFilterCLVSD.ax
09-05-2003 16:16 45568 A___ 23075 351 VideoFilterCLLine21.ax
---------- ---------- -------------------
49878589 19880422 311 file(s) total

C:tempInstallShield>

The list output is more interesting than the extract output. which is why I've showed list. Other options are:

C:tempInstallShield>i6comp
InstallShield 6.x Cabinet Util
Version 0.2 -] fOSSiL & Morlac - 2000 [-

Usage: i6comp [-opts] [file index|fmask|path] [disk fmask|path]
Commands
l: list Files
g: list File Groups c: list Components t: list Setup Types
s: convert multi-volume cab to a single volume (not recommended)
e: extract files (specify when specifying )
x: same as 'e' with subdirs
r: replace files in cab (same syntax as 'e')
d: delete files from cab (specify )
a: add files to cab ( is optional; must specify -g OR -f)
z: zero-size files (specify )
Options
v: verbose info mode
r: extract subdirs/recurse and store subdirs
d: include directories in cab matches
g: specifies File Group to work with
o: suppress supplementary output (start msg, comments, etc.)
f: treat File Groups as directories (usefull for GUI, wrappers)

C:tempInstallShield>

Update: this does not work with InstallShield 12 or later. I've written a post about that here.

InstallShield 2015 » InstallScript Debugger

Installshield Wizard Free Download

In order to find bugs that are occurring only with certain hardware or software configurations, you may need to debug your installation on a system other than your development machine. In that case, it is not necessary to install InstallShield on that computer.

To debug the installation on a debug machine, instead of on your installation development machine:

This is the executable file for the InstallScript Debugger.

This file must be present on the debug machine in the same folder as the ISDbg.exe file.

This is the help file that you can optionally copy to the debug machine so that you can access the InstallScript Debugger help from within the debugger.

Tip: If the project files on your development machine are accessible to the debug machine over a network, you can skip step 4.

So it's a good thing that CDMediaWorld has utilities, such as i6Comp to extract the files. Just download it (I picked i6comp02.zip) and then run i6comp. This is what i6Comp looks like when listing files from the data.cab file:

C:tempInstallShield>i6comp l -v -r data1.cab
InstallShield 6.x Cabinet Util
Version 0.2 -] fOSSiL & Morlac - 2000 [-

Date Time OrigSize Attr CompSize Ind FileName
12-16-1999 10:24 28529 ____ 5841 0 corecomp.ini
09-05-2001 04:18 77824 A___ 29916 1 ctor.dll
09-05-2001 04:13 32768 A___ 4483 2 objectps.dll
...
08-22-2003 17:27 278190 A___ 264385 180 PowerDVD.CHM
09-05-2003 16:16 65536 A___ 30014 342 AudioFilterclds.dll
09-05-2003 16:16 45056 A___ 8203 343 AudioFilterclwo.dll
09-05-2003 16:16 245760 A___ 81241 344 AudioFilterCLADR.ax
09-05-2003 16:16 126976 A___ 43046 347 AudioFilterCLAuTS.ax
09-05-2003 16:25 73728 A___ 27800 348 AudioFilterCLAudioCD.ax
09-05-2003 16:25 503808 A___ 239856 349 NavFilterCLNAVX.ax
09-12-2003 18:38 520192 A___ 205346 350 VideoFilterCLVSD.ax
09-05-2003 16:16 45568 A___ 23075 351 VideoFilterCLLine21.ax
---------- ---------- -------------------
49878589 19880422 311 file(s) total

C:tempInstallShield>

The list output is more interesting than the extract output. which is why I've showed list. Other options are:

C:tempInstallShield>i6comp
InstallShield 6.x Cabinet Util
Version 0.2 -] fOSSiL & Morlac - 2000 [-

Usage: i6comp [-opts] [file index|fmask|path] [disk fmask|path]
Commands
l: list Files
g: list File Groups c: list Components t: list Setup Types
s: convert multi-volume cab to a single volume (not recommended)
e: extract files (specify when specifying )
x: same as 'e' with subdirs
r: replace files in cab (same syntax as 'e')
d: delete files from cab (specify )
a: add files to cab ( is optional; must specify -g OR -f)
z: zero-size files (specify )
Options
v: verbose info mode
r: extract subdirs/recurse and store subdirs
d: include directories in cab matches
g: specifies File Group to work with
o: suppress supplementary output (start msg, comments, etc.)
f: treat File Groups as directories (usefull for GUI, wrappers)

C:tempInstallShield>

Update: this does not work with InstallShield 12 or later. I've written a post about that here.

InstallShield 2015 » InstallScript Debugger

Installshield Wizard Free Download

In order to find bugs that are occurring only with certain hardware or software configurations, you may need to debug your installation on a system other than your development machine. In that case, it is not necessary to install InstallShield on that computer.

To debug the installation on a debug machine, instead of on your installation development machine:

This is the executable file for the InstallScript Debugger.

This file must be present on the debug machine in the same folder as the ISDbg.exe file.

This is the help file that you can optionally copy to the debug machine so that you can access the InstallScript Debugger help from within the debugger.

Tip: If the project files on your development machine are accessible to the debug machine over a network, you can skip step 4.

setup /d'C:Test'

Note that if your installation, script, and debug files are all in their original location on the development system, you do not need to specify the path to the debug file—use the following:

setup /d