Installshield 8.0 decompiler

View statistics for this project via Libraries. A native Python cross-version decompiler and fragment decompiler. A reworking of uncompyle6. It accepts bytecodes from Python version 3. For decompilation of older Python bytecode see uncompyle6. Uncompyle6 is awesome, but it has has a fundamental problem in the way it handles control flow. In the early days of Python when there was little optimization and code was generated in a very template-oriented way, figuring out control flow-structures could be done by simply looking at code patterns.

Over the years more code optimization, specifically around handling jumps has made it harder to support detecting control flow strictly from code patterns.

This was noticed as far back as Python 2. However all of this is complicated, not robust, has greatly slowed down deparsing and is not really tenable. Control flow needs to be addressed by using dominators and reverse-dominators which the python-control-flow project can give.

It is a lot of work. So it may take time and is on the back burner. And if it were worked on, I expect it will be a while before an approach using control flow is as good as this is for Python 3. But if decompilation is to have a future and work in Python 3. The code here can be run on Python versions 3.

The bytecode files it can read have been tested on Python bytecodes from versions 3. A GNU makefile is also provided so make install possibly as root or sudo will do the steps above. A GNU makefile has been added to smooth over setting running the right command, and running tests from fastest to slowest.

If you have remake installed, you can see the list of all tasks including tests via remake --tasks. If you want Python syntax verification of the correctness of the decompilation process, add the —syntax-verify option. However since Python syntax changes, you should use this option if the bytecode is the right bytecode for the Python interpreter that will be checking the syntax.

You can also cross compare the results with another python decompiler like unpyc There is an interesting class of these programs that is readily available give stronger verification: those programs that when run test themselves.

Our test suite includes these. I will also be posting it to my site shortly but will make it available here. Feedback appreciated. Regards, CrackZ. Attached Files isDcc31src. Find all posts by CrackZ. Thanks, that's what i need! It must be some private modification, because i don't hear about it ;-. Summary: isDcc31 decrypt script - OK, but decompile only part of file and then exit as usually no error, output only kb of 3,2mb listing.

Maybe some bug that can be corrected. PM me for example. It will be good fix this nice tool I am the "Friend" who hacked away that version and indeed it is some private modification I needed the tool for something so I wrote it. Unfortunately I had very little samples to test it with so I am not surprised that it is crashing half-way. Regards, shsan. It seems that in some case one of the value I was relying on was 0 when it was supposed to be an offset telling me the end of the code segment.

Well in that case I treat the end of the file as the end of the code segment and it seems to do the trick. Originally Posted by sweetdj. This nice decompiler still works with. But ist there a tool for extracting. I can't find anything, so may be someone can help. Hi, i can create setup. Any clues? Attached Files setup.

This is a bug in ISDev 8. It still exists in DevStudio 9. This only happens if the previous version, Visual Studio. NET , is not installed on the machine. Workaround: InstallShield Knowledge Base article Q includes a tool that activeates the integration. Status: This problem has been reported for ISDev 8. Workaround: None. The IDE view sort algorithm by filename with "-" removed is wrong.

The filenames themselves do not lend themselves to sorting in Windows Explorer, or from any other file-level tool, due to month-day-year date format, hour time format, and lack of leading zeroes on single-digit months and days.

If this was fixed, it would also fix issue a. The file-system timestamps are getting reset on every build for all previous build logs and reports. It can display two values with "key path" icons. Workaround: Change the name of the control to ErrorIcon. This happens if the DLL was built for. NET and "scan at build for. NET dependencies" is selected.

But only if the file is located on the network. Copying the file to the local hard disk avoids the error. Workaround: Copy the :NET file to the local hard disk. This results in compile errors.

Uncheck the option "Correct text case while typing language keyword. It is documented in InstallShield knowledge base article Q Not fixed in ISDev 8. You will see a Path Variable whose value contains the old name of the Visual Studio project. Update the name to reflect the new value. Module failed to register. Contact your support personnel.

Created: InstallShield tracking number: G9RC Features Appear in the Wrong Order in the Feature Tree Dialog Description: In a setup with multiple configurations, which include features based on release flags, some features may appear in the wrong order, i.

This is not consistent between projects. Workarounds: None. However such entries don't work if entered in the registry view of ISD.