[ZoSTeR]

With InnoUnp, the Inno Setup Unpacker you can not only unpack the files inside an IS but you also get a *part* of the setup script.

Here's an example of how to repack SpywareBlaster 3.0

To get the setup script:
innounp.exe -i sblaster_setup.exe >sblaster.iss

To get the files:
innounp.exe -x sblaster_setup.exe

The extracted script only contains file, registry and run settings. All advanced features are removed.


To add shortcuts and remove the starting of SB after a silent setup edit the sblaster.iss directly or with ISTool.

Add/change:

[Setup]
...
DefaultGroupName=SpywareBlaster

[Run]
Filename: {app}\spywareblaster.exe; Description: Run SpywareBlaster; Flags: skipifsilent

[Icons]
Name: {group}\SpywareBlaster; Filename: {app}\spywareblaster.exe; WorkingDir: {app}; IconFilename: {app}\spywareblaster.exe; IconIndex: 0
Name: {group}\SpywareBlaster AutoUpdate Configuration; Filename: {app}\sbautoupdate.exe; WorkingDir: {app}; IconFilename: {app}\sbautoupdate.exe; IconIndex: 0; Parameters: -config
Name: {group}\SpywareBlaster Help; Filename: {app}\sbhelp.chm; WorkingDir: {app}

Now compile the script and test it.

This method only works with very basic setups but InnoUnp seems to get updated frequently so keep an eye on it's site.

PS: This also works with Ad-Aware Pro

[XtremeMaC]

nice!!
do u know a way to extract the installshield executables msi files?
I mean they come with .exe and bunch of cab files.
i want to edit them but since they're distributed to "cd-rom" i cannot edit it. any way around it?

[mazin]

Does unpacking Ad-Aware help in solving the problem of the password?

[evilvoice]

Ok, I did this with KLR 007, but it wont compile...In Inno Setup 4 it complains about languages, then about components...In IsTool it cuts off half of my iss file because it cant handle the binary value of registry. Can Someone help me???? Please?

nevermind, got it...though it isnt exactly the same as the old exe, but it looks like it worked

[ZoSTeR]

mazin, on Apr 6 2004, 04:24 PM, said:

Does unpacking Ad-Aware help in solving the problem of the password?

Yes.

@XtremeMac
I'm not quite sure what you mean. The stuff here is only for Inno Setup based installers.
Installshield can create msi based installations and exe / cab based. You can extract Installshield cabs (very different from MS cabs btw) with special unpackers but i don't think you can edit the installation like with msi files.
Do you have any particular program in mind?

[mazin]

ZoSTeR, on Apr 6 2004, 11:26 PM, said:

mazin, on Apr 6 2004, 04:24 PM, said:

Does unpacking Ad-Aware help in solving the problem of the password?

Yes.

Well! Come on, ZoSTeR.

I'm interested in this.

[Alanoll]

XtremeMaC, on Apr 6 2004, 03:50 PM, said:

nice!!
do u know a way to extract the installshield executables msi files?
I mean they come with .exe and bunch of cab files.
i want to edit them but since they're distributed to "cd-rom" i cannot edit it. any way around it?

the problem with Installshield and when they are in the cab/exe form is that there is also a compiled installscript that you can't edit real easily.

You can find a program to extract the cabs, but you'd have to completely recreate the setup in MSI. It's like the Nullsoft Installer. Pain in the butt to mod.

[XtremeMaC]

i knew it dang
do u have a program for the cab's cause i cannot open them.
well actually that'd be so hard to start from scratch. they've too many files. (1 way would be repacker but not for what i'm interested in doing.)

[ZoSTeR]

mazin, on Apr 7 2004, 05:39 PM, said:

Well! Come on, ZoSTeR.

I'm interested in this.

I posted the script here on Apr 2 2004. You even answered that you'll check it soon.

Just use the method above and then compare the two scripts.
It's just some minor additions.

[ZoSTeR]

For unpacking Install Shield cabs you can use ZipScan or the Installshield Cabinet Viewer from IS DevStudio (is available for evaluation at IS)

[XtremeMaC]

nice proggie
THanks!!!

[ZoSTeR]

But be careful. There's actually a lot more information in the .hdr file (e.g folders). For best results i would use the official IS cab viewer.

[mazin]

Yes! I checked it, immediately, that day. I can't be patient when it comes to learning.

That day, I nearly downloaded everything on that site and even its relatives and neighbors!

I played with those programs but didn't understand anything; perhaps, because it was all new to me.

But now, I've just re-visited my thread and understood everything in a second. I returned to my C:\Program Files\Lavasoft\Ad-aware 6\ and did it.

I'd say: What's that CRAZY?!

Where have you got that idea?! It's really a charm!

Million thanks to you, ZoSTeR.

[ZoSTeR]

Here's the complete script for repackaging SpywareBlaster 3.1 (incl. innounp and start batch).

Inno Setup must be installed.
Put the three files and spywareblastersetup.exe in an empty folder.
Run StartMe.bat
Inno Setup should come up.
Choose compile and get the new setup exe from the output subfolder.

Use /VERYSILENT for installation.

Attached File(s)

•  Repack_SB31.zip (92.43K)
  Number of downloads: 295

[evilvoice]

what does it mean when i get incompatible version when running innounp on certain inoo setup installers? It says version is 4.2.1 and internal is 4201...but whne i check istool and innosetup they both say their version is 4.2.1 (I installed both because I was having problems getting KLR to run on istool and thought the real inno setup would fix it, but it didnt, so I changed a bunch of things) TIA

XtremeMac, there is a installshield decompiler here http://protools.anti...decompilers.htm I would take a look at those, I have not yet as I just found it, but I am going to soon...the only thing I can see is there is a version it doesnt go past, so if the installer is made with a newer version, it prolly wont work, but there ya go.

[ZoSTeR]

The current version of innounp only supports IS versions up to 4.1.8

[Narag]

There's version 0.08 of InnoUnp which supports Inno Setup versions up to 4.2.1
:-)

[Shannon]

Hey, do you know of anything that will unpack NSIS installers?

[CoffeeFiend]

@ZoSTeR: thank you VERY, VERY MUCH!

After looking for a simple way to install extreme movie manager for a while you came up with my answer!

-I couldn't really repack it, as there was a bunch of unknown runtime DLLs (and nowhere was a list of them to find...)
-You couldn't use AutoIt either as, you would get messageboxes for every tuntime DLL that's already on your system. Not always for the same DLLs, and not always the same messageboxes...

Anyways, it was VERY frustrating to even think about it! Until I found out it's using INNO setup and that I remembered your post.

Now that I unpacked it, I know exactly how to proceed:
-The program files can just copied over (ie: $OEM$\$Progs) or make a sfx with them (including your current DB)
-There are no registry entries
-We also have to remember the start menu shortcuts
(Or even better - use /SAVEINF so it doesn't install the runtimes, it works great)
-Finally, we can recopy DLLs without overwriting (just the ones missing from the list, and regsvr32 when needed, which is easy to do with a .cmd or vbscript...)

I got the list of runtime DLLs (already!! 41 of them)

ASYCFILT.DLL	(VB Runtimes)
CMCTLIT.DLL	(VB Runtimes)
COMCAT.DLL	(could be unsafe to install)
ComCtl32.ocx	(VB Runtimes)
COMDLG32.OCX	(VB Runtimes, not safe to overwrite)
DAO360.DLL	(part of MDAC, and let's hope that app doesn't use DAO... scary!)
DOWNLOADCONTROL.OCX	(can't find any references to that, must be renamed)
expsrv.DLL	(part of MDAC)
MSCMCIT.DLL	(VB Runtimes)
Mscomctl.ocx	(VB Runtimes)
msexch40.DLL	(part of MDAC)
msexcl40.DLL	(part of MDAC)
MSFLXGRD.OCX	(VB Runtimes)
mshtml.TLB	(comes with IE)
MSINET.ocx	(old internet xfer control)
msjet40.DLL	(part of MDAC)
msjetoledb40.DLL	(part of MDAC)
msjtes40.DLL	(part of MDAC)
msltus40.DLL	(part of MDAC)
mspbde40.DLL	(part of MDAC)
msrd2x40.DLL	(part of MDAC)
msrd3x40.DLL	(part of MDAC)
msrepl40.DLL	(part of MDAC)
mstext40.DLL	(part of MDAC)
MSVBVM60.DLL	(VB Runtimes, could be unsafe to install)
MSWinsck.ocx	(old winsock control)
msxbde40.DLL	(part of MDAC)
OLEAUT32.DLL	(could be unsafe to install)
OLEPRO32.DLL	(could be unsafe to install)
RCHTXIT.DLL	(VB Runtimes)
RICHED32.DLL	(not safe to overwrite)
RICHTX32.ocx	(VB Runtimes)
STDOLE2.TLB	(could be unsafe to install)
TABCTIT.DLL	(VB Runtimes)
TABCTL32.ocx	(VB Runtimes)
VB6IT.DLL	(VB italian file...)
WININET.DLL	(already on any system with IE4+, not safe to overwrite)
winmm.DLL	(old multimedia dll)
xpControlAdv01.ocx	(can't find any references to that, must be renamed)
xpControlAdv02.ocx	(can't find any references to that, must be renamed)
xpControlBase.ocx	(can't find any references to that, must be renamed)

(Right now I'm even considering rebuilding it, using the onlyifdoesntexist flag and no confirmoverwrite flags... That should fix it)

Anyways, you made this possible

[edit] after going thru all this, when I look at the list of DLLs, it's sad to say that all of it except about a half dozen OCX'es shouldn't be needed on most systems... Lots of very old stuff too (Win 3.1/DAO technology "under the hood" type of app)

[CoffeeFiend]

Just in case someone stumbles across this again...

innounp.exe (v0.14) had different switches now, -x will extract all the files and the script

Repacking with a modified script worked well, but I had more changes to do than I thought I would have to (most likely because the original is packed with an older version)

Things I had to change:

I Had to add

DefaultGroupName=eXtreme Movie Manager

at the top of the script to fix the install group name.

Types also gave me some problems. They were comma separated:

Name: "main_program"; Description: "Main Program Files"; Types: custom,compact,full;

The commas have to be replaced by spaces like such:

Name: "main_program"; Description: "Main Program Files"; Types: custom compact full;

Else it won't even compile.

I also had to add a [Types] section before [Components]:

[Types]
Name: "full"; Description: "Full installation"
Name: "compact"; Description: "Compact installation"
Name: "custom"; Description: "Custom installation"; Flags: iscustom

Also, some "dangerous" DLLs (like WININET.DLL, which probably shouldn't be included anyways...) had to have the allowunsafefiles flag added for the project to compile.

DLL wise, I noticed also that the installer overwrites blindly DAO360.DLL with the included version (no version checking, rather unprofesionnal of them). I changed it to onlyifdoesntexist instead. (let's hope it doesn't REALLY rely on DAO for database... scary thought!)

Finally, somehow when I use it with /SP- /VERYSILENT (no need for /LOADINF anymore) it still runs the app after installing. So I had to take out the [Run] section...

(I decided to leave the desktop icon in there and to delete it post-install)

To sum things up, I wouldn't say it was hard to fix by any means, but it sheds some light on a sub par installer. The app itself might be good but the author ought to fix the installer - the runtimes part anyways...

As a reward, I get a functionnal (and unattended) non-broken, non system files overwriting installer. I had been waiting on that for all too long. One less of my few "problem apps" to install on my to-do list (at least, most others can be easily captured/repackaged) Inno setup is quite nice after all. I might use it more soon

[edit] After finally including it on a unattended disc. It turns out it will prompt for some of the DLLs (mostly MDAC ones) to keep/replace still. I'll try adding onlyifdoesntexist to all the system DLLs or perhaps taking the obviously useless out (might be a better option after all...) Oh well.