RIS+XPSP1+Intel100VE = Mission Impossible

[Aatu]

Hi!

Tech: Win2000SP3 RIS Servers (RIS Patched) with W2KSP1,
W2KSP2, W2kSP3 and XPSP1 images. Everything works fine so
far.
New: 300 Desktops with MSI 845GE Max mainboard and
integrated Intel 100 VE NIC/Graphics/Audio. Now comes the
problems.
It's impossible to get them going through RIS.
- added $OEM$ folder to RIS with nic, audio and display
drivers and edited the sif file (audio and display drivers
installs nicelly)
- added drivers to I386 folder
- tried different NIC drivers (Intel XP and W2k,
manufacturers, old and new)
- used XP-drivers in $OEM$ folder and W2K inf files in
I386 folder
- deleted all *.pnf files in I386 folder after altering
- restarted BINLSVC after altering
- even edited the e100b325.inf file, there is no [Intel]
section so I created one!
- all Ms Q-patches are applied conserning this matter.
- and all over again.. and again... and again..

And the client respons over and over:
"the image selected does not contain drivers for your
hardware" on blue screen.
On RIS server I have "Error parsing specified section of
INF file".

With a 3Com905 NIC everything works fine! Is the only
solution to buy 300 3Com NICs? Anyone else dealing with
these "sucking" problems?

Cheers
Aatu

 

[Aatu]

Hi!

Beleave it or not.... all solved!
Our test environment uses 10 Mb/s hubs to connect
testboxes.
Intel 100 VE NIC and RIS *ONLY* works with native 100 Mb/s
ports.
Connected testboxes to our LAN using Cisco 29xx Switch and
RIS works OK with these NICs.

A solution can some times be very simple )

Cheers
Aatu

 

[Cary Shultz]

-----Original Message-----
Hi!

Beleave it or not.... all solved!
Our test environment uses 10 Mb/s hubs to connect
testboxes.
Intel 100 VE NIC and RIS *ONLY* works with native 100 Mb/s
ports.
Connected testboxes to our LAN using Cisco 29xx Switch and
RIS works OK with these NICs.

A solution can some times be very simple )

Cheers
Aatu


.

But N E V E R easy....

 

[Michalko]

Hi!

) i have also this problem with Dell D500 notebook with Intel 100VE NIC.

I have cisco 3300 switch
I created:
-i386
-$oem$
--$1
---drivers
----nic
----- - I copy winXP drivers here

Next I copy WinXP (with e100b325.inf) drivers to i386 folder.
I Replace e100b325.inf in i386 by Win2000 inf file (e100bnt5.inf) - changed
inf file has same name as WinXp inf file

Next delete e100*.pnf files
Next restart binlsvc

IT'S STILL NOT WORK !!!!

ERROR: Blue screen -> The operating system image you selected does not
contain the necessary drivers for your network adaptor........

HELP ME !!!! PLEASE!

THANK YOU!

 

[Charles Wilson]

Hi,

Yes getting the same problem with an onboard Intel NIC.
Tried alsorts to remedy it!

 

[Aatu]

Hi!

I hope you both, Charles and Johan, read my earlier
message how I found the solution:
- Intel 100 VE integrated NIC needs, at least in our
environment, native 100 Mb/s networkport to functioin
properly with RIS. I used 10 Mb/s hub to connect my
testboxes and didn't work -> changed to 100 Mb/s switch
and everyting works just fine.

Cheers
Aatu

 

[Charles Wilson \(Sheffield UK\)]

Hi again,

Managed to get this to work (after 4 days of playing!).
I had to slipstream in SP3 to my Win2k image, then copy
the correct drivers into the Drivers\Nic folder.

One important note though, I had to copy the entire Win2k
cd into a temp folder on the server first, do the
slipstreaming to that, then create the RIS image from
that, NOT from the Win2k cd. It then worked perfectly

If you need more info. give me an emither


Charles

-----Original Message-----
First of all, the $OEM$ folder needs to be in the same folder as i386
(not in i386 as you normally do with ordinary unattended installs)

At the same level as the I386 folder on the RIS image, create a $oem$
folder with the following structure: \$oem$\$1 \Drivers\Nic . Copy the
OEM-supplied driver files to this folder (Note the folder in which the
..inf file looks for its drivers)

If the driver is not signed you also need to set the
driversigningpolicy in the.sif-file (normally Ristndrd.sif)
[Unattended]
DriverSigningPolicy = Ignore
OemPreinstall = yes
OemPnpDriversPath = Drivers\Nic

On the RIS server, copy the OEM-supplied .inf and .sys file for the
network adapter to the
RemoteInstall\Setup\Language\Images\Dir_name\i386 folder. This allows
Setup to use the driver during the Text-mode portion of the
installation.

Stop and restart the BINL service on the RIS server

Johan Arwidmark

Hi,

Yes getting the same problem with an onboard Intel NIC.
Tried alsorts to remedy it!

-----Original Message-----
Hi!

Tech: Win2000SP3 RIS Servers (RIS Patched) with W2KSP1,
W2KSP2, W2kSP3 and XPSP1 images. Everything works fine so
far.
New: 300 Desktops with MSI 845GE Max mainboard and
integrated Intel 100 VE NIC/Graphics/Audio. Now comes the
problems.
It's impossible to get them going through RIS.
- added $OEM$ folder to RIS with nic, audio and display
drivers and edited the sif file (audio and display drivers
installs nicelly)
- added drivers to I386 folder
- tried different NIC drivers (Intel XP and W2k,
manufacturers, old and new)
- used XP-drivers in $OEM$ folder and W2K inf files in
I386 folder
- deleted all *.pnf files in I386 folder after altering
- restarted BINLSVC after altering
- even edited the e100b325.inf file, there is no [Intel]
section so I created one!
- all Ms Q-patches are applied conserning this matter.
- and all over again.. and again... and again..

And the client respons over and over:
"the image selected does not contain drivers for your
hardware" on blue screen.
On RIS server I have "Error parsing specified section of
INF file".

With a 3Com905 NIC everything works fine! Is the only
solution to buy 300 3Com NICs? Anyone else dealing with
these "sucking" problems?

Cheers
Aatu

.

.

 

[Brian P.]

Intels site contains fixes for all of these problems, we
fought them all but no we are up and running. Here is the
Blue screen issue fix:
http://support.intel.com/support/network/adapter/pro100/pro
100ve/tti007.htm

As far as no drivers for NIC, we had to put the non
modified .inf driver file in the i386 directory of the CD
Image. Just remove the .x86 from the intel header. Then
follow the microsft directions to add the OEM drivers to
the ripreped image. Voila.