Device Driver and Installation for Video Components
This section summarizes the requirements for video components.
11. Device driver and installation meet Windows and Windows NT standards
The manufacturer does not need to supply a driver if a standard driver provided with the operating system can be used. If the manufacturer supplies drivers, the requirements for installation include the following:
- All devices and drivers must pass testing by Microsoft WHQL.
- All configuration settings are stored in the registry. The driver must not use INI files for configuration settings.
- The correct minidriver, VxD, or any other manufacturer-supplied files specified in the device's INF must be installed in the correct locations. For manufacturer-supplied files, the vendor must not be identified as Microsoft, and all other copyright and version information must be correct for the manufacturer.
- Driver installation and removal uses the Windows-based methods defined in the Windows 95 and Windows NT DDKs. However, any software applications included with the device can be installed using an alternate Windows-based installation method.
- Driver files provided by the vendor must not use the same file names as used by files included in Microsoft operating systems, unless specifically agreed with Microsoft.
- Only 32-bit protected-mode components are installed. No real-mode or 16-bit protected-mode components are provided in order to operate under Windows.
- Driver supports Plug and Play IRPs (for WDM drivers) or messages (for VxDs).
- If support using WDM drivers is provided in the operating system, the driver supplied by the manufacturer must be a WDM minidriver.
For complete details about standard installation requirements for drivers, see "Basic PC 97" in Part 2 of this guide.
Note Monitor support for Windows is installed using a Monitor INF file, as defined in the Windows 95 and Windows NT DDKs.
12. Applications provided with device meet Windows standards
Any Windows-based applications provided with the device must meet Microsoft requirements for software compatibility as indicated by the "Designed for Microsoft Windows" logo. Applications installed with the device must use a standard Windows-based installation method, as defined in the Win32 SDK.