I got something I'm trying to work on that's confusing me. I got a sample of a VerQueryValue app basically working, but I run across a few files that the app doesn't work on. Is there a new standard/change of this function that needs to be called for these files to be able to properly read the extended information?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
VerQueryValue Issue
- Thread starter Glenn9999
- Start date
- Thread starter
- #2
DelphiAaron
Programmer
Could it be in the way your retrieving the information not the file your retrieving the information from.
have a look at this.
Aaron Taylor
John Mutch Electronics
have a look at this.
Aaron Taylor
John Mutch Electronics
- Thread starter
- #4
Thanks for the help, aaronjme, but I already got this one figured out now.
Actually that page, and the Win32 SDK descriptions is where I started from in trying to learn how to handle the version information. I can say from debugging this problem and everything that I probably understand a bit more than what that page has - to wit I can point out a couple of problems with the code on the page (one of them being what I run into).
To describe the problem, the answer lies perhaps a little bit in both of those things. The problem I was encountering was in handling MSI executables. Basically these are OLE containers, which by Microsoft standards must *always* be unicode. I was starting with that code sample on that page, which uses ANSI characters, so naturally the standard executables would work, but the MSI executables don't. After I figured out the unicode issue, I tried it that way but had a minor bug - I fixed it just now and all of them work.
On to see if I can solve the other problem I saw, and then to get it into unit form
Actually that page, and the Win32 SDK descriptions is where I started from in trying to learn how to handle the version information. I can say from debugging this problem and everything that I probably understand a bit more than what that page has - to wit I can point out a couple of problems with the code on the page (one of them being what I run into).
To describe the problem, the answer lies perhaps a little bit in both of those things. The problem I was encountering was in handling MSI executables. Basically these are OLE containers, which by Microsoft standards must *always* be unicode. I was starting with that code sample on that page, which uses ANSI characters, so naturally the standard executables would work, but the MSI executables don't. After I figured out the unicode issue, I tried it that way but had a minor bug - I fixed it just now and all of them work.
On to see if I can solve the other problem I saw, and then to get it into unit form
- Status
Similar threads
- Locked
- Question
- Locked
- Question