| deploy.sh
| main_toolkit_launch.sh
| raid1-1si.sh
| sstk.conf
| sstkw_functions
| windows-setup.sh
|
\---utilities
| CLMChecking
| allboards.xml
| cfggen
| conrep
| conrep.xml
| cpqacuxe-X.YY-Z_ia64.tar.gz
| efibootmgr
| efivar
| gen-setupldr-options
| getuuid
| hplpcfg
| hpqlarep
| hpshowdisk
| hwdisc
| hwquery
| ifhw
| parted
| hpsetacpi
| sstkencrypt
| windows
\---sstkencrypt.exe
Set up driver installation
To install an OEM driver, the SSTK must copy the driver files from the repository to the target
server and update the unattended file which instructs Windows setup to install the driver.
To take advantage of these capabilities, you must upload the driver files into the repository (as
described in “Upload the operating system installation files” (page 30)). This section describes
how the windows-setup.sh script copies available drivers from the OEM folder, the
identification of the boot controller type, and items that are added to the unattended file. As
previously detailed, the PnP drivers are installed during the graphical mode of the Windows
Setup and copied by the copy_pnp_drivers() function in the windows-setup.sh script.
copy_pnp_drivers()
{
# Copy PnPDrivers driver files to windows installation path
# Destination folder
local targdir="${MSDATA}/\$win_nt\$.~ls/\$OEM\$/"
mkdir -p $targdir || return 1
find ${SOURCE}/drivers/*/*/windows/${OS_VERSION}/other-files/\$OEM\$ \\
-mindepth 1 -maxdepth 1 -exec cp -R {} $targdir \; || return 1
return 0
}
The $MSDATA, $SOURCE (set in sstk_defines), and $OS_VERSION (set in sstk.conf) SSTK
variables refer to the Windows MSDATA partition at the target server, the repository path, and
the operating system edition, respectively.
SSTK automatically sets the OemPnPDriversPath in the unattended file according to the driver
repository structure. During Windows text mode setup, only the OEM driver for the boot
Set up driver installation 39
To Next Page
Loading...
Need help?
General