[WLX] fileinfo 2.23 x32/x64 (May 2017)

[fg_2002fr]

Hi all,

A long time since I updated this plugin. this release fixes several bugs.

2.23 - 18.05.2017
- Fixed : ListLoadNext not really working (content not changed)
- Fixed : Pointer moved to arbitrary location
- Fixed : Missing values in "Manifest"
- Fixed : Crash in "Image File Header" on some DLL
- Fixed : Crash in "Image File Header" with option "Relocations" (Dump_Pdata)
- Fixed : Some memory leaks

size is ~1MB
You can download it here: http://fg.tcplugins.free.fr/wlx_fileinfo223.zip

see webpage at:
http://fg.tcplugins.free.fr/

[Peter]

Thanks François,

I use the plugin since a long time.

Peter

[EricB]

Hello François,

When I download I still get the 2.2.2 version served? I've already cleared my cache, but to no avail...

Regards, EricB

[VSB]

2fg_2002fr
Wrong link (222 instread 223)

Still no support for latest mangling scheme (rvalue references, etc.)

Bug: no horizontal scroll on imports tab when Lister window is maximized

[fg_2002fr]

Oooops, sorry!
the link is restored to the right file.

[tbeu]

Most missing feature: In tab Imports/Exports copy the function names to clipboard. This would save me some redundant work to open the binary in depends (Dependency Walker) again.

Any chance to see it implemented? Big thank you!

[TychoBarfy]

Hi François,
Thanks for this great plugin first.

I use both x32 and x64 version of TC.

In x64 version of TC version 2.2.3.0 of fileinfo.wlx64 is not called, if I want to take a look for information of dll or exe files.

c:\totalcmd\Plugins\wlx\Fileinfo\
fileinfo.ini 307 2018.4.13 11:26.12
fileinfo.wlx 299008 2017.5.18 8:33.26
fileinfo.wlx64 398848 2017.5.18 8:33.20
ReadMe.txt 17516 2017.5.18 8:18.34
cadt.dll 19456 2012.1.29 10:48.56
unaspack.dll64 12288 2012.1.15 18:40.38
unaspack.dll 11264 2012.1.15 18:40.36
unupx.dll 172296 2009.10.14 18:58.56
plugins.txt 2174 2004.9.1 16:8.8

Content of fileinfo.ini:
[Options]
Autosave=0
Disassemble=1
Dump_res=0
Dump_Pdata=1
Dump_reloc=1
MaxDepth=2
RememberAP=0
ShowDebug=1
Sort=1
Undecorate=1

[plugins]
0=%COMMANDER_PATH%\plugins\wlx\fileinfo\unaspack.dll
1=%COMMANDER_PATH%\plugins\wlx\fileinfo\unupx.dll
2=%COMMANDER_PATH%\plugins\wlx\fileinfo\cadt.dll

[ghisler(Author)]

fileinfo.wlx is a lister plugin. Please check the [ListerPlugins] section whether there is a line like this:
0=%COMMANDER_PATH%\plugins\wlx\fileinfo\fileinfo.wlx

Total Commander will automatically use the wlx64 plugin when you specify just the .wlx extension.

[TychoBarfy]

[ListerPlugins]
...
3=%COMMANDER_PATH%\Plugins\wlx\fileinfo\fileinfo.wlx
....

TC x64 only shows binary view.

[Dalai]

2TychoBarfy
There are statically and dynamically linked versions (for both 32 and 64 bit) of FileInfo. A TC plugin can only be loaded successfully when all dependencies are met. According to your directory listing above, you're using the dynamically linked versions of FileInfo. They depend on the Visual C++ 2008 runtimes. Is it possible that your system has installed only the Visual C++ 2008 x86 (32 bit) runtimes? If so, you should be able to solve the issue by either installing the VC++ 2008 x64 runtimes, or by using the statically linked FileInfo plugin.

Regards
Dalai

[TychoBarfy]

Installed the x64 libraries and it worked.
Now I took the static ones. It works too, thanks.

[Hurdet]

Do it is possible to have tree items in "DLL Dependency" tab already opened without have to click it?

[Hurdet]

ty for the suggestion, but even so tree remain closed.

[DVV]

I noticed that FileInfo became much slower in analyzing modules under Windows 10 Pro (I had updated to Win 10 from Win 7).
For example, in Win 7 it tooked less than a second to analyze an .exe file and show the dlls it depends on.
In Win 10 the very same action takes about 5 seconds!
Any hints on how to improve this?

[Horst.Epp]

I noticed that FileInfo became much slower in analyzing modules under Windows 10 Pro (I had updated to Win 10 from Win 7).
For example, in Win 7 it tooked less than a second to analyze an .exe file and show the dlls it depends on.
In Win 10 the very same action takes about 5 seconds!
Any hints on how to improve this?

I would not even think about such a useless improvment.
How often do yo make that ?