Driver verifier

In Verifier Dialog, there is a window to select drivers to verify.

The list control has 4 column.

  1. Verify?
  2. Driver name.
  3. Provider
  4. Version

My driver’s provider and version are represented as “unknown”.
I don’t know how can I set these values.

How can I set this value? By SignTool? Or Resource file?
Yes, this is not a big problem. But I would like to correct that.

Our driver has a rc file. The file defines following values.

VER_FILETYPE
VER_FILESUBTYPE
VER_FILEDESCRIPTION_STR
VER_INTERNALNAME_STR
VER_INTERNALNAME_STR
VER_LEGALCOPYRIGHT_YEARS
VER_LEGALCOPYRIGHT_STR
VER_ORIGINALFILENAME_STR
VER_COMPANYNAME_STR
VER_PRODUCTVERSION
VER_PRODUCTVERSION_STR
VER_FILEVERSION
VER_FILEVERSION_STR
VER_PRODUCTNAME_STR
VER_LEGALCOPYRIGHT_STR

Windows explorer represents our driver’s version and digital sign information well. But Driver Verifier doesn’t!

Let me know please.
Thanks.

> My driver’s provider and version are represented as “unknown”.

I don’t know how can I set these values.

By signing.


Maxim S. Shatskih
Windows DDK MVP
xxxxx@storagecraft.com
http://www.storagecraft.com

>

> My driver’s provider and version are represented as “unknown”.
> I don’t know how can I set these values.

By signing.

I think that signing solves a slightly different problem… don’t those
values come from the resource (rc) file? Signing just gives you some
confidence that those values are what they appear to be (and haven’t
been tampered with) based on the trust of a third party.

James

I think “3. Provider” is set up in *.inf file
A *.inf file contains the section [Version] , the field “Provider”
Some thought about your “4. Version”. The *.inf file also contains the field “DriverVer”. In *.rc file you could set up a FILEVERSION and PRODUCTVERSION. But I think “4. Version” related to a Driver version which is set up in *.inf file.

Igor Sharovar

>I think that signing solves a slightly different problem… don’t those

values come from the resource (rc) file?

At least in some UI boxes in Device Manager these values come from the signature and not from the VersionInfo resource.


Maxim S. Shatskih
Windows DDK MVP
xxxxx@storagecraft.com
http://www.storagecraft.com

I think that Igor is correct here, but it’s certainly easy enough to figure out whether the version resources are correct by looking at what explorer reports.

mm

@Maxim S. Shatskih
If signing can resolve this problem, what option should I use?

Thanks.

The option means singtool.exe’s option.

I am absolutely positive that just a .RC will solve that issue with the
Driver Verifier display by providing the information in the VersionInfo.
Signing might also do it, but I know that the .RC is enough, having done
that many times and also just fixing that same problem with someone
else’s driver just a few weeks back.

If I remember correctly, the most common reason for missing these strings from the Verifier GUI is that you didn’t install the driver image file under %windir%\system32\drivers.

Dan

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@gmail.com
Sent: Saturday, May 29, 2010 9:27 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] Driver verifier

In Verifier Dialog, there is a window to select drivers to verify.

The list control has 4 column.

  1. Verify?
  2. Driver name.
  3. Provider
  4. Version

My driver’s provider and version are represented as “unknown”.
I don’t know how can I set these values.

How can I set this value? By SignTool? Or Resource file?
Yes, this is not a big problem. But I would like to correct that.

Our driver has a rc file. The file defines following values.

VER_FILETYPE
VER_FILESUBTYPE
VER_FILEDESCRIPTION_STR
VER_INTERNALNAME_STR
VER_INTERNALNAME_STR
VER_LEGALCOPYRIGHT_YEARS
VER_LEGALCOPYRIGHT_STR
VER_ORIGINALFILENAME_STR
VER_COMPANYNAME_STR
VER_PRODUCTVERSION
VER_PRODUCTVERSION_STR
VER_FILEVERSION
VER_FILEVERSION_STR
VER_PRODUCTNAME_STR
VER_LEGALCOPYRIGHT_STR

Windows explorer represents our driver’s version and digital sign information well. But Driver Verifier doesn’t!

Let me know please.
Thanks.


NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

Thanks Taed and Dan.
I’ll try it when I get back my company. I’m on vacation.

On Sun, 30 May 2010 00:27:00 -0400 (EDT)
xxxxx@gmail.com wrote:

Our driver has a rc file. The file defines following values.

VER_FILETYPE
VER_FILESUBTYPE
VER_FILEDESCRIPTION_STR
VER_INTERNALNAME_STR
VER_INTERNALNAME_STR
VER_LEGALCOPYRIGHT_YEARS
VER_LEGALCOPYRIGHT_STR
VER_ORIGINALFILENAME_STR
VER_COMPANYNAME_STR
VER_PRODUCTVERSION
VER_PRODUCTVERSION_STR
VER_FILEVERSION
VER_FILEVERSION_STR
VER_PRODUCTNAME_STR
VER_LEGALCOPYRIGHT_STR

Windows explorer represents our driver’s version and digital sign
information well. But Driver Verifier doesn’t!

Driver Verifier displays the FileVersion string: it’s set from
VER_FILEVERSION_STR in inc/api/common.ver:

VALUE “FileVersion”, VER_FILEVERSION_STR BUILD_MACHINE_TAG_PADDED

In Vista and Windows 7 the FileVersion string doesn’t seem to be
displayed in the Windows Explorer properties window. You can also see
all the version strings by running Sysinternals’ sigcheck from
http://technet.microsoft.com/en-us/sysinternals/bb897441.aspx .


Bruce Cran

> displayed in the Windows Explorer properties window. You can also see

all the version strings by running Sysinternals’ sigcheck from
http://technet.microsoft.com/en-us/sysinternals/bb897441.aspx .

filever /v also helps.


Maxim S. Shatskih
Windows DDK MVP
xxxxx@storagecraft.com
http://www.storagecraft.com

Dan was right.

It’s displayed well.
The point was “\system32\drivers”