Thanks, does this decompiler even work on newer verisons?

@chronos
let it be your home work
try it and tell the community!

ther is a SID imporved version can decompile higher version installshield

Do you mean an update to this old (but gold) tool? If so, can you provide more details about it? TIA.

[sid] - installshield 6/7 script decompiler
v1.0 written by sn00pee

Can someone upload isDcc31 to somewhere else please?

here we go -

isDcc v3.1, (c) 1998 Andrew de Quincey
isDcc v2.00, (c) 2000 Mr. Smith
isDcc v2.10, (c) 2001 Mr. Smith
isDcc v3.10, (c) 2001 Mr Won't tell:)
Syntax : isDcc -u filename.inx //To Unscramble the script file
Syntax : isDcc -s filename.inx.dec //To Scramble the script file
Syntax : isDcc filename.inx.dec //To desassemble the script file


https://www.sendspace.com/file/qpfb1y

Is there any way to add the modified files to *.cab package ?
ISCAB.exe is discontinued and doesn't work with newer versions :-(

repack it

with advanced installer

capture before and after and generate msi NEW installer

no other solution no one have updated version of that tool, anyway was useless.

Tool is 7 years old. Now there are better tools to unpack installers. That tool was very good in its time.

Thanks Guys;

I will try with AI .

Rasmus - can you recommend something ?

PS. I have setup & *.cab - not *.msi
That's why I want to update *.cab (file extract is possible, but how to exchange a modified file ?)

I'm sorry for resurrecting this old topic. I am currently trying to decompile some custom actions in a msi installer. With ORCA, I see that the custom action is located in issetup.dll.

Am I right to assume that the function that is called from the installer actually then resides in setup.inx? I am trying to decompile with some older SID version, but can't find any other tools...

The setup.inx may contain the called functions.
Can you share a copy of the "setup.inx" file?

Unfortunately I cannot the share the .inx file. But I succeeded using https://github.com/darknesswind/IsDcc.git and fixing its compilation errors. With that, i was able to see which DLL-Functions where called from the script code.

Fixes were:

https://github.com/darknesswind/IsDcc/blob/master/common.h#L29

Changing that to TYPE_UNDEF5, instead of TYPE_AUTOSTRING - if I recall correctly.