Question about RIS - Can't install the Network card after installation..

  • Thread starter Thread starter Miklos
  • Start date Start date
M

Miklos

Hello to all here...

I post this question on other forums and no answers yet, I hope you can help
me....

The main problem here is that I make a RIS Server for my enterprise with 2
choices: Windows XP and Windows 2000 Professional..... When the users select
the Windows XP they have no problems (yes all the drives are there), but
with Windows 2000 no way.. we can't even install...

Well, searching in microsoft I found the KB315279: How to add a third-party
OEM Netword Adapter to an RIS Installation...

I made everything that is there... well I will present the steps here:

1. Run RISETUP and copy and Win2kPro cd as master image in folder Win2kPro
(Slipstream with Sp4).
3. Created a \DRV\NIC folder on the computer and gathered all drivers:
Pro100, Pro1000 there (mostly the *.cab, *.inf, *.sys).
3. created \$oem$\$1 under the s RIS Server and copied \drv\nic to it.
4. copied .inf's and .sys's to RIS SERVER - Win2kPro folder \i386.
Note: (following instructions from intel:
http://support.intel.com/support/network/sb/cs-000023-prd38.htm)
5. Also change the registry *.sif file in the \i386\templates folder....
with the parameters:
[Unnatended]
DriverSigningPolicy = Ignore
OemPreInstall = yes
OemPnpDriversPath = drv\nic
6. Rebooted RIS server (easier then stopping and starting binlsvc).
7. PXE booted all clients: all can see the win2k image and start the
installation of the windows 2000 Pro Sp4.

However after finish the installation - Windows2000ProSP4 didn't install
anything (of the DRV\NIC Folder), why ? Not even the network drivers ? weird
?!!!!!

As you can see all the network cards are mostly Intel PRO 100....

And remember that if I install the computers with Windows XP (with the RIS
Server of course) all works perfectly....

Please help..

Thanks a lot

Miklos
 
With some setups you can take the manufactures OEM
drivers and compy them straight into the I386 folder of
your image then restart the BINL service. Try this...
-----Original Message-----
Hello to all here...

I post this question on other forums and no answers yet, I hope you can help
me....

The main problem here is that I make a RIS Server for my enterprise with 2
choices: Windows XP and Windows 2000 Professional..... When the users select
the Windows XP they have no problems (yes all the drives are there), but
with Windows 2000 no way.. we can't even install...

Well, searching in microsoft I found the KB315279: How to add a third-party
OEM Netword Adapter to an RIS Installation...

I made everything that is there... well I will present the steps here:

1. Run RISETUP and copy and Win2kPro cd as master image in folder Win2kPro
(Slipstream with Sp4).
3. Created a \DRV\NIC folder on the computer and gathered all drivers:
Pro100, Pro1000 there (mostly the *.cab, *.inf, *.sys).
3. created \$oem$\$1 under the s RIS Server and copied \drv\nic to it.
4. copied .inf's and .sys's to RIS SERVER - Win2kPro folder \i386.
Note: (following instructions from intel:
http://support.intel.com/support/network/sb/cs-000023- prd38.htm)
5. Also change the registry *.sif file in the \i386 \templates folder....
with the parameters:
[Unnatended]
DriverSigningPolicy = Ignore
OemPreInstall = yes
OemPnpDriversPath = drv\nic
6. Rebooted RIS server (easier then stopping and starting binlsvc).
7. PXE booted all clients: all can see the win2k image and start the
installation of the windows 2000 Pro Sp4.

However after finish the installation -
Click to expand...
Windows2000ProSP4 didn't install
 
I ran into the same type of problems using Intel cards.
Hopefully what I experienced and learned will assist you
with your problem:

I had 2 PCs and a laptop all running Intel Nics. I would
get the error "Does not contain the necessary drivers.
Blah Blah Blah." Here's the scenerio:
1. Desktop with Pro100b Card - 50 of them onsite.
2. Desktop with Pro100ve Integrated
3. Laptop with Pro1000ct Integrated

The default MS Windows 2K drivers would allow systems 1
and 2 to come up but not 3. If you install the new Intel
Drivers system 3 would come up but not 1 and 2. What I
found was that when you followed the Intel and Microsoft
support documents it would have you copy all of the DLL
files from the Drivers\Nic folder to i386 which would
replace e100bnt5.sys and e1000nt5.sys which would make
system 3 work but systems 1 and 2 would fail. By leaving
Microsoft's E100bnt5.sys file for systems 1 and 2 then
updating the E1000NT5.sys file in i386 this would get me
past the point where it could start copying files. You
can have all of the latest drivers from intel in the
$OEM$\1\Drivers\Nic folder since that appears to be used
later in the setup (GUI Setup). The lastest driver set
from intel had the driver files for all three cards.
System 1 required the older e100bnt5.sys and luckily the
100VE could also used it. The 1000CT required that latest
e1000NT5.sys files. Yuo can see that by taking the driver
disk that contained all three drivers and following the
Support documents it created a mess.

This took me awhile to dignose and troubleshoot. I have
found the best approach is to use a diagnostic utility to
find out what the PCI ID number is. Then look at the .INF
file supplied by the vendor to see what files are required
for the paticular card you're working with(*.DLL, etc.)
Then only copy the files you need to i386 to make it
through text mode. In my case I was able to use the
latest drivers in the $OEM$\1\Drivers\Nic since the
problem was only with getting past the point where it
would start copying the files.

RIS with Windows 2000 is no fun. I am currently trying to
bring an XP image online with my 2000 configuration and I
am back to the battle as I write this. I wish you luck
and I hope what I experienced assists you in resolving
your problem.

Thanks,

Scott
-----Original Message-----
Hello to all here...

I post this question on other forums and no answers yet, I hope you can help
me....

The main problem here is that I make a RIS Server for my enterprise with 2
choices: Windows XP and Windows 2000 Professional..... When the users select
the Windows XP they have no problems (yes all the drives are there), but
with Windows 2000 no way.. we can't even install...

Well, searching in microsoft I found the KB315279: How to add a third-party
OEM Netword Adapter to an RIS Installation...

I made everything that is there... well I will present the steps here:

1. Run RISETUP and copy and Win2kPro cd as master image in folder Win2kPro
(Slipstream with Sp4).
3. Created a \DRV\NIC folder on the computer and gathered all drivers:
Pro100, Pro1000 there (mostly the *.cab, *.inf, *.sys).
3. created \$oem$\$1 under the s RIS Server and copied \drv\nic to it.
4. copied .inf's and .sys's to RIS SERVER - Win2kPro folder \i386.
Note: (following instructions from intel:
http://support.intel.com/support/network/sb/cs-000023- prd38.htm)
5. Also change the registry *.sif file in the \i386 \templates folder....
with the parameters:
[Unnatended]
DriverSigningPolicy = Ignore
OemPreInstall = yes
OemPnpDriversPath = drv\nic
6. Rebooted RIS server (easier then stopping and starting binlsvc).
7. PXE booted all clients: all can see the win2k image and start the
installation of the windows 2000 Pro Sp4.

However after finish the installation - Windows2000ProSP4 didn't install
anything (of the DRV\NIC Folder), why ? Not even the network drivers ? weird
?!!!!!

As you can see all the network cards are mostly Intel PRO 100....

And remember that if I install the computers with Windows XP (with the RIS
Server of course) all works perfectly....

Please help..

Thanks a lot

Miklos



.
Click to expand...
 
Great!!

That works now at least!!

Really very thanks Scott!!!


Miklos

I ran into the same type of problems using Intel cards.
Hopefully what I experienced and learned will assist you
with your problem:

I had 2 PCs and a laptop all running Intel Nics. I would
get the error "Does not contain the necessary drivers.
Blah Blah Blah." Here's the scenerio:
1. Desktop with Pro100b Card - 50 of them onsite.
2. Desktop with Pro100ve Integrated
3. Laptop with Pro1000ct Integrated

The default MS Windows 2K drivers would allow systems 1
and 2 to come up but not 3. If you install the new Intel
Drivers system 3 would come up but not 1 and 2. What I
found was that when you followed the Intel and Microsoft
support documents it would have you copy all of the DLL
files from the Drivers\Nic folder to i386 which would
replace e100bnt5.sys and e1000nt5.sys which would make
system 3 work but systems 1 and 2 would fail. By leaving
Microsoft's E100bnt5.sys file for systems 1 and 2 then
updating the E1000NT5.sys file in i386 this would get me
past the point where it could start copying files. You
can have all of the latest drivers from intel in the
$OEM$\1\Drivers\Nic folder since that appears to be used
later in the setup (GUI Setup). The lastest driver set
from intel had the driver files for all three cards.
System 1 required the older e100bnt5.sys and luckily the
100VE could also used it. The 1000CT required that latest
e1000NT5.sys files. Yuo can see that by taking the driver
disk that contained all three drivers and following the
Support documents it created a mess.

This took me awhile to dignose and troubleshoot. I have
found the best approach is to use a diagnostic utility to
find out what the PCI ID number is. Then look at the .INF
file supplied by the vendor to see what files are required
for the paticular card you're working with(*.DLL, etc.)
Then only copy the files you need to i386 to make it
through text mode. In my case I was able to use the
latest drivers in the $OEM$\1\Drivers\Nic since the
problem was only with getting past the point where it
would start copying the files.

RIS with Windows 2000 is no fun. I am currently trying to
bring an XP image online with my 2000 configuration and I
am back to the battle as I write this. I wish you luck
and I hope what I experienced assists you in resolving
your problem.

Thanks,

Scott
-----Original Message-----
Hello to all here...

I post this question on other forums and no answers yet, I hope you can help
me....

The main problem here is that I make a RIS Server for my enterprise with 2
choices: Windows XP and Windows 2000 Professional..... When the users select
the Windows XP they have no problems (yes all the drives are there), but
with Windows 2000 no way.. we can't even install...

Well, searching in microsoft I found the KB315279: How to add a third-party
OEM Netword Adapter to an RIS Installation...

I made everything that is there... well I will present the steps here:

1. Run RISETUP and copy and Win2kPro cd as master image in folder Win2kPro
(Slipstream with Sp4).
3. Created a \DRV\NIC folder on the computer and gathered all drivers:
Pro100, Pro1000 there (mostly the *.cab, *.inf, *.sys).
3. created \$oem$\$1 under the s RIS Server and copied \drv\nic to it.
4. copied .inf's and .sys's to RIS SERVER - Win2kPro folder \i386.
Note: (following instructions from intel:
http://support.intel.com/support/network/sb/cs-000023- prd38.htm)
5. Also change the registry *.sif file in the \i386 \templates folder....
with the parameters:
[Unnatended]
DriverSigningPolicy = Ignore
OemPreInstall = yes
OemPnpDriversPath = drv\nic
6. Rebooted RIS server (easier then stopping and starting binlsvc).
7. PXE booted all clients: all can see the win2k image and start the
installation of the windows 2000 Pro Sp4.

However after finish the installation - Windows2000ProSP4 didn't install
anything (of the DRV\NIC Folder), why ? Not even the network drivers ? weird
?!!!!!

As you can see all the network cards are mostly Intel PRO 100....

And remember that if I install the computers with Windows XP (with the RIS
Server of course) all works perfectly....

Please help..

Thanks a lot

Miklos



.
Click to expand...
Click to expand...
 
Back
Top