Easy question, but frustrating to search on the Internet: How to set our .sys file's

Hello,

So, we've created our Authenticode signed driver deployment package, and everything looks and works great, but... I noticed that when I did a right mouse, properties on our xxxxxdriver.sys file, it shows the incorrect information for the following fields:


File version: 6.1.7600.16385 (should be 1.0.0000.0)
Product name: Windows (R) Win7 DDK driver (should be our product's name)
Copyright: (C) Microsoft Corporation. All rights reserved. (should be our copyright)

I noticed that other vendor's .sys files have their information, so it must be possible
to set it. Is there a way for us to correct these fields for our .sys file? Our .inx
file has the following information in [VERSION]

Provider=Our Company Name
Version=02/03/2011,1.0.0000.0

Thanks you for your help!

Mike

On Thu, 3 Mar 2011 06:55:10 -0500 (EST)
xxxxx@a-bit-of-help.com wrote:

I noticed that other vendor’s .sys files have their information, so
it must be possible to set it. Is there a way for us to correct
these fields for our .sys file? Our .inx file has the following
information in [VERSION]

http://www.ms-news.net/f1022/how-do-i-set-driver-version-and-description-9499690.html
explains how to set all the extra fields.


Bruce Cran

That was quite nice of me :slight_smile:

Mark Roddy

On Thu, Mar 3, 2011 at 7:49 AM, Bruce Cran wrote:
> On Thu, 3 Mar 2011 06:55:10 -0500 (EST)
> xxxxx@a-bit-of-help.com wrote:
>
>> I noticed that other vendor’s .sys files have their information, so
>> it must be possible to set it. ?Is there a way for us to correct
>> these fields for our .sys file? ?Our .inx file has the following
>> information in [VERSION]
>
> http://www.ms-news.net/f1022/how-do-i-set-driver-version-and-description-9499690.html
> explains how to set all the extra fields.
>
> –
> Bruce Cran
>
> —
> 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, Bruce, for the lead! :slight_smile:

Thanks, Mark, for the great ideas! This is my first Windows driver deployment and I was stumped about where to change this info!

Have a great day, guys, and thanks again!

Mike

You don’t need to repro all of the contents in common.ver and ntvertp.h in your own RC file, you can easily do something like this which uses all of the contents from those files as provided by the kit (from src\input\mouclass), obviously you would change the VER_ #defines

#include <verrsrc.h>

#include <ntverp.h>

#define VER_FILETYPE VFT_DRV
#define VER_FILESUBTYPE VFT2_DRV_SYSTEM
#define VER_FILEDESCRIPTION_STR “Mouse Class Driver”
#define VER_INTERNALNAME_STR “mouclass.sys”
#define VER_ORIGINALFILENAME_STR “mouclass.sys”

#include “common.ver”

#include “moulog.rc”

d

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@a-bit-of-help.com
Sent: Thursday, March 03, 2011 11:25 AM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] Easy question, but frustrating to search on the Internet: How to set our .sys file’s

Thanks, Bruce, for the lead! :slight_smile:

Thanks, Mark, for the great ideas! This is my first Windows driver deployment and I was stumped about where to change this info!

Have a great day, guys, and thanks again!

Mike


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</ntverp.h></verrsrc.h>