Home > Articles > Operating Systems, Server > Microsoft Servers

  • Print
  • + Share This
From the author of

Adding Third-Party Device Drivers

So far I've shown you how to create the $OEM$ directory structure and then cause the setup program to copy it to each target computer by setting the value OemPreinstall to Yes in your answer file. This helps you get custom files to each target computer, but what do you do with them after that?

One of the most common scenarios is including third-party device drivers that didn't ship with Windows 2000. For example, your company uses a new network adapter that Windows 2000 doesn't support. The IHV provides a Windows 2000 driver, though, so you require the ability to first add that driver to your source files and then have the setup program automatically detect and use it during Plug and Play hardware detection. No problem. In i386\$OEM$\$1, create a subdirectory called Drivers and copy your new device drivers into that directory. Then, set OemPnPDriversPath to Drivers. The setup program copies the Drivers directory from the $OEM$ folder to C:\Drivers; then, it uses those drivers during hardware detection. You can organize your device drivers, too. For example, create the directories Drivers\video and Drivers\nic and set OemPnPDriversPath to Drivers\video;Drivers\nic. Note that the setup program automatically prefixes the path with %SystemDrive%.

Windows 2000 prompts users as to whether or not it's OK to install unsigned device drivers. If your IHV didn't digitally sign their driver, the setup process will stop for this prompt, defeating the purpose of an unattended installation. In order to prevent the setup program for prompting whether users want to install unsigned device drivers, add DriverSigningPolicy = "Ignore" to the [Unattended] section of your answer file. Presumably, you've tested these device drivers ahead of time and can vouch for their quality. As a result, ignoring driver-signing policy isn't a problem.

  • + Share This
  • 🔖 Save To Your Account