InstallShield 10

[pibrox]

Is there a plugin available to extract files from setup.exe?
It is a InstallShield 10 file.

[Gral]

I'm not sure. Can you post link to example file(s) ?

[Hacker]

pibrox,
Maybe InstallExplorer can help.

HTH
Roman

[TychoBarfy]

Can anybody else confirm that TC crashes without any error message after Ctrl+PgDn on this setup.exe?
And if so, what plugin or what else coul be the cause?
I tried to deactivate one packer plugin after the other.

http://rapidshare.de/files/33699649/setup-InstallShield-7.1.100.1248.zip.html
File size: 53 kb

[TW]

nothing happens here.

this is really only a launcher, there are no files inside.

[TychoBarfy]

Now I've got it. It was
msi=511,%COMMANDER_PATH%\plugins\wcx\instexp\InstExpl.wcx

Is there something wrong with my flag?

[deus-ex]

Now I've got it. It was
msi=511,%COMMANDER_PATH%\plugins\wcx\instexp\InstExpl.wcx

Is there something wrong with my flag?

Did you set that flag value by yourself?

• If so, can you tell what the value stands for?

Looks like nonsense to me, eg. "all and every available flag is set, it sure can't hurt".

Why do you use 'InstExpl' cr*p for MSI in the first place, when there is a very good plugin available specialized on just that format?

TW is right, mentioned <setup.exe> is the original InstallShield Setup Launcher v7.1.100.1248 from the InstallShield Setup suite and does not contain any files. InstallShield Setup consists of several more files which on their own occupy a lot more space than just the ~100k of the Launcher, let alone the data to be installed which is stored in InstallShield CAB-files. The launcher by itself is pretty useless without the missing files and of course can't do anything for you.

[TychoBarfy]

Thanks for your answer deus-ex.

Now I've got it. It was
msi=511,%COMMANDER_PATH%\plugins\wcx\instexp\InstExpl.wcx

Is there something wrong with my flag?

Did you set that flag value by yourself?

• If so, can you tell what the value stands for?

Looks like nonsense to me, eg. "all and every available flag is set, it sure can't hurt".

You're right, I set rhe flag manually after reading some post of any tc power user (guru) here in this forum .
Now I had TC set this flag. The crash still remains if I let the resextract.wcx entry stay below the InstExpl.scx entry.
But read more below, please.

Why do you use 'InstExpl' cr*p for MSI in the first place, when there is a very good plugin available specialized on just that format?

For InstExpl cr*p is the only packer plugin which shows and extracts all file names and folder structure of msi files correctly, which msi.wcx and msi-plus.wcx do'nt.

TW is right, mentioned <setup.exe> is the original InstallShield Setup Launcher v7.1.100.1248 from the InstallShield Setup suite and does not contain any files. InstallShield Setup consists of several more files which on their own occupy a lot more space than just the ~100k of the Launcher, let alone the data to be installed which is stored in InstallShield CAB-files. The launcher by itself is pretty useless without the missing files and of course can't do anything for you.

I know, but in this case rather resextract.wcx should offer icons and other resources.
Now I've put the enty of resextract.wcx ro the top of the list and let msi with InstExpl.wcx at its place in the alphabetically sorted list.
No TC crash in case of Ctrl+PgDn with this setup.exe anymore and resextract.wcx shows me the sources as it should when no other plugin for unknown exe format is found .

Code: Select all

[PackerPlugins]
exe_UPX=223,%COMMANDER_PATH%\plugins\wcx\packer_plugins\multiarc\multiarc.wcx
exe_NSIS=223,%COMMANDER_PATH%\plugins\wcx\packer_plugins\multiarc\multiarc.wcx
exe_IS=223,%COMMANDER_PATH%\plugins\wcx\packer_plugins\multiarc\multiarc.wcx
exe_RK=223,%COMMANDER_PATH%\plugins\wcx\packer_plugins\multiarc\multiarc.wcx
exe_SQX=95,%COMMANDER_PATH%\plugins\wcx\packer_plugins\sqx\totalsqx\totalsqx.wcx
exe_UHA=223,%COMMANDER_PATH%\plugins\wcx\packer_plugins\multiarc\multiarc.wcx
pe_res=479,%COMMANDER_PATH%\plugins\wcx\packer_plugins\pe_res\resextract.wcx
...
msi=68,%COMMANDER_PATH%\plugins\wcx\packer_plugins\instexp\InstExpl.wcx

 

At the end I think its a retrieval bug in InstExpl.wcx.

[deus-ex]

So i take it you don't know what the flag value stands for. Here is a list of the flags and values. Enabling all flags results in a total of 511.

Code: Select all

Packerplugin configuration flags:

PK_CAPS_NEW        =   1  can create new archive
PK_CAPS_MODIFY     =   2  can modify exisiting archive
PK_CAPS_MULTIPLE   =   4  archive can contain multiple files
PK_CAPS_DELETE     =   8  can delete files
PK_CAPS_OPTIONS    =  16  supports the options dialogbox
PK_CAPS_MEMPACK    =  32  supports packing in memory
PK_CAPS_BY_CONTENT =  64  detect archivetype by content
PK_CAPS_SEARCHTEXT = 128  allow searching for text in archives created with this plugin
PK_CAPS_HIDE       = 256  show as normal file, hide packer icon (open with Ctrl+PgDn, not Enter)

• Especially you probably don't want to hide the packer icon (value 256) for MSI-files as it helps spotting archive files in large filelists.
• InstExp can't create MSI-files (value 1) so the total sum of the flag value has to be even in any case (eg. not 11, 33 ..., but 10, 32 ...).

In conclusion the correct flag value for MSI with InstExp is: 64 (detect archive type by content) + 4 (archive can contain multiple files) = 68.


Placing resextract.wcx somewhere in between the other packer plugins likely disables TCs ability to open certain SFX-archives.

________
Regards,
deus-ex

[TychoBarfy]

2deus-ex, thanks for your list and explanation.
I even had the list somewhere and knew, that it can be found at the Wiki.
http://www.ghisler.ch/wiki/index.php/GetPackerCaps

I'll walk through my complete [PackerPlugins] section once again.

Placing resextract.wcx somewhere in between the other packer plugins likely disables TCs ability to open certain SFX-archives.

Your right, I noticed it when I wanted to extract a 7-zip sfx today.
Moved it to the bottom of the section.

A good idea was to add 256 to the flag's value.

cu
TychoBarfy
[/quote]

[XPEHOPE3KA]

2deus-ex
Install Explorer isn't crap. It does its job correct while far plugins don't
But for msi of course I use msi-plus...

2TychoBarfy

For InstExpl cr*p is the only packer plugin which shows and extracts all file names and folder structure of msi files correctly, which msi.wcx and msi-plus.wcx do'nt.

Gimme an example.

[TychoBarfy]

...
2TychoBarfy

For InstExpl cr*p is the only packer plugin which shows and extracts all file names and folder structure of msi files correctly, which msi.wcx and msi-plus.wcx do'nt.

Gimme an example.

All, in msi.wcx and msi-plus.wcx I only see the stream names of the files, not the real names.
In InstExpl I see the real names. Or did I oversee something?

[deus-ex]

TychoBarfy is right.

I tested InstallExplorer with the MSI-file of ACDSee which gets stored to your HD upon installation (MSI-file inside the installer can't be opened due to encryption which was introduced by Microsoft with MSI v3.0).

InstallExplorer displays and extracts the files structured in folders with correct names and filesizes. MSI-Plus just displays streams and allows to extract the whole file container (data1.cab) at once only.
Opening extracted data1.cab (MSCF) you are presented to a listing with all files in the root (no subdirs) containing lots of file entries made of 32 alphanumeric chars and a leading _ (eg. _01CBB1D331B24AE5A5A9D4EA52EF3741) thus requiring you to find out the correct filenames yourself.

I witnessed this using MSI-Plus with many MSI-files hence InstallExplorer brings quite an improvement.

________
Regards,
deus-ex

[byblo]

InstallExplorer, like IEtotal, extracting zero byte file in some cases from msi archives : http://download.microsoft.com/download/9/c/0/9c060978-3ed3-4d42-9940-b7b44adcf893/XLVIEWER.EXE

[TychoBarfy]

InstallExplorer, like IEtotal, extracting zero byte file in some cases from msi archives : http.....

What do you mean with "zero byte file"?
I didn't see any zero byte file in the exe you linked to.

2deus-ex, finally someone who understands me (and the programmer of InstExpl.wcx "Domo")
http://www.totalcmd.net/plugring/InstallExplorer.html