Hi!

I'm really tired!

I did try almost everything...

I remove every driver injected in the WinPE Image...

I do those commands to create the CD...

MKIMG.CMD X: C:\WinPE /WMI

BUILDOPTIONALCOMPONENTS.VBS /ado /hta /wsh /s:X: /d:C:\WinPE

then I burn it and I always get stuck when I run Factory -winpe in the part named "Starting Networking"

I added this line in my startnet.cmd before factory -winpe.

regsvr32 /s netcfgx.dll

Doesn't work either...

So, what should I do now... please help me!

Thanks a lot...

ShrimpyOne

What are you trying to do? Start networking alone or with Factory to connect to do some installs?

If you are trying to use this as a recovery tool and want to be able to cannect to a remote machine or the internet your statnet.cmd should look like this:

regsvr32 /s netcfgx.dll
factory -minint
netcfg -v -winpe
net start dhcp
net start nla

Edited September 21, 200520 yr by likuidkewl

Actually, factory -winpe runs the exact same code as what you just specified, and will additionally process a winbom.ini. To the original poster - are you sure your NIC driver is in WinPE? Have you added it if not?

To add another question.

What nic do you got and on wich motherboard?

Chances are that someone here got it working

Hi

My board is an Asus A7N8X with an on board nvidia nic and a 3c905...

THe nforce nics has been a little tricky but the 905 should be easy. I'll se if i can find a Dell during the day and test it.

are you running the two nics in the same machine?

If you are, try dissabeling the nforce nic

I had this problem with the "Starting Network" hanging on our Dell GX 150 PCs with 3com nic on board. I had to go into the BIOS and set the IRQ for the nic to be different than any other device and that go it past the "Starting Network" hang.

I was using a modified kernel that was my problem, see the other post for information on custom kernel...