The big question: what is version.dll and is it spyware, a trojan and if so, how do I get rid of Version Checking and File Installation.However, removing Version Checking and File Installation may adversely impact your system.
Get Dll Version .Dll And IsMany spyware malware programs use filenames of usual, non-malware programs. If we have included information about version.dll that is inaccurate, we would greatly appreciate your help by leaving a comment with the correct information below and well do our best to correct it. Anyway, Im going to just stick with calling GetFileVersionInfo once when my DLL is loaded and cache the value. Using VC 7.0.9466. Visual C that automatically increments the SpecialBuild entry within your. If in doubt please contact the author via the discussion board below. VerQueryValue(), like strtok(), perforates the versionInfo by padding the 0 character for StringFileInfo sections. Get Dll Version Code Might HaveThat means, it attempts to write to protected data - GPF I think, Lutz code might have run under an earlier windows version, but nowadays it fails. The protection fault occurs even if you write a single byte to the versionInfo buffer yourself, like in HGLOBAL hGlobal LoadResource( hLib, hVersion ). It is Simple-Chinese, but it provides the same thinking to get version number. The codes provided by web side presents the feature to get version of dll module. It is well known how to get version info from a file (EXE or DLL containing version resource) using GetFileVersionInfoSize, GetFileVersionInfo, VerQueryValue, etc. The whole point of the articel was to get the version resource directly, without going back to the disk file, in the same way you can get string resources and other resources. Im speaking specifically about VerQueryInfoA not unicode version here. First, it will write inside the first parameter (const LPVOID pBlock), so passing the pointer from LoadResource is a big no no. You just tried to write to a read-only memory mapped file (the DLL). VerQueryInfoA uses space AFTER the end of the resource to write the ASCII version of the version string, and returns to you a pointer (LPVOID lplpBuffer), that is in the memory AFTER the end the resource. You must allocate a new block that is (LenOfResourceFromSizeofResource 2) 4 bytes long according to reactos. You then must copy the resource from the LoadResource pointer (which is to the read only mapped PE file) to begining of your new malloced block. The pointer returned will be malloced block AFTER the resource. You also need to wrap all your static string with T() in other functions too. Infact this func gave up and just returned a blank string. Odd. Actually the application GetVersion.Exe was intended to be just a demo on how to your this class. Further more, Im not developing with VS.NET. Sorry again, Luetz Hartmut Luetz-Hawranke tetronik GmbH AEN. According to this recent article: you shouldnt be using ANYTHING other than GetFileVersionInfo for the parameter to VerQueryValue. Still, I gave it a shot in my project, and while it works in Debug mode, in the Release compilation, the call to VerQueryValue seems to just. I have a call to log an Event Viewer entry before the call, which I see, and after the call, which I dont see. Anyway, Im going to just stick with calling GetFileVersionInfo once when my DLL is loaded and cache the value. Using VC 7.0.9466.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2020
Categories |