Each section is labeled with a decoration (for example. This type of INF file is created by creating additional DefaultInstall, DefaultInstall.Services, DefaultUninstall, and DefaultUninstall.Services sections for each operating system version.
FILE DRIVER INSTALL
You can create a single INF file to install your driver on multiple versions of the Windows operating system. The CopyFiles directive should not refer to the catalog file or the INF file itself SetupAPI copies these files automatically. In the DefaultInstall section, a CopyFiles directive copies the file system driver's driver files to the destination that is specified in the DestinationDirs section.
FILE DRIVER CODE
The Version section specifies the driver version information, as shown in the following code example.Įxamplefilesystem.sys = 1 DefaultInstall Section (required) You can use the InfVerif tool to check the syntax of your INF file.Īn INF file for a file system driver generally contains the following sections.ĭestinationDirs (optional but recommended) To construct your own file system driver INF file, use the following information as a guide. Sections in a file system driver INF file INF files cannot be used to read information from the registry or to launch a user-mode application.
FILE DRIVER DRIVERS
For more information, see Signing Drivers during Development and Test (Windows Vista and Later). However, the driver will fail to load (and thus execute) because it is unsigned.įor detailed information about the driving signing process, including the driving signing process for 64-bit versions of Windows Vista, see Kernel-Mode Code Signing Walkthrough.Īll kernel-mode components, including custom kernel-mode development tools, must be signed. With Administrator privileges, an unsigned driver can still be installed on 圆4-based systems starting with Windows Vista. Given an INF file, the Inf2Cat command-line tool can be used to create a catalog (.cat) file for a driver package. For performance reasons, boot-start drivers must contain an embedded signature. The SignTool command-line tool, located in the \bin\SelfSign directory of the WDK installation directory, can be used to directly "embed sign" a driver SYS executable file.
INF files for non-PnP drivers, including file system drivers, are not required to contain or sections. For these versions of the Windows operating system, the following list contains information that is relevant to file system drivers. Starting with 64-bit versions of Windows Vista, all kernel-mode components, including non-PnP (Plug and Play) drivers such as file system drivers (file system, legacy filter, and minifilter drivers), must be signed in order to load and execute. For more information about creating such an INF file, see Creating INF Files for Multiple Platforms and Operating Systems and Creating International INF Files.
For general information about signing drivers, see Driver Signing. An INF file also contains driver configuration information that SetupAPI stores in the registry, such as the driver's start type and load order group.įor more information about INF files, see Creating an INF File and INF File Sections and Directives. The INF file is a text file that specifies the files that must be present for your driver to run and the source and destination directories for the driver files. The installation process is controlled by INF files.Ī file system driver's INF file provides instructions that SetupAPI uses to install the driver. The Windows Setup and Device Installer Services, known collectively as SetupAPI, provide the functions that control Windows setup and driver installation. Creating an INF file for a file system driver About file system INF files
0 kommentar(er)
