Click an icon to either expand ( ) or collapse ( ) each section. (If you cannot expand a section, then read the document Cannot expand sections in a Symantec Knowledge Base document.)
Brief introduction to integrating device drivers into Windows 2000/XP installation packages
Setup installs the device drivers by using Plug and Play (PnP) IDs that have been enumerated by the Windows Plug and Play function. Setup searches for a predefined path on the local drive. The relevant information for the driver is stored in the driver information .inf files. Windows Setup tries to find the best possible match for the Plug and Play ID of the device.
The default installation search path is set to %SystemRoot%\Inf by default, and is defined in the following registry key:
Setup uses this path to locate .inf files for any device installation. Once the original Windows Setup ends, the path stays active for the MS PNP Hardware installation wizard. If you modify this key during setup by using the Sysprep.inf or any Unattended answer file, the value becomes permanent unless changed again.
In the params.txt file, CCM uses a hardcoded, dedicated parameter, "OemPnPDriversPath." The "OemPreinstall" switch in the params.txt file must be set to "Yes." For example:
OemPnpDriversPath=the path to the oem drivers
If this switch is not set to yes, the OEM drivers are ignored.
Driver locations and handling in the CCM OS script.
There are many different methods to implement PnP drivers. The standard CCM Windows 2000 script and the early Windows XP scripts used the "Machinetype" admin parameter.
The machine type then includes references to the subdirectories where the drivers are located, resulting in the following depot directory structure:
- - \machine
- - - \GX110
- - - - - \NIC
- - - - - \MODEM
- - - - - \VIDEO
Later XP scripts handle OEM drivers using a script parameter named "COMPTYPE," resulting in the following depot directory structure:
- - \comptype
- - \pnp
- - - \MODEM
- - - \VIDEO
- - - \NIC
- - - - \e100b
- - - - \3c90x
- - \storage
The comptype folder then acts as a root folder containing the directory structure specified by the comptype parameter. The contents of the folders are basically batch files. These batch files are responsible for setting environment variables to later identify the Pnp driver needed, which is stored in the special PnP folder. This method has the advantage of using the same driver for different machine types without storing it in different locations.
The actual copying of the driver itself is indicated and regulated by a separate batch file named copydrv.bat. This file copies to the location specified through the already mentioned OemPnpDriversPath configuration parameter..
Step 1: Copy the driver into the CCM Depot
To copy the driver (or drivers) into the CCM Depot, do the following:
For Microsoft's step by step instructions for Windows 2000 & 2003 go to the following URL: http://support.microsoft.com/kb/254078/en-us
You can download the example batch files dell.bat and copydrv.bat.
Login to Subscribe
Please login to set up your subscription.
Get support for your product, with downloads, knowledge base articles, documentation, and more.
Maximize your product competency and validate technical knowledge to gain the most benefit from your IT investments.
Set default language
Do you wish to save this as your future site?