Mr. Smith
December 20th, 2000, 04:12
Hi,
I recently worked on an install shield script and I wasn't quite happy with the available tools. So I modified slightly Andrew de Quinceys installshield decompiler isDcc.
I wanted to put it on protools but couldn't contact them (email didn't work), so if you are interested contact me at MrSmith_@hotmail.com and I'll send you the package (I couldn't figure out how to attach a file to this message board :-( ). Here is a short description what's it all about.
Whatīs the problem ?
If you currently have a problem with an Installshield script file you can use either use
NaTzGULs and SiraXs wisdec, which is easy to use but has problems with many install shield scripts,
or use isDcc which can handle most scripts but that one gives you "only" the source of the script
which canīt be used immediately. Only with the install shield compiler itself can those scripts be
compiled again. Often you need the right compiler version for your script version and even then it can
be tricky to compile it.
What is the solution ?
Version 2 of isDcc prints by default some additional information for each source line which can be
helpful. Like wisdec is prints the offset and opcode for each source line. If you figured out which line
you would like to change you open the script in a hexeditor and go to the offset of that line. The things
you can change are comparisons. "if" statements like "if (lNumber1 = 0) then" have in their binary
representation somewhere a
91 for an <
92 for an >
93 for an <=
94 for an >=
95 for an =
96 for an !=
The other thing which can be changed are lines like "lNumber1 = lNumber0 = 12". Here you find at the
binary level.
01 for an <
02 for an >
03 for an <=
04 for an >=
05 for an =
06 for an !=
After you made the necessary changes you have to correct the CRC which is best be done with mkcrc
by Sebastian Apel which I have included.
Oh yes, if you need the old behaviour you can always start isdcc2 with
isdcc2 -classic bla.ins
Mr. Smith
I recently worked on an install shield script and I wasn't quite happy with the available tools. So I modified slightly Andrew de Quinceys installshield decompiler isDcc.
I wanted to put it on protools but couldn't contact them (email didn't work), so if you are interested contact me at MrSmith_@hotmail.com and I'll send you the package (I couldn't figure out how to attach a file to this message board :-( ). Here is a short description what's it all about.
Whatīs the problem ?
If you currently have a problem with an Installshield script file you can use either use
NaTzGULs and SiraXs wisdec, which is easy to use but has problems with many install shield scripts,
or use isDcc which can handle most scripts but that one gives you "only" the source of the script
which canīt be used immediately. Only with the install shield compiler itself can those scripts be
compiled again. Often you need the right compiler version for your script version and even then it can
be tricky to compile it.
What is the solution ?
Version 2 of isDcc prints by default some additional information for each source line which can be
helpful. Like wisdec is prints the offset and opcode for each source line. If you figured out which line
you would like to change you open the script in a hexeditor and go to the offset of that line. The things
you can change are comparisons. "if" statements like "if (lNumber1 = 0) then" have in their binary
representation somewhere a
91 for an <
92 for an >
93 for an <=
94 for an >=
95 for an =
96 for an !=
The other thing which can be changed are lines like "lNumber1 = lNumber0 = 12". Here you find at the
binary level.
01 for an <
02 for an >
03 for an <=
04 for an >=
05 for an =
06 for an !=
After you made the necessary changes you have to correct the CRC which is best be done with mkcrc
by Sebastian Apel which I have included.
Oh yes, if you need the old behaviour you can always start isdcc2 with
isdcc2 -classic bla.ins
Mr. Smith