![Nsis Decompiler](https://kumkoniak.com/63.jpg)
Might also be an option for a switch that you can use when you run MakeNSIS.exe, instead of coding it yourself.There are several ways to install software and also a number of different solutions to create the setup file for end users to get the product installed. Then you have never the trouble of losing the source, but having the installer that you want to decompile. Sunjammer 12th February 2003 22:06 UTC need to read more books about decompilation Its just the reverse process of compilation, and in our case that means what is done as an nsis installer runs.īut since the decompiling user only needs to extract the source code (after all, the files are extracted by the installer itself), I would include the source code and extract it automatically to the TEMP directory.Īnd when you release your program with the installer, you just remove the few lines that include and extract the source code file. ) These compilation make ma head dizzy:igor: Thanks for the info. Joel 12th February 2003 21:48 UTC Virgin at that too:) mmm, ok.īut to avoid these: many possible forms of binary data because the actual form depends on which version of makensis was used to create the exe Lets make a cool installer in the first time. If you dont know what version of makensis was used to create the installer then life becomes very difficult, and it becomes (practically) impossible if an altered makensis (it is opensource after all) was used to create the installer. In that way youd be able to determine the opcodes and parameters to each opcode that would be run, and be able to decompress the data files contained within the exe installer. Youd try to write a program that would load the installer data in the same way that the header attached to the data by makensis would go about it. Sunjammer 12th February 2003 20:26 UTC darkboy I think youve got the wrong idea about decompilation. I think that he was looking for is the script that genereted the installer.
![Nsis Decompiler Nsis Decompiler](http://dotfixsoft.com/images/vbdecompiler/vb_decompiler_105/vb_decompiler_vb6_gui_designer_2.png)
We most know the properties of the installer to know what we can do. Its very dificult(but not impossible) to reverse the project. Try to modify my IO page and when I try to recompile give errors like: Corrupted file. Joel 12th February 2003 19:37 UTC I watch the source in a HEX Editor and Resource Hacker. Sunjammer 12th February 2003 17:16 UTC That would only work for official versions, a modified source version would not be decompilable still. That versionnumber could be a number, starting at 0, going up for each CVS released. You could make this optional, so that not all NSIS installers can be decompiled unless you know the version number.
![Nsis Decompiler Nsis Decompiler](http://www.bytesin.com/software/media/screens/266099.jpg)
If the user didnt change the source, and you know the exact version the parsing will be very easy. I think that what Idimmu wants is to get the original script (or something alike).
![Nsis Decompiler](https://kumkoniak.com/63.jpg)