Hex workshop 6.8 portable

broken image

But don't be a hacker! Mommy will scold you. A3X files using this method, if you so desire. You can actually extract AutoIt scripts and write them to. The UDF here allows you to detect any overlay a PE ( Portable Executable) file may have, and allows you to extract the Overlay into a separate file - or alternatively extract the exe without the overlay. While future versions of AutoIt (new beta releases and any official release after v3.3.8.1) are putting tokenized scripts into a resource within the executable, all current compiled scripts are still put together with the tokenized script appended as an overlay. And also a legit >answer to my topic in Help and Support. This project is actually a result of dealing with so-called 'File Optimizer' programs that would strip Overlay information from Executables (leaving compiled AutoIt scripts crippled!). Whatever the case is, I wanted to find a way to detect if this data was present. Or it could just be extra unneeded cruft (sometimes). This data can be important, such as setup packages, Authenticode signatures*, and overlays for AutoIt scripts. Executable and other PE files can contain 'overlays', which is data that is appended to the end of the file.

broken image