Project file
Extracts the project file from a compiled exe, dll or ocx, so you can see how the application was put together.
Visual Basic 4 (32-bit) · 5 · 6 — Native & P-Code
Pull the project back out of the .exe.
Semi VB Decompiler is a tool for recovering your lost Visual Basic 4 (32-bit), 5 and 6 project information from an exe, dll or ocx. It extracts the project file, all forms, API calls, procedure names, event names, and the P-Code tokens if the application was compiled to P-Code.
Looking for a Native code solution?
Semi VB Decompiler has been replaced by VB Source Code Recovery.
For the best in class VB 5/6 Native and P-Code decompiler, visit vbsourcecoderecovery.com. Excellent tool for reverse engineering and security analysis.
Go to vbsourcecoderecovery.com →
https://vbsourcecoderecovery.com/
What it recovers
Everything the compiler left behind in the file.
A Visual Basic binary still carries most of its project structure. Semi VB Decompiler reads it back out and lets you edit what it finds.
Forms & controls
Extracts all forms and resources. The built-in form and control editor lets you change properties and save the changes straight back to the file.
Procedure & event names
Recovers procedure names from forms and class files (when public), event names, and the events of the common controls.
API calls
Recovers the APIs the program calls. When the API is in the database, the full call is recovered, parameters included.
P-Code tokens
Decompiles P-Code events and procedures to tokens and attempts to convert them to VB code. Includes a full P-Code string list.
Native code offsets
Native code offset list for events, with partial disassembly to assembly listings and the string references used by each event.
Native or P-Code?
Two compile options, two levels of recovery.
Visual Basic 5 and 6 have two compile options: Native, which is turned on by default, and P-Code. How much you get back depends on which one the original developer chose.
Native Default
From a Native build, Semi VB Decompiler recovers the assembly listings of events and their string references, plus everything that lives in the VB structures: forms, controls, project information, API calls and procedure names.
Want full Native code recovery? That is what the new product is for. Visit vbsourcecoderecovery.com.
P-Code Optional
From a P-Code build you can recover a lot more detailed information about procedures and events: the P-Code tokens themselves, converted to VB code where possible, along with the complete P-Code string list.
The older Visual Basic versions 1 through 4 used P-Code as well, though in a different, 16-bit format.
Version coverage
Which Visual Basic versions it handles.
VB 4 (32-bit), 5, 6
Full support for exe, dll and ocx files, compiled to either Native or P-Code.
SupportedVB 4 (16-bit)
Not supported for decompiling, but Semi VB Decompiler is able to read part of the NE file format to get you some extra information if you desire it.
PartialVB 2, 3
Not supported by the decompiler itself. The bundled VB 1/2/3 Binary Form To Text Converter turns their binary forms into editable text.
Forms onlyVB 1
No decompiler support in Semi VB Decompiler. The Binary Form To Text Converter can read its forms.
Forms onlyVB.NET
VB.NET compiles to MSIL, a byte code a little like what Java uses, which can easily be recovered to VB.NET or even C#. Semi VB Decompiler does not decompile .NET files, but it will extract .NET information such as the CLR header and stream information: strings, GUIDs, blobs and more.
Metadata onlyWhere to go next
Looking for a Native code solution?
For the best in class VB 5/6 Native and P-Code decompiler, visit vbsourcecoderecovery.com.