84 comments on pestudio

the undersigned hereby pledge to abide by the recommendations, protocols,procedures and regulations set forth by my Right Honourable Friend Midas,the Member for TPFC's constituency,... cross my heart and hope to die... ;-)

Version 8.61 changelog:. Increase performance when loading executable with large collection of exports. Consolidate switches in settings.xml. Consolidate API classification. Fix a bug when handling the Thread-Local Storage (TLS). Fix a bug of the Manifest View. Fix a bug when detecting 64-bit managed files. Add online check of update in the "About" dialog. Add support for ARM detection. Indicate missing library. Extend features of standard version

Changelog:. Differentiate between standard and professional (pro) versions of pestudio. Added deletion of overlay. Added computation of entropy. Added detection of TLS Callback functions. Show more details about sections. Fixed bugs and crash

Unfortunately, the command prompt usage "Pestudio file:-typical.exe" is broken again in this latest version...:-( (It was working fine in previous v8.51)

This program is really quite amazing for what it does, I just wish it was easier to make sense of what a lot of what it says, if the dev is reading this, maybe you could add a context menu for google searching things, like right click> google search > kernal32.dll, or wsock32.dll for people wanting to look these things up easier. And would it be possible to have it expand on some of the features it lists, like many programs will say "The Image modifies the Windows registry" but it would be nice what its doing, if possible.

One additional thing I'd like to see is a way for it to remember the window size and location with some sort of setting.ini

Regarding my previous post - it seems there is a registry entry for a Borland Database Engine file, specifically 'idr20009.dll', which wasn't pointing to the right location. I'm not sure if PEStudio loads it or some other driver on my system, but its now working.

@navinbhai: The changelog is located within the app ZIP file. It would be better if the changelog is published on the website instead.

navinbhai2010-10-03 22:24

What a program! Daily update? Even what is updated is not known.

marc ochsenmeier2010-09-27 15:53

Version 3.22 has been made available (with a changelog). Logfile is now XML based. Debug info and certificate are detected.

marc ochsenmeier2010-09-21 17:25

This feature it planned, thanks to be patient. At this point, I have set the focus on the programmatic interface (the parser - peparser.dll). The UI, which is 'only' a client application consuming the parser, will be changed in the next...days. Please tell me why you use PeStudio, what kind of features you like...and what you are missing. Thanks.

TT2010-09-21 13:11

GUI is too large to work with Netbooks (1024x600). Any way to resize it?

marc ochsenmeier2010-09-21 12:11

@Bass Changelog. Of course I can. Cheers.

Baas2010-09-21 11:03

@marc ochsenmeierThanks for PeStudio. Can you add a changelog with each new version? Cheers.

marc ochsenmeier2010-09-21 08:46

PeStudio is still under development. It will soon provide command line parameters. It will also support more compressed files. Yes PeStudio (still) crashes when inspecting BitComet (which is compressed using PECompat). Thanks for your comments!

Emil2010-09-04 10:28

Opening BitComet.exe it crashes. When it can open BitComet.exe than it crashes at clicking on the Imported Libraries or Imported Functions.Please help. Thanks

Lyx2010-08-31 12:08

Feature proposal: Define binary that is to be opened via commandline parameter. That way, one could integrate calling this nice app into filemanagers (i just tried calling it from total commander via pestudio.exe %1, and noticed that this doesn't work).

mox2010-08-30 16:42

PeStudio has been Updated to Version 3.15 and now can start without the Visual Studio libraries. I just tried it on a clean Windows XP SP3 box and it runs.

Lyx2010-08-30 05:15

It was DLL-hell in my case, because i did already have that library installed - just not in the required version. Such situations were the main reason why MS began to store such libraries no longer centrally in system32, but instead in seperate directories, "to reduce DLL-hell."

Anyways, thank you for this great application. Looking forward to the next version.

marc ochsenmeier2010-08-29 02:21

Hi guys, sorry about that. I forgot to deliver these MSVC9 redistribuables! Next version will correct this. BTW, this has nothing to do with DLL-hell :-)

Hope you will enjoy the next version.

Lyx2010-08-28 23:34

Cool. Its kinda funny when an app that is about dynamic linking, is affected by DLL-hell :)

Doesn't launch here. Error-Dialog "The ordinal 7138 could not be located in the dynamic link library mfc90u.dll". This is a plain WinXP SP3 install that was kept very clean. I also tried downloading an mfc90u.dll version from the web and putting it in the app dir - no change.