RIS OEM Driver NIC install

[Dave]

Had exact same problem with some new Gateways we bought
with that exact adapter. I finally got it working, with
the original OEM drivers and with the ones I downloaded
from the Intel site. Here are the drivers that are used.

e100bnt5.sys
e100bnt5.inf
e100bmsg.dll
e100bnt5.din
IntelNIC.dll
Prounstl.exe

I put all of them in the i386 directory and in $OEM$\$1
\Drivers\NIC directory. Then I setup the .sif file as per
the article you refered too.

Something that bite me in the butt initially was a simple
problem, but I'll throw it out there.
Your directory structure should be..
[Correct Structure]
.....\Images\win2000.pro\i386
.....\Images\win2000.pro\$OEM$\$1\Drivers\NIC ...

[Wrong Structore]
I had this ... \Images\win2000.pro\i386\$OEM$\
(left over from prior habits)
its always the simple stuff.

Here is the what was in my .sif file (the
DriverSigningPolicy will stop the driver confirm messages)

[Unattened]
OemPreinstall = Yes
OEMPnpDriversPath = "Drivers\NIC"
DriverSigningPolicy = Ignore

Everything worked after that... if you want my full .sif
file let me know...

Dave

 

[Howard]

Dave,

Thankyou for your feedback,

The problem came to its end yesterday when I streamlined
sp4 with my source files before generating any flat images.

Regards,

Howard

-----Original Message-----
Had exact same problem with some new Gateways we bought
with that exact adapter. I finally got it working, with
the original OEM drivers and with the ones I downloaded
from the Intel site. Here are the drivers that are used.

e100bnt5.sys
e100bnt5.inf
e100bmsg.dll
e100bnt5.din
IntelNIC.dll
Prounstl.exe

I put all of them in the i386 directory and in $OEM$\$1
\Drivers\NIC directory. Then I setup the .sif file as per
the article you refered too.

Something that bite me in the butt initially was a simple
problem, but I'll throw it out there.
Your directory structure should be..
[Correct Structure]
.....\Images\win2000.pro\i386
.....\Images\win2000.pro\$OEM$\$1\Drivers\NIC ...

[Wrong Structore]
I had this ... \Images\win2000.pro\i386\$OEM$\
(left over from prior habits)
its always the simple stuff.

Here is the what was in my .sif file (the
DriverSigningPolicy will stop the driver confirm messages)

[Unattened]
OemPreinstall = Yes
OEMPnpDriversPath = "Drivers\NIC"
DriverSigningPolicy = Ignore

Everything worked after that... if you want my full .sif
file let me know...

Dave

-----Original Message-----
Hello,

I am in the process of setting up an RIS. Everything is
fine save that the client systems tend to contain a
variety of several different NIC's.
For the time being I am concerned primarily with
the "Intel® PRO/100 VE Desktop Adapter". Windows begins,
to boot up until the point were I assume BINL mode is
replaced by use of the network driver.
At this point I receive an error message stating that the
install can not continue because the network driver is
unavailable for this image.
Based on the article 246184 I have updated the sif file
Ristndrd.sif; however there is some room for error. If
anyone has solved a similar problem perhaps they might be
kind enough to explain plausible and probable areas of
complication.
Typically there are several .sif files in the directory
structure, if one were to use RIPREP (see article), what
would the other .sif file name be set as?
How can one tell without doubt if the drivers should be in
a directory as suggested; given that my Intel drivers are
available from three sources and each seems different?

The most confusing issue is that of copying inf and sys
files to the i386 directory. Simply I do not know which
inf or sys files to copy. There are several.
Further to this Windows (when already installed via cd and
being configured graphically) had to be told that the
drivers were correct as Windows did not believe that they
were, so in other words instead of being detected they had
to be selected and then selected/confirmed to be used.

Replication of sub directory structure seems an area open
to confusion perhaps someone might present an example of
correct method? for the sake of certainty.
Is there some particular order to instructions in the
unattended section of the unattended file?
If is canny with the concept of supporting many NIC's with
RIS, then a distillation of typical complications would be
of use? i.e. many cards which are unsupported all need
their .inf and .sys files copied to the respective i386
directory.

Lastly is there any way to force Windows to use a
particular driver?

I will be testing on all solutions.
.

.