New Import Test and KeTickCount

[cd]

I recently received an email from WHQL indicating that the new import test
flagged the import of KeTickCount in my driver and that I should use
KeQueryTickCount instead.

Knowing I had never used that import, I searched my Codeview files of my
object files and discovered the reference to KeTickCount was generated by my
use of KeQueryTickCount.

So I get a note to get rid of an import which I don't use and to replace it
with an approved API that imports the invalid reference.

Time to fix the new PIT?

 

[cd]

I am posting again with my new ms-supported nospam alias...

------------------

I recently received an email from WHQL indicating that the new import test
flagged the import of KeTickCount in my driver and that I should use
KeQueryTickCount instead.

Knowing I had never used that import, I searched my Codeview files of my
object files and discovered the reference to KeTickCount was generated by my
use of KeQueryTickCount.

So I get a note to get rid of an import which I don't use and to replace it
with an approved API that imports the invalid reference.

Time to fix the new PIT?

 

[cd]

Here is what I received via email...

UPDATE: Public Imports Tool - Follow-up.

Hello, this email provides and update on the status and changes of the PIT
tool in HCT12. Below are some important points of information for the
current and future versions of the PIT tool.

HCT12 RC - PIT test always passes testing

We have discovered that HCT 12 RC had a setup issue which did not
consistently register two key dll's that PIT relies on. For the PIT tool to
work properly in HCT 12 RC it is necessary to manually register these two
DLL's with the system. This issue will be fixed for RTM.

If you have run the PIT tool from the HCT 12 RC kit on a driver that was
reported to have illegal imports and the test passed you may need to
register two DLL's that the PIT tool. Then rerun the PIT test on your
drivers.

Run the following commands to register all components needed for the PIT
tool:

o Regsvr32 c:\hct\peinfo.dll
o Regsvr32 c:\windows\system32\Mercclient.dll

KeTickCount will be moved from Block to Warn

The KeTickCount function is listed as illegal today and if found in your
driver results in an error in the PIT test. The recommended alternative for
KeTickCount is KeQueryTickCount, a macro which calls KeTickCount, since the
PIT test does not currently identify if a macro is calling the function of
the function is being called directly KeTickCount will be moved to warn.
Keep in mind that warnings are important to review as well as they many
impact the quality and stability of your driver.

Display Class Drivers do not need to pass the PIT test

If one of the drivers in your list is installed as a display driver you
do not need to pass the PIT tool to obtain logo at this time, however the
DCT's including the Vchk tool will need to be passed.

PIT tool will become optional for HCT12

After reviewing feedback from the hardware community we have decided to
make the PIT tool optional for HCT 12. The tool will still be available in
the same test kits however if a failure occurs it will not result in a
failure of the HCT's. The Tool will be required for HCT 12.1 so it is
important that testing continues using the PIT tool and feedback is
submitted on failures that are seen. If these failures are not resolved the
driver will fail HCT 12.1.



If you have feedback on any questions or concerns regarding the PIT tool I
would love to hear from you.

Thanks again for your time,

~Brian



For more information:

Public Import Test Changes information

http://www.microsoft.com/whdc/devtools/PIT.mspx



Recommended Functions for Kernel-Mode Drivers

http://www.microsoft.com/whdc/driver/kernel/km-fns.mspx

Using the HCT for Driver Development

http://www.microsoft.com/whdc/devtools/tools/hctndev.mspx

"Designed for Windows" Logo Program for Hardware

http://www.microsoft.com/whdc/winlogo/default.mspx