Products
Out soon
Recall.VBRB
This product is in the stage of testing for robustness. Given a native-code compiled Visual Basic 6 DLL or executable, it figures out where all the functions start and end, and then decompiles them one by one. An older version of VBRB exists, but this has been superceded by a version built around the new engine (Recall), which is far more accurate and robust.
In Development
Recall.Win32
VB6-compiled native-code programs are based around the Intel 80386's 32-bit architecture. This is why, with the research done into this architecture during the authoring of the VB decompiler, we were able to write the Recall engine from scratch with C/C++-compiled programs in mind, and then port VBRB 2.0 (Recall.VBRB) and the VB-specific features back on top of it.
C is easy to decompile as it is a very restricted language. However, C++ will have many restrictions. There will most likely be no class names, just a lot of C source files. However, the class structure can be reconstructed using clues, so likely class functions will be in groups, making things much easier.
Planned
Recall.Java
This isn't a top priority as there are many free Java decompilers, but porting Recall to Java enough to get useful output (from a Java program written the other month) took just a lazy Sunday afternoon.
Recall.Vax
This would be for recovery, into source code, of legacy Digital Vax systems. An interesting idea, but its commercial value is unproven. Please contact us if you have a large (+25,000 lines of code) piece of legacy Vax software. Read on for more details.
Recall.Any
We can do custom ports of Recall to whatever architecture you want. The best way to proceed would be a high hourly charge for porting the instruction set in question to Recall, then once the job was done, a cost per thousand lines. Some architectures have custom binary formats which would require decoding, along with the format of their static libraries for discovery of linked library functions. Some architectures will transfer function arguments in via registers, in which case header files are completely essential. We would require all binary libraries and textual header files used, including system header files and custom ones. If you cannot supply these without infringing on copyright, you would need to lend us an original copy or point us to a place where one can be bought.
Once we have done a large project with Recall.Any, it will then be commercially viable to offer the service to anybody, for the usual charges. We will do projects of less than 25,000 lines of code, but the hourly rate will apply. We can't say if it will be worth it with such a rate, but if your program is very large, then it will be.
However, we will not do projects of less than 25,000 lines on an architecture that has not yet been ported.