The Signability command-line tool (signability.exe):

• Determines whether a driver package INF file can be digitally signed.
• Optionally generates a catalog file whose name must be specified by a CatalogFile=filename.cat directive in the INF Version section of the driver package INF file.

Signability [/driver:path] [/os:nnn] [/cat] [/dtc] [/dbgsym] [/auto] [/?]

Parameters

/driver:path

Supplies the path to the directory that contains the driver package files.

/os:nnn

Configures Signability to verify that the driver package INF file complies with the requirements of the Windows versions that are specified by the flag value nnn. The value of the flag nnn is either a single value or a sum of values in the following table.

Flag value	Corresponding Windows version
1	Windows 98
2	Windows 2000
4	Windows Millennium Edition
8	Windows XP, 32-bit version
16	Windows XP, 64-bit version
32	Windows Server 2003, 32-bit version
64	Windows CE for Smart Display
128	Windows Server 2003, 64-bit version
256	Windows Vista, 32-bit version
512	Windows Vista, 64-bit version

/cat

Configures Signability to generate the catalog file whose name is supplied by the driver package INF file.

/dtc

Configures Signability to add a DataCenter attribute to the catalog file.

/dbgsym

Not supported in the WDK build environment.

/auto

Configures Signability to run without user interaction.

/?

Configures Signability to display help information in a dialog box.

Comments

To use Signability, the user must be a member of the Administrators group on the system and run the command from an elevated command prompt.

Signability checks driver package INF files for structural errors and verifies that a driver package can be digitally signed. A driver package can be signed only if all of the files that are referenced in an INF file are present and the source files are in the correct location. If an INF file cannot be signed or if it contains structural errors, the driver package might not be installed correctly or might incorrectly display a driver signing warning dialog box during installation.

When you run Signability, it displays a dialog box, as illustrated in the following figure. Signability fills in the text box and selects the check boxes that correspond to the parameters that are supplied on the command line.

Signability tool dialog box

The Signability tool creates a Signability.txt log file that the tool opens in Notepad. The log file includes a Warnings section and an Errors section. The Warnings section lists the files in the driver package and a corresponding warning message if a file is not represented by a signed catalog file. The Errors section lists the INF file errors that the tool detected.

The Signability tool is installed automatically the first time you make a new submission on the  Windows Quality Online Services (Winqual) Web site.

The installation adds a WinQual Tools entry under the Accessories entry under All Programs and installs the tool in Program Files\WLPQS directory on the system disk. For more information about the Signability tool, see the readme.htm file that is included with the Signability tool installation.

The Signability tool is located in the ..\bin\selfsign folder of the WDK.

Examples

The following Signability tool command verifies the driver package INF file in c:\MyDriver directory and creates a catalog file for the INF file. The /os:186 parameter configures the tool to verify that the INF file complies with the requirements of the following Windows versions: Windows Server 2003 (32-bit and 64-bit versions), Windows XP (32-bit and 64-bit versions), and Windows 2000. The value 186 is the sum of the flag values that correspond to these Windows versions: (2+8+16+32+128) = 186.

Signability /auto /cat /driver:c:\MyDriver /os:186

The following Signability tool command displays a dialog box that lists the Signability tool options.

Signability /?