It's considered a bit kludgy, but it works fine if you don't mind that.
We did this to push self-installer images out to servers. Some had
card X, some had card Y. Just add the drivers into the $oem$\$$\inf
directory, and text-mode setup will happily dump them in the right
place. There are a couple of caveats.
%WINDIR%\inf is where the OS looks for the base-included OS drivers.
For NT/2k, that's C:\WINNT\inf, C:\Windows\inf on XP/2K3. Setup will
auto install the drivers if it finds the right ones there (based on the
ID the card returns based on a hardware probe).
CAVEATS:
You need to make sure you get flat drivers, though (where the .inf and
the .sys files are in the same folder), or edit the inf file to get rid
of the subdirectories. Also, if you're shipping drivers for anything
(like an Intel gig nic) that Windows ships with drivers for, make sure
you get *signed* drivers, or else SFC will backrev your driver. Took me
a few days to figure out why my servers were installing, successfully
doing network operations, then rebooting after setup with nonfunctional
network cards. Had to get the certified drivers to keep SFC from
replacing them.
Shout if you need anything else on this one.
(j)
James
