Requirements and Limitations
This topic explains the software that is required to run ChkINF and the limitations of the tool.
Starting with the Windows Driver Kit (WDK) for Windows Vista, the ChkINF tool contains a Perl interpreter that is located in the Tools\chkinf subdirectory of the WDK.
In earlier versions of the Windows Driver Kit (WDK) that were known as the Device Driver Kit (DDK), you needed a Perl interpreter installed on your computer to run ChkINF. ChkINF should work correctly with any version of Perl 5.0 or greater, but it has not been tested with any versions previous to 5.003_07.
Also, the directory in which the Perl interpreter is located must be added to the %PATH% environment variable on your system. If the installation program does not amend the path, you must do it manually.
Microsoft neither endorses nor recommends any specific third-party Perl interpreters, but ChkINF has been tested with the following Perl interpreters:
GNU Perl 5.005_02 compiled for Win32
GNU Perl 5.6.0 compiled for Win32
Perl for Win32 5.003_07 from ActiveWare Internet Corp.
ActivePerl 18.104.22.1681 from ActiveState (see the ActiveState website)
To validate Include and Needs directives in an INF file, you must run ChkINF on the operating system for which the INF file is designed.
ChkINF does not support INF files for Windows 98 or Windows Me.
ChkINF validates elements of an INF file specific to a device setup class only for the device setup classes listed in the chkinf.htm file (located in the Tools\chkinf subdirectory of the Windows Driver Kit [WDK].)
ChkINF has limited support for INF files in Unicode format, including Unicode Big Endian and UTF8, but it cannot interpret all extended characters. To validate an INF file in Unicode format, save the file as an ASCII text file before running ChkINF.
ChkINF does not verify the registry keys set by an INF file.
ChkINF incorrectly reports an error if a named service uses different binary names on the x86-based and Itanium-based platforms.