1 Reply Latest reply on Nov 19, 2003 8:44 AM by Support_1

    Adding Additional Drivers

    pikem1 Rookie
      We are experiencing the situation that the company is ordering new desktops/laptops with drivers different than what we currently use.  I need to add these additional drivers to OSD. 

      We currently have OSD configured to look to the unattend.txt file to know where to find the drivers.  I know how to add driver locations to the OemPnPDriversPath line.  However, I also know that we will eventually hit the 256 character limit set by Microsoft.  I would like to try to circumvent this problem before it happens.

      My first thought was to create a new setup using the Setup Builder for each model type.  I would then copy the necessary driver files into the appropriate *.zip file under OSDSetups.  But then those zip files become such a hodgepodge of different drivers.  Not that it should be an issue, but it's not very organized.

      Then I considered continuing to add new drivers as we do now in the $OEM$\$1\Drivers\*.* location.  I would create a subfolder for each model type.  (Ex. ...\Drivers\NetCard\Dell260).  But in order to minimize the OemPnPDriversPath file in the unattend.txt file, I could copy all files from the Dell260 folder to the root of the NetCard folder.  Then the OemPnPDriversPath line would just reference the root of each driver's folder.  But this would become just as large of a collection of files that would be in the LAN.zip file. 

      My question is this:  Which method is recommended for dealing with the proliferation of new drivers over time - unattend.txt or zip files?  Regardless of the method, is my plan of just lumping all driver files in the zip file or the root of the appropriate driver folder a "good" plan?  What other options are there?

      I guess I'm trying to keep some kind of order by separating the different drivers for the various models in their own subfolders somewhere.  But maybe this isn't an issue and I'm looking too deep into this.  My ultimate goal is to successfully add new drivers without running into the 256 character limit in the unattend.txt file soon.  Any advice or suggestions would be helpful.  Thank you.
        • 1. Re: Adding Additional Drivers
          Support_1 Specialist
          To add additional drivers to your OSD setup, you have two options.

          Option 1:

          Insert the the driver files into the appropriate ZIP file's located in the source fileshare:

          \Drivers\.ZIP

          *   designates the relevant share for the operating system source files.
          *   .zip designates the relevant zip file depending on the driver category.

          Option 2:

          According to Microsoft:

          "Plug and Play device drivers that are not included on the Windows 2000 Professional operating system CD can easily be added by following the steps in this section. This method works for all Plug and Play device drivers. You can also use this method for updating drivers.

          To add Plug and Play devices

          In the \$OEM$ subfolder of the distribution folder, create a subfolder for any special Plug and Play drivers and their INF files, for example:
          $OEM$\$1\PnPDrvrs

          In the answer file, edit the [Unattend] key for Plug and Play, adding the path to the list of Plug and Play search drives, for example:
          OEMPnPDriversPath = "PnPDrvrs"

          To maintain the folders so that they can accommodate future device drivers, create subfolders for potential device drivers. By dividing the folders into subfolders, you can store device driver files by device type, rather than having all device driver files in one folder. Suggested subfolders types include Audio, Modem, Net, Print, Storage, Video, and Other. An Other folder can give you the flexibility to store new hardware devices that might not be currently known.

          If the PnPDrvs folder contains the subfolders Audio, Modem, and Net, the answer file must contain the following line:

          OEMPnPDriversPath = "PnPDrvs\Audio;PnPDrvs\Modem;PnPDrvs\Net"

          Note The specified folder is created at the root of the system drive and remains there after setup is complete.

          Driver Signatures
          If you intend to use any updated drivers, you must first verify that they are properly signed. If they are not, those drivers might not be installed. To verify that drivers are properly signed, contact the vendor.

          Driver Signing Policy
          In the answer file, the DriverSigningPolicy key in the [Unattended] section specifies how nonsigned drivers are processed during installation.

          Important Microsoft strongly advises against using DriverSigningPolicy = Ignore unless you have fully tested the device driver in your environment and are sure that it works properly. Using unsigned drivers increases the risk of device driver problems that can effect the performance or stability of your computer.

          If you are using DriverSigningPolicy = Ignore and you attempt to install a newer, unsigned copy of a driver that is protected by Windows 2000 Professional, the policy level is automatically updated to Warn.

          For more information about driver signing policy, see Unattend.doc in Support\Tools\Deploy.cab on the Windows 2000 Professional operating system CD."

          http://www.microsoft.com/technet/treeview/default.asp?url=/technet/prodtechnol/windows2000pro/reskit/part2/proch05.asp