Lisa,
You want to get the latest BINLSVC (RIS) hotfix from Microsoft. With that,
getting Intel's NICs working with RIS becomes easy. It will also fix other
problems with Broadcom and other vendor's NICs and the INF files they use.
There are two phases in which RIS requires drivers - the first phase is
while PXE hands off driver support to normal XP drivers (before it does the
file copying phase, while still in text-mode) and the second is when there
are about 34 minutes left during the GUI install, when your NIC drivers are
installed during the heart of XP's setup routines.
I'll assume your problem is in phase 1.
1. Download the binlsvc fix from Microsoft (call the helpdesk, get the
hotfix, install it on the RIS server, reboot if prompted.)
2. Ensure in the image you're using (start with only one image to simplify
things!) that you have the e1000.sys and e1000.inf (or the other name for
those drivers - Intel names it oddly sometimes) in the i386 directory. Once
you restart binlsvc (or reboot the server) the INFs will be parsed and the
next client that runs should then "find" the e1000 NIC and it should then
'just work'.
3. For the PnP phase of XP's setup (at 34 minutes remaining) do as Nick
suggested - make sure at the same level as the i386 directory you have an
$OEM$ directory, and in there you'll need your NIC drivers (yes, another copy
of the NIC drivers.) Be sure to modify ristndrd.sif in \templates with the
OEMPNPDRIVERSPATH= statement (the web page goes into more details on that.)
