[Update] MiTeC EXE Explorer 3.7.4

[Allan Higdon]

"MiTeC EXE Explorer reads and displays executable file properties and structure. It is compatible with PE32 (Portable Executable), PE32+ (64bit), NE (Windows 3.x New Executable) and VxD (Windows 9x Virtual Device Driver) file types, as well as .NET executables.

The program identify compiler and packer/protector, enumerates introduced classes, used units and forms for files compiled by Borland compilers. It contains powerfull Resource Viewer that is able to abalyze and display all basic resouce types and some extra ones as JPEG, PNG, GIF, AVI, REGISTRY and Type Library viewer that enumerates all objects and creates import interface unit in Object Pascal language. Every type of resource can be saved to file.

Program data can be output to a text report."

https://www.portablefreeware.com/index.php?id=2857

Home Page
https://mitec.cz/exe.html

3.7.4 17.12.2024
* Exceptions for 64bit fixed

[JJ]

Post by Allan Higdon
"MiTeC EXE Explorer reads and displays executable file properties and structure. It is compatible with PE32 (Portable Executable), PE32+ (64bit), NE (Windows 3.x New Executable) and VxD (Windows 9x Virtual Device Driver) file types, as well as .NET executables.
The program identify compiler and packer/protector, enumerates introduced classes, used units and forms for files compiled by Borland compilers. It contains powerfull Resource Viewer that is able to abalyze and display all basic resouce types and some extra ones as JPEG, PNG, GIF, AVI, REGISTRY and Type Library viewer that enumerates all objects and creates import interface unit in Object Pascal language. Every type of resource can be saved to file.
Program data can be output to a text report."
https://www.portablefreeware.com/index.php?id=2857
Home Page
https://mitec.cz/exe.html
3.7.4 17.12.2024
* Exceptions for 64bit fixed

This is probably the only program of its kind which support 16-bit, 32-bit,
and 64-bit modules. But not quite detailed on providing non 32/64 bit
Windows module information.

And oh... I managed to cause an "unhandled error" with an old DOS EXE.