winipe on ris server with DELL SX270

[Peter M.]

Hi,

I did the right steps to include winpe as aboot option on my RIS-Server
(Server 2003).
I also added the driver for the Intel Pro/1000 to \$OEM$/$1/Drivers/Nic (XP
Driver) and
also to the \I386 Folder. (I also did the changes in e100b325.inf like shown
on

http://www.intel.com/support/network/sb/cs-000023-prd38.htm
in section For XP* and Windows Server 2003 - e100b325.xxx and e1000325.xxx

This step is necessary to work with this nic in this environment.


When I start from network WinPE starts up (the striped bar gets filled
entirely).
After a short moment, I think very closely before the Logo should appear,
there
is an error message, that the driver e1000325.sys caused
an unexpected error (21) in Line xxxx fo d:\xpsp1\base.....\setup.c
Seems to be an error out of the c-source of the driver.

Crazy, I don't have any folder D:\xpxp1

I think there is a problem with WinPE itself and this configuration or the
driver from intel.
I also tried driver packages from Dell - same problem.

I want to use this custom WinPE version on my RIS-Server to deploy a
classroom.

Any ideas?

Thanks in advance.

Regards

Peter M.

 

[JoeBlow]

What you'll need to do is get the Windows 2000 Intel .sys file from the
drive set and copy it to i386\system32\drivers (overwriting anything already
there), as well as copy your Windows 2000 Intel .inf file to \i386\inf
folder. Now for the interesting part... What i did to fix the bluescreen,
find an inf called nete1000.inf . This file is the built-in driver for the
Intel gig nic that uses the E1000NT5.sys driver in the i386\system32\drivers
directory. Delete the nete1000.inf file. Restart the binlsvc (Remote
Installation) service for good measure and everything should work fine
there. I've done this for our GX260's and D600's that had the same problem.
With the D600's I had to swap out the broadcom gig nic drivers using this
same process and also using the 2000 drivers. However, I had to use the
Windows 2000 drivers in the I386 directory for the initial RIS loading of
drivers, then when PE loaded and winbom detected the NIC, I had to place the
WXP drivers into the inf and drivers directory as stated above otherwise I'd
get an even weirder BSOD.

 

[Peter M.]

Hi,

What you'll need to do is get the Windows 2000 Intel .sys file from
the drive set and copy it to i386\system32\drivers (overwriting
anything already there), as well as copy your Windows 2000 Intel .inf
file to \i386\inf folder. Now for the interesting part... What i did
to fix the bluescreen, find an inf called nete1000.inf . This file is
the built-in driver for the Intel gig nic that uses the E1000NT5.sys
driver in the i386\system32\drivers directory. Delete the
nete1000.inf file. Restart the binlsvc (Remote Installation) service
for good measure and everything should work fine there. I've done
this for our GX260's and D600's that had the same problem. With the
D600's I had to swap out the broadcom gig nic drivers using this same
process and also using the 2000 drivers. However, I had to use the
Windows 2000 drivers in the I386 directory for the initial RIS
loading of drivers, then when PE loaded and winbom detected the NIC,
I had to place the WXP drivers into the inf and drivers directory as
stated above otherwise I'd get an even weirder BSOD.

I really helped me a lot. WinPE is up and running now. I also have
network connection under PE, but Starting up factory.exe in WinPE
Mode brings one error message saying something like no
network adapter or something. I can ping, and can map drives,
but ipconfig does bring an error.

Any ideas? - This is not essential but would be nice to startup without
errors to click away.

Thanks.

Greets Peter

 

[JoeBlow]

I wouldn't bother with Factory.exe, instead load these lines from your
startnet.cmd.....

:********************************
title Loading PE Environment ...
color 0a

echo.
echo. Loading Network Components ...
regsvr32 /s netcfgx.dll

echo.
echo. Detecting Network Adapter ...
factory -minint

echo.
echo. Configuring TCP/IP ...
netcfg -winpe

echo.
echo. Starting Service(s) ...
net start dhcp
net start nla

echo.
echo. Refreshing IP/DNS/WINS Information ...
ipconfing /renew > nul
:********************************

You'll need the ipconfig /renew at the end to pick up the correct WINS
servers (if you use them) for some weird reason.
After that net use and ping work great.