inf2cat - postdated DriverVer not allowed

James_Harper · March 3, 2009, 6:10pm

Stampinf -d * appears to stamp the inf file with the local date, as
opposed to the UTC/GMT date. I am at +11 hours at the moment. Inf2cat
requires the date to be UTC, so it won’t work for me until 11am as a
postdated DriverVer is not valid

Any suggestions?

Thanks

Jame

Peter_Viscarola_OSR · March 3, 2009, 6:13pm

Ah… put the date in yourself and get rid of the STAMPINF tool?

Wait until 11AM and run STAMPINF then??

Peter
OSR

David_R_Cattley · March 3, 2009, 6:35pm

Visit England virtually?

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@osr.com
Sent: Tuesday, March 03, 2009 6:14 PM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] inf2cat - postdated DriverVer not allowed

Ah… put the date in yourself and get rid of the STAMPINF tool?

Wait until 11AM and run STAMPINF then??

Peter
OSR

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

Michal_Vodicka-2 · March 3, 2009, 6:44pm

Well, this question seems strange but I can imagine it can be a problem
for an automated build if it is really like this.

So the solution can be:

use -d xx/yy/zzzz instead of -d *
set STAMPINF_DATA environment variable to desired date (run stampinf
without parameters to see help)

Finally, report it as a WDK bug, please.

Best regards,

Michal Vodicka
UPEK, Inc.
[xxxxx@upek.com, http://www.upek.com]

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of David
R. Cattley
Sent: Wednesday, March 04, 2009 12:35 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] inf2cat - postdated DriverVer not allowed

Visit England virtually?

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@osr.com
Sent: Tuesday, March 03, 2009 6:14 PM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] inf2cat - postdated DriverVer not allowed

Ah… put the date in yourself and get rid of the STAMPINF tool?

Wait until 11AM and run STAMPINF then??

Peter
OSR

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

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

Michal_Vodicka-2 · March 3, 2009, 6:45pm

Sorry, it should be STAMPINF_DATE.

Best regards,

Michal Vodicka
UPEK, Inc.
[xxxxx@upek.com, http://www.upek.com]

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Michal Vodicka
Sent: Wednesday, March 04, 2009 12:43 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] inf2cat - postdated DriverVer not allowed

Well, this question seems strange but I can imagine it can be
a problem
for an automated build if it is really like this.

So the solution can be:

use -d xx/yy/zzzz instead of -d *

set STAMPINF_DATA environment variable to desired date (run stampinf
without parameters to see help)

Finally, report it as a WDK bug, please.

Best regards,

Michal Vodicka
UPEK, Inc.
[xxxxx@upek.com, http://www.upek.com]

> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of David
> R. Cattley
> Sent: Wednesday, March 04, 2009 12:35 AM
> To: Windows System Software Devs Interest List
> Subject: RE: [ntdev] inf2cat - postdated DriverVer not allowed
>
> Visit England virtually?
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@osr.com
> Sent: Tuesday, March 03, 2009 6:14 PM
> To: Windows System Software Devs Interest List
> Subject: RE:[ntdev] inf2cat - postdated DriverVer not allowed
>
> Ah… put the date in yourself and get rid of the STAMPINF tool?
>
> Wait until 11AM and run STAMPINF then??
>
> Peter
> OSR
>
> —
> 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
>
>
> —
> 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
>

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

James_Harper · March 3, 2009, 9:44pm

>

Well, this question seems strange but I can imagine it can be a
problem
for an automated build if it is really like this.

So the solution can be:

use -d xx/yy/zzzz instead of -d *

set STAMPINF_DATA environment variable to desired date (run stampinf
without parameters to see help)

Finally, report it as a WDK bug, please.

How do I do that? Is that just the ‘send feedback’ link in the help or
is there an actual bug tracking page?

Thanks

James

Peter_Viscarola_OSR · March 3, 2009, 10:02pm

You can file a bug on the WDK through Windows Connect. It goes directly into the bug tracking database that way.

Alternatively, use “send feedback”-- that’ll go to the doc writers, but hopefully they’ll forward it to the right place (and not just close it).

Peter
OSR

J_J_Farrell · March 3, 2009, 10:04pm

James Harper wrote:

Stampinf -d * appears to stamp the inf file with the local date, as
opposed to the UTC/GMT date. I am at +11 hours at the moment. Inf2cat
requires the date to be UTC, so it won’t work for me until 11am as a
postdated DriverVer is not valid

Any suggestions?

Move a long way East of Greenwich, but not quite as far East as you are
now You’ll be just like the people who created this bug then, and so
won’t notice it.

You can just use the options other than * or twiddle your time zone if
you’re doing it by hand, but it’s a real pain to deal with it
automatically in build.

Pity all those poor driver writers in Tonga though, they only get 11
hours a day to play with.

James_Harper · March 3, 2009, 10:18pm

>

You can file a bug on the WDK through Windows Connect. It goes
directly
into the bug tracking database that way.

Done. I think. Bug #420467

Thanks

James

David_R_Cattley · March 4, 2009, 9:43am

I am sure there are people whom wish I would (be) moved to a timezone where
I could only do one hour of development [damage] a day …

-Dave

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of J. J. Farrell
Sent: Tuesday, March 03, 2009 10:03 PM
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] inf2cat - postdated DriverVer not allowed

James Harper wrote:

Stampinf -d * appears to stamp the inf file with the local date, as
opposed to the UTC/GMT date. I am at +11 hours at the moment. Inf2cat
requires the date to be UTC, so it won’t work for me until 11am as a
postdated DriverVer is not valid

Any suggestions?

Move a long way East of Greenwich, but not quite as far East as you are
now You’ll be just like the people who created this bug then, and so
won’t notice it.

You can just use the options other than * or twiddle your time zone if
you’re doing it by hand, but it’s a real pain to deal with it
automatically in build.

Pity all those poor driver writers in Tonga though, they only get 11
hours a day to play with.

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

OSR_Community_User · March 4, 2009, 8:25pm

James,
Your bug report does not contain enough information for us to understand/reproduce the problem. Specifically, I need:

What is the complete syntax of your stampinf command?
What is the value of stampinf_date environment variable, if set?
What is the value of Driver Ver in the INF file after you issue the stampinf command?
What is the Date value for your computer?
What is the complete syntax of your inf2cat command?
What is the error message you receive from inf2cat? (Please use inf2cat with /v option for verbose output).

You can add this info to the bug report you filed, or post it here. Either way.
Thanks,
Jennifer

James_Harper · March 4, 2009, 8:41pm

> James,

Your bug report does not contain enough information for us to
understand/reproduce the problem. Specifically, I need:

What is the complete syntax of your stampinf command?

stampinf -f xenpci.inx -a $(_BUILDARCH) -d * -v 0.10.0.21

What is the value of stampinf_date environment variable, if set?

It is not set

What is the value of Driver Ver in the INF file after you issue the
stampinf command?

At 9:00am 4-Mar-2009 AEDT (UTC+11), the value of driver ver was

DriverVer=03/04/2009,0.10.0.21

What is the Date value for your computer?

Tue 04/03/2009
(that’s dd/mm/yyyy format)

What is the complete syntax of your inf2cat command?

%DDK_PATH%\bin\selfsign\inf2cat /driver:xenpci%BUILDDIR%
/os:Server2003_X86

What is the error message you receive from inf2cat? (Please use
inf2cat with /v option for verbose output).

Sorry I don’t have that information right now, and can’t reproduce it
until before 11am tomorrow morning (after 11am the local date and UTC
date will be the same and the error won’t occur), and unfortunately I’ll
be travelling until 11am tomorrow.

The gist of the error message was that the stampinf set the date
component of the DriverVer to the local date time (4th March), but
inf2cat expected the date to be UTC (3rd March), and so failed.

I will forward the information when I can.

James

Michal_Vodicka-2 · March 4, 2009, 8:55pm

> -----Original Message-----

From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of James Harper
Sent: Thursday, March 05, 2009 2:41 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] inf2cat - postdated DriverVer not allowed

Sorry I don’t have that information right now, and can’t reproduce it
until before 11am tomorrow morning (after 11am the local date and UTC
date will be the same and the error won’t occur), and
unfortunately I’ll
be travelling until 11am tomorrow.

Have you considered changing your computer time for a while?

Best regards,

Michal Vodicka
UPEK, Inc.
[xxxxx@upek.com, http://www.upek.com]

James_Harper · March 4, 2009, 8:58pm

>

> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of James Harper
> Sent: Thursday, March 05, 2009 2:41 AM
> To: Windows System Software Devs Interest List
> Subject: RE: [ntdev] inf2cat - postdated DriverVer not allowed
>
> Sorry I don’t have that information right now, and can’t reproduce
it
> until before 11am tomorrow morning (after 11am the local date and
UTC
> date will be the same and the error won’t occur), and
> unfortunately I’ll
> be travelling until 11am tomorrow.

Have you considered changing your computer time for a while?

I only have the wdk installed on my laptop, which also runs outlook. The
thought of changing the date frightens me a little

I don’t see that it’s a huge problem to wait a few days. If there is a
bug in stampinf, it’s been there a long time already.

James

Michal_Vodicka-2 · March 4, 2009, 9:04pm

> -----Original Message-----

From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of James Harper
Sent: Thursday, March 05, 2009 2:58 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] inf2cat - postdated DriverVer not allowed

I only have the wdk installed on my laptop, which also runs
outlook. The
thought of changing the date frightens me a little

Now I imagine a poor MS support guy traveling to your time zone with his
laptop to reproduce a problem

I see no problem with changing time and if you’re frightened, you can
always close Outlook

Best regards,

Michal Vodicka
UPEK, Inc.
[xxxxx@upek.com, http://www.upek.com]

OSR_Community_User · March 5, 2009, 8:09am

hi,

I had the same problem. Although germany is not so many hours off, but our
automatic build process sometimes runs short after midnight. There is an
environment variable
STAMPINF_DATE

which can be used. So the build environment (small perl program) first sets
the correct local date in the environment and then the batch file to compile
the driver is called with the correct parameter for stampinf. This solved
the problem.

– Reinhard

“James Harper” wrote in message
news:xxxxx@ntdev…
Stampinf -d * appears to stamp the inf file with the local date, as
opposed to the UTC/GMT date. I am at +11 hours at the moment. Inf2cat
requires the date to be UTC, so it won’t work for me until 11am as a
postdated DriverVer is not valid

Any suggestions?

Thanks

Jame

OSR_Community_User · March 5, 2009, 12:24pm

James,
Thanks for the additional info. This should be enough for us to investigate. Seems more like an inf2cat issue to me. Although, as suggested, there is a workaround by setting stampinf_date environment variable.
Jennifer

James_Harper · March 5, 2009, 7:02pm

> hi,

I had the same problem. Although germany is not so many hours off, but
our
automatic build process sometimes runs short after midnight. There is
an
environment variable
STAMPINF_DATE

which can be used. So the build environment (small perl program) first
sets
the correct local date in the environment and then the batch file to
compile
the driver is called with the correct parameter for stampinf. This
solved
the problem.

I’d like to not involve perl if possible. I’ve so far managed to do
everything with bat files.

Any suggestions for how I could set the STAMPINF_DATE to the current UTC
date in a bat file?

Thanks

James

Michal_Vodicka-2 · March 5, 2009, 7:07pm

> -----Original Message-----

From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of James Harper
Sent: Friday, March 06, 2009 1:02 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] inf2cat - postdated DriverVer not allowed

Any suggestions for how I could set the STAMPINF_DATE to the
current UTC
date in a bat file?

Use 4NT instead of CMD. It should be possible there.
Write a small console app which sets the variable and call it from
your batch.
Write a small console app which creates a batch file with desired
“set var=value” command and call app followed by generated batch.

etc.

Best regards,

Michal Vodicka
UPEK, Inc.
[xxxxx@upek.com, http://www.upek.com]

OSR_Community_User · March 9, 2009, 6:19am

On 3/4/2009 4:02 AM, xxxxx@osr.com wrote:

You can file a bug on the WDK through Windows Connect.
> It goes directly into the bug tracking database that way.

IMHO, you could also tell the problem to your coffee mug – in my
experience the outcome is nearly 100% identical.

I’d go with the documentation team - last time I submitted a doc change
request, the underlying problem actually got fixed.

BTW, did anybody else notice that the beta newsgroups (which also were
advertised on the Connect website) seem to have gone?