WDK5483 question

NTDEV
1

I met a annoying question this morning when I try to build the KMDF
static bus example.
Sometime it complained about:
“ERROR -
“g:\winddk\5483\src\kmdf\toaster\bus\static\objchk_wnet_x86\i386_objects.mac”
file time is in the future.”
No matter which command I used to build it-bz, bcz ,build -cz, build
-cez, the build environment could complains about it. I have reinstalled
wdk5483 2 times. Could this be a problem caused by DDK3790 and WDK5483
coexisting?

–

Best Regards,
hanzhu

2

hanzhu wrote:

I met a annoying question this morning when I try to build the KMDF
static bus example.
Sometime it complained about:
“ERROR -
“g:\winddk\5483\src\kmdf\toaster\bus\static\objchk_wnet_x86\i386_objects.mac”
file time is in the future.”
No matter which command I used to build it-bz, bcz ,build -cz, build
-cez, the build environment could complains about it. I have
reinstalled wdk5483 2 times. Could this be a problem caused by DDK3790
and WDK5483 coexisting?

No. Is g: a network share? It is possible that the time on the server
is not aligned with the time on your workstation. So, when build.exe
creates _objects.mac, it DOES get a file time in the future.

You can use “net time” to synchronize yourself to the server.

–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.

3

Tim Roberts дµÀ:

>

No. Is g: a network share? It is possible that the time on the server
is not aligned with the time on your workstation. So, when build.exe
creates _objects.mac, it DOES get a file time in the future.

You can use “net time” to synchronize yourself to the server.

Unfortunately, it’s a local disk. And I have synchronized the clock with
the NTP server. When I use DDK3790, I never met this problem on this
computer.:frowning: Does anybody know how can I contact with the WDK team? Or
is there any newsgroup for this? Hope them can provide some feedback.

4

hanzhu wrote:

Tim Roberts 写道:

>
> No. Is g: a network share? It is possible that the time on the server
> is not aligned with the time on your workstation. So, when build.exe
> creates _objects.mac, it DOES get a file time in the future.
>
Unfortunately, it’s a local disk. And I have synchronized the clock
with the NTP server. When I use DDK3790, I never met this problem on
this computer.:frowning: Does anybody know how can I contact with the WDK
team? Or is there any newsgroup for this? Hope them can provide some
feedback.

Is g: a FAT32 disk? Timestamps on FAT32 are only stored with 2-second
precision, which can sometimes cause issues like this. When you look at
the timestamp for _objects.mac, does it seem way out of whack?

Of course, if that is the case, I’m not sure what solution to suggest to
you.

–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.

5

Thanks a lot for your help, Tim
You should have helped me find out the root cause of this annoying
problem. After I convert the file system to NTFS, the problem goes away
forever. :slight_smile:

Best Regards,
hanzhu

Tim Roberts дµÀ:

hanzhu wrote:

> Tim Roberts 写道:
>
>> No. Is g: a network share? It is possible that the time on the server
>> is not aligned with the time on your workstation. So, when build.exe
>> creates _objects.mac, it DOES get a file time in the future.
>>
> Unfortunately, it’s a local disk. And I have synchronized the clock
> with the NTP server. When I use DDK3790, I never met this problem on
> this computer.:frowning: Does anybody know how can I contact with the WDK
> team? Or is there any newsgroup for this? Hope them can provide some
> feedback.

Is g: a FAT32 disk? Timestamps on FAT32 are only stored with 2-second
precision, which can sometimes cause issues like this. When you look at
the timestamp for _objects.mac, does it seem way out of whack?

Of course, if that is the case, I’m not sure what solution to suggest to
you.