Edit

Share via

Installing Customized Driver Components

  • Article

Important

The modern print platform is Windows' preferred means of communicating with printers. We recommend that you use Microsoft's IPP inbox class driver, along with Print Support Apps (PSA), to customize the print experience in Windows 10 and 11 for printer device development.

For more information, see Modern print platform and the Print support app design guide.

When you provide customized components for Microsoft's printer drivers, you must also provide an .ini file for installation of the component. (If your printer isn't supported by ntprint.inf, you must also provide a printer INF file.)

The .ini file must contain an OEMFiles section. In this section, each customized component is described by using one of the following entries:

  • OEMDriverFilen

    Names a rendering plug-in.

  • OEMConfigFilen

    Names a user interface plug-in.

where n specifies the order in which the installer installs the files. Numbers specified for n must be contiguous, starting with 1, for both types of plug-ins.

For example, if you're providing two rendering plug-ins and one user interface plug-in, and your printer model is XYZ, your .ini file might appear as follows:

[OEMFiles]
OEMDriverFile1=XYZDRV1.DLL
OEMConfigFile1=XYZUI1.DLL
OEMDriverFile2=XYZDRV2.DLL

Spaces aren't allowed before or after the equal sign (=). File names can't include path specifications.

In the example, two rendering plug-ins are specified. Based on the n values for OEMDriverFilen, xyzdrv1.dll is installed before xyzdrv2.dll. The Unidrv and Pscript5 drivers call plug-ins in the order they're installed, so later, when a driver needs to call graphics DDI hooking functions and COM methods supplied by these plug-ins, xyzdrv1.dll is called before xyzdrv2.dll.

The .ini file name should reflect the printer product name. The .ini file name should be distinct from the names of .ini files for other printers to avoid name conflicts. If you're back-porting a rendering plug-in or user interface plug-in to Windows NT 4.0, your .ini file name must match your .gpd or .ppd file name. (That is, xyz.ini must be used for xyz.gpd or xyz.ppd.) This restriction doesn't apply to Windows 2000 or later versions of Windows operating system.

An .ini file can contain either ANSI or Unicode text, but Unicode text is recommended. Within an .ini file, lines beginning with the pound sign (#) are comments.

For more information, see General Guidelines for INF Files and Installing a Unidrv Minidriver.

If you provide a printer INF file, a convenient way to install and register a customized component is to make the component a dependent file of the printer driver. In addition, the associated .inf file can be installed as a dependent file. For more information about dependent files for printer drivers, see Printer INF File Entries.

Alternatively, you can install a customized component by making the component a dependent file for another print component such as a port monitor or a status application. However, this method might create difficulties because point-and-print operations install only the driver and driver-dependent files on the client. If a customized component isn't listed as a dependent file of the printer driver, the component must be installed on the client in some way other than as part of the point-and-print operation.