Unppacking Msi and innosetup executables

[clauderenaud]

[quote="Gral"]Did you add
[code]IDPos=48 [/code]?
This is addon from innounp 0.17:
[code][InnoSetup]
Description="InnoSetup"
Archiver=C:\PROGRAM FILES\WINCMD\WCXPlugin\MultiArc\innounp.exe
Extension=exe
ID=49 6E 6E 6F
IDPos=48
Start="^--------------------------------------"
End="^--------------------------------------"
Format0="zzzzzzzzzz yyyy.tt.dd hh:mm nnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn"
List=%P -v -m %AQ
Extract=%P -e -m -c%R %AQ @%LQ
ExtractWithPath=%P -x -m -c%R %AQ @%LQ
IgnoreErrors=0
SkipEmpty=0
SkipDirsInFileList=0
SearchForUglyDirs=0
BatchUnpack=1
UnixPath=0
AskMode=0
SkipLIST=1
Debug=0

[/code]

Change only path to archiver and try.
Define any unused extension. Extension is unimportant - this lines:
ID=49 6E 6E 6F
IDPos=48
means that file is detected by content.
Associate extension with Multiarc.

Open archive by CTRL+PAGEDOWN, not ENTER.[/quote]

Here is the last lines of my multiarc.ini

[InnoSetup]
Description="InnoSetup"
Archiver=Y:\totalcmd\plugins\wcx\multiarc\addons\InnoSetup\innounp.exe
Extension=ino
ID=49 6E 6E 6F
IDPos=48
Start="^--------------------------------------"
End="^--------------------------------------"
Format0="zzzzzzzzzz yyyy.tt.dd hh:mm nnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn"
List=%P -v -m %AQ
Extract=%P -e -m -c%R %AQ @%LQ
ExtractWithPath=%P -x -m -c%R %AQ @%LQ
IgnoreErrors=0
SkipEmpty=0
SkipDirsInFileList=0
SearchForUglyDirs=0
BatchUnpack=1
UnixPath=0
AskMode=0
SkipLIST=1
Debug=0

My nnounp.Exe file is in wight place...
Doing enter or ctrl+pgdn give always the same error ...
Should I ask for technical support to the author ?

[clauderenaud]

Normal innosetup executable are well browsed now.
But I can not run them each time the unpacker runs...
And when I try to run regular executable as totalcmd.Exe I have the previously reported error.
How to solve this ?

And how to remove a extension rather than manually ?

And how to handle innosetup executable which are password protected ?

Greetings,

[clauderenaud]

Everything seems to be working well now...

But complementary question :

When we want to remove an extension do we have to do it manually or is it possible from within tc ?

How to handle password protected Innosetup files ?

[Gral]

1. Run configuration dialog for packers plugins"
(Configuration - Options - Packer - Configure packer extension WCXs)
Select extension from dropdownlist and clear field "Associate with" , press OK.
2 . I don't know.

[clauderenaud]

[quote="Gral"]1. Run configuration dialog for packers plugins"
(Configuration - Options - Packer - Configure packer extension WCXs)
Select extension from dropdownlist and clear field "Associate with" , press OK.
2 . I don't know. :([/quote]

Thanks you for your very detailed help ...

[TychoBarfy]

I think I now found a allround solution for old and new inno files. See my postings above.
My previously posted solution was to greedy. This now works with every kind of Inno Setup file. Tested it with any old and new inno files and it nomore conflicts with upx section in multiarc.ini or other exe headers.

string................<.@
This is a common string in every inno file (new and old) starting at the same position. And till now I didn't find any other non inno exe with this string at that pos.


My entries in multiarc.ini (you DON'T have to rename the exe extension):

Code: Select all

; -----------------------------------------------------------------------
; Inno Setup (3.0.0-beta through 5.1.x)
; Uses: Innounp v0.17 and higher
; Home page: http://innounp.sourceforge.net/
; Download latest version: http://innounp.sourceforge.net/get-latest-innounp.php
; -----------------------------------------------------------------------
[InnoSetup]
Description="Inno Setup (3.0.0-beta to 5.1.x)"
Extension=EXE_IS
Archiver=D:\tcmd\multiarc_packer\innounp.exe
ID=49 6E 6E 6F, 73 74 72 69 6E 67 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 3C 10 40
IDPos=48, 1026
Start="^--------------------------------------"
End="^--------------------------------------"
Format0="zzzzzzzzzz yyyy.tt.dd hh:mm nnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn"
List=%P -v -m %AQ
Extract=%P -e -m -c%R %AQ @%LQ
ExtractWithPath=%P -x -m -c%R %AQ @%LQ
IgnoreErrors=
SkipEmpty=0
SkipDirsInFileList=0
SearchForUglyDirs=0
BatchUnpack=1
UnixPath=0
AskMode=0
SkipLIST=1
Debug=0
; -----------------------------------------------------------------------

Code: Select all

; -----------------------------------------------------------------------
; UPX 124 compressed files (Ver 1.1)
; Unpacker: upx v1.24 stable
; http://web.cefriel.it/~frumento
; -----------------------------------------------------------------------
[UPX_Compress_124]
TypeName=UPX
ID=31 2E 32 34 00 55 50 58
IDPos=987
Extension=EXE_UP
Archiver=D:\tcmd\multiarc_packer\upx124.exe
Start="--------------------"
Format0="zzzzzzzzzzzzzzzzzzzzzz -> pppppppppppppppppppppp nnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn"
Extract="%P -d %FQ -o%AQAW"
;Extract="%P -d %AQAW"
List="%P -q -l --no-color %AQA"
Test="%P -t -q --no-color %FQ"
Add="%P --best -q --no-color --compress-icons=1 %FQ -o%AQ"
IgnoreErrors=0
Debug=0
UnixPath=0
SkipDirsInFileList=1
SkipEmptyNames=1
BatchUnpack=0
SearchForUglyDirs=0
AskMode=0
SkipLIST=0
; -----------------------------------------------------------------------

Here my WINCMD.INI entries for upx and inno two posts above:

Code: Select all

...
exe_up=223,%COMMANDER_PATH%\plugins\wcx\packer_plugins\multiarc\multiarc.wcx
exe_is=223,%COMMANDER_PATH%\plugins\wcx\packer_plugins\multiarc\multiarc.wcx...

NOTE: My previously posted solution was to greedy. This now works with every kind of Inno Setup file. Tested it with any old and new inno files and it nomore conflicts with upx section (see two posts below) in multiarc.ini or other exe headers.


However, if you set IgnoreErrors=1 in the [InnoSetup] section of
multiarc.ini you even don't get error messages if you try to open
an inno file version smaller than 3.0.0-beta.

The only effect is that in the opened archive there's to see something like that
in TC file window:

[cified file "Z:]
ddress 0043F654
up Setup Data (2.0.18) This is not a supported version.
withmessage:1

This could be usefull. Firstly you don't have to close any annoying popup
message; secondly you get an information about the version and you see
that you tried to open an inno file; and last not least all innos newer
or equal version 3.0.0-beta can be extracted as before.

By the way. I extracted an Inno Setup Setup Data (3.0.0a). This seams to
be a version higher 3.0.0-beta. Old innos and 3.0.0a I found on a CD from 2002.

Have fun!

[TychoBarfy]

Multiarc files without the packers
------------------------------------------

EDIT 18.01.2006:
The archive contains my multiarc folder and in addition the [xxxxxxPlugins] sections of my
WINCMD.INI to demonstrate how I use to extract my other files and how the multiarc
entries in WINCMD.INI should be. I made a lot of changes in multiarc.ini and [Packerplugins]
section of WINCMD.INI.

A small tcmd.dir is included to show my TC's internal plugin structure.

Instead of extract.exe for DDI images I want to implement UNDDI from
http://www.ii.pw.edu.pl/~borkowsm/unddi.htm

I'm in contact with the author. He said, he has less time for programing and I could compile
the EXE myself. If someone tells me what compiler to use and where to get it I would do it.
I found the lines in the source code which must be modified to let it work properly in Multiarc.

The tool works fine. But because there are empty lines at the start and at the end of the files
list it's inpossible to get it work in Multiarc.

Some remarks to gaup.wcx (Game Archive UnPacker).
If you also want to open bin images in TC delete the string ",BIN "
(without quotes) in plugininst.inf of GAUP and open BIN's with iso.wcx.
If you have already installed GAUP than change the BIN line in WINCMD.INI
and instead point to iso.wcx plugins dir.


For those who didn't use Rapidshare before.

If you enter the site after clicking the link below, scroll down and click at the Free button.
Than wait a few seconds until the little picture with the chars on it appears.

Type in these chars into the textbox (lower/upper case doesn't matter).
Note: The char which looks like zero is an o. If it's a zero its marked with a point in it.

Don't use dowload managers!!!

Here the actual multiarc.ini:
http://rapidshare.de/files/11257998/multiarc_ini.zip.html

[TychoBarfy]

One note to Inno Setup section in multiarc.ini. At

Code: Select all

Format0="zzzzzzzzzz  yyyy.tt.dd hh:mm
nnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn"

all in one line AND put 2 spaces between hh:mm AND nnnnnnn...
So date/time of files/dirs will be displaied correctly again.

[TychoBarfy]

Fixed some errors in multiarc.ini and WINCMD.INI and
added some new features. Now everything works including
UNDDI. Mariusz, the author of UNDDI was so kind to
make a new compilation.

Included in this file is multiarc.ini, plugin sections
of WINCMD.INI and the Multiarc compatible UNDDI. He plans
an other release with more comprehensive commanders-integration
and other improvements.
NOTE: Do not use unddi from athors homepage. It doesn't
work with Multiarc.

Please ignore my previous download links above.

http://rapidshare.de/files/11738388/multiarc_ini.zip.html

[TychoBarfy]

Fixed some errors in multiarc.ini and WINCMD.INI and
added some new features. There was an error in ARC
and InstallShield_6to7 sections of multiarc.ini.

Included in this file is multiarc.ini, plugin sections
of WINCMD.INI and the Multiarc compatible UNDDI.
NOTE: Do not use unddi from athors homepage. It doesn't
work with Multiarc.

Please ignore my previous download links above.

http://rapidshare.de/files/12806173/multiarc_ini.zip.html

[deus-ex]

Please ignore my previous download links above.

Instead of phrasing this sentence over and over and posting a new link every time you post an update you are better off by editing the post where you offered a download link the first time. Optionaly you could then add a link to that edited post in every update message.

Examples:

• http://ghisler.ch/board/viewtopic.php?p=42991#42991
• http://ghisler.ch/board/viewtopic.php?p=43076#43076

Regards,
deus-ex

[Hacker]

deus-ex,
After 8 days only moderators can edit posts.

Roman

[TychoBarfy]

I would, but since a few weeks I only can delete my last post and edit only if the post is not older then EDIT: 8 days.

[deus-ex]

After 8 days only moderators can edit posts.

I would, but since a few weeks I only can delete my last post and edit only if the post is not older then EDIT: 8 days.

Ehrm... okay, become a Moderator then.


Regards,
deus-ex

[ghisler(Author)]

Note to beta testers: Editing of the first post can be tried in the beta forum now. Of course moderators can always edit them, so don't try it if you're moderator.