Creating a DPInst Installation Package

To create an installation package that uses DPInst, you must first create driver packages that comply with DIFx driver package requirements. In addition, DPInst requires that driver packages comply with the following requirements:

  • General driver package requirements that apply to all of the driver packages. These requirements are described in Creating a Driver Package and in the information about driver development on the Windows Hardware Developer Central website.

  • General driver package requirements that apply to each driver package type.

  • Additional DIFx-related entries in the INF file of a driver package, including an entry that specifies the driver package type; entries that identify the driver package to an end user; and an entry that specifies the name of the catalog file for a signed driver package.

  • Driver packages must be signed with a Microsoft Windows Hardware Quality Labs (WHQL) signature or a Microsoft Authenticode signature. Note that DPInst can also be configured to install unsigned driver packages in legacy mode and in debug mode. For more information about legacy mode, see Setting the legacyMode Flag. For more information about debug mode, see Configuring DPInst to Install Unsigned Driver Packages for Testing Purposes.

After creating the driver packages, add the driver packages and the DPInst-related files to the DPInst installation package. The DPInst-related files include the following:

  • The DPInst executable file (DPInst.exe).

  • An optional DPInst descriptor file, which can be used to:
    • Localize and customize the text, icon, and bitmaps that appear on the DPInst wizard pages.
    • Specify the subdirectories under the DPInst working directory where the driver packages are located.
    • Set configuration flags.
  • The files that customize the DPInst wizard pages. These files include the EULA text file, icon file, and the bitmap files. For information about these files, see Customizing the Items That Appear on the Wizard Pages.

There is no requirement for how the files are organized in a redistributable DPInst installation package. However, after an installation application copies the files to a computer, DPInst requires that files be organized in directories as follows:

  • All the DPInst-related files must be located in a single directory. This directory is the DPInst root directory. DPInst must be executed from the DPInst root directory.

  • All the driver package files must be located in the DPInst working directory or in subdirectories under the working directory. For information about specifying the DPInst working directory and subdirectories under the working directory, see Specifying the Location of a Driver Package.

In addition to using the DPInst descriptor file to set configuration flags, you can also use the optional DPInst command-line switches to set configuration flags. These configuration flags control:

If you distribute the installation package on a CD, we recommend that you create an AutoRun-enabled installation package. In the AutoRun.inf file for the package, configure the open command to open the DPInst.exe program included on the CD.

If you distribute driver packages over the Web, we recommend that you use the Microsoft IExpress Wizard to create a self-extracting executable file for the installation package that automatically executes DPInst.exe after it extracts all of the files from the installation package. For information about using IExpress Wizard, see Using IExpress Wizard to Create a DPInst Installation Package.

 

 

Send comments about this topic to Microsoft

Show:
© 2014 Microsoft