Hi,
Not sure if this is the right place to post this…But I have a small problem with an INX file I wrote for my driver.Under the [Version] section, I have given the DriverVersion as follows,
DriverVer=4/25/2007,1.0.0
However, when I build the driver the INF file I get has a different version number.
DriverVer=4/25/2007,6.0.5384.4
As this is just a sample driver, I’m using the KMDFSamples.cat file. My WDK version is 5384 and I am doing a checked build of the driver on a x86 platform for XP.
This is not that serios an issue but I was just curious as to why the version number changes. Is this how it was designed to be?
Your makefile (see makefile.inc) uses stampinf to generate the inf file from the inx file.
I think the -v option is what you want to change.
USAGE:
stampinf -f filename [-s section] [-d | ]
-a architecture -n [-c catalogfile]
[-v <w.x.y.z> | ]
[-k nnnnn] [-u nnnnn]
-f specifies the INF file to process
-s specifies the INF section to place the DriverVer= directive. By
default this directive is placed in the [Version] section.
-d specifies the date written in the DriverVer= directive. Note that
a '’ given for a date value means for stampinf to write the
current date. If the date is not specified, the date is taken
from the STAMPINF_DATE environment variable.
-v specifies the version written in the DriverVer= directive. Note
that a '’ given for a version value means for stampinf to write
the current time (h.m.s.ms). This is useful during development
in order to get increasing version numbers. If the version is not
specified, its value is taken from the STAMPINF_VERSION
environment variable.
-a specifies the architecture string to replace the $ARCH$ keyword.
The $ARCH$ keyword is used to tailor a TargetOSVersion decoration
in a [Manufacturer] section, as well as its respective section
name, to a specific platform. If no value is specified, stampinf
takes its value from the _BuildArch environment variable.
-c specifies the value to be written in the CatalogFile= directive
in the [Version] section. By default, this directive is not
written.
-k specifies the version of KMDF that this driver depends on. This
is used to tailor the KmdfLibraryVersion & KMDF co-installer name
in the INF. This will replace the $KMDFVERSION$ and
$KMDFCOINSTALLERVERSION$ keywords in the INF. The string is of
the format:
<major_version>.<minor_version>
As an example, supplying 1.5 as the version string will result in
values of 1.5 and 01005 for the two keywords (respectively).
-u specifies the version of UMDF that this driver depends on. This
is used to tailor the UmdfLibraryVersion & UMDF co-installer name
in the INF. This will replace the $UMDFVERSION$ and
$UMDFCOINSTALLERVERSION$ keywords in the INF. The string is of
the format:
<major_version>.<minor_version>.<service_version>
(where service_version is generally zero)
As an example, supplying 1.5.0 as the version string will result
in values of 1.5.0 and 01005 for the two keywords (respectively).
-n noisy mode shows verbose stampinf output
NOTES:
The environment variable PRIVATE_DRIVER_PACKAGE can be set to
enable stampinf’s ‘developer mode’ behavior. When this is
set, the date and version used for DriverVer is set to the
current date and time, regardless of the command line
settings. Also, ‘CatalogFile=delta.cat’ is written to the
version section, unless a catalog was already specified
with ‘-c’.
> -----Original Message-----
> From: xxxxx@lists.osr.com [mailto:bounce-284442-
> xxxxx@lists.osr.com] On Behalf Of xxxxx@wipro.com
> Sent: Tuesday, April 24, 2007 7:12 AM
> To: Windows System Software Devs Interest List
> Subject: [ntdev] INX file version problem…
>
> Hi,
>
> Not sure if this is the right place to post this…But I have a small
> problem with an INX file I wrote for my driver.Under the [Version]
> section, I have given the DriverVersion as follows,
>
> DriverVer=4/25/2007,1.0.0
>
> However, when I build the driver the INF file I get has a different
> version number.
>
> DriverVer=4/25/2007,6.0.5384.4
>
> As this is just a sample driver, I’m using the KMDFSamples.cat file. My
> WDK version is 5384 and I am doing a checked build of the driver on a
> x86 platform for XP.
>
> This is not that serios an issue but I was just curious as to why the
> version number changes. Is this how it was designed to be?
>
> —
> Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer</service_version></minor_version></major_version></minor_version></major_version></w.x.y.z>
Thanks Mark… Now I get what’s going on.