Slow NIC detection

[Martin Zugec]

Hi, is it normal when detection of NIC is extremely slow (few minutes)?

I tried it on few computers and same result, also in VirtualPC it is extremely lazy.

I thought about using NetCard in Winbom.ini to define what NIC to detect, but isnt there any other solution?

[Martin Zugec]

I am still trying to solve this problem

The problem is not in detection - there is some problem with driver.

I am trying it on VirtualPC, however it still hangs on Updating driver (bartpe.exe -v -minint).

I just want to know:

a.) is there ANYBODY using BartPE on VirtualPC?

b.) is there anybody using BartPE networking?

Please respond, I freezed on this one

[Daan]

Did you already try to make an INF-cache to speed things up a bit?

[Martin Zugec]

Yes, however infcache is just for faster inf processing. My problem is after inf files are processed during updating driver

[Bilou_Gateux]

Slow NIC detection with all brands or only with a specific model?

I use BartPE with HP w/ Broadcom onboard, FSC w/ Intel 1000 onboard and NEC w/ VIA Rhine II onboard and don't have encountered slow detection...

Do you use original WinPE factory.exe or "Bartpe network support plugin" for NIC detection?

[Martin Zugec]

I tried only on Virtual PC yet...

I am using Bartpe Netowrk Support Plugin (PeNetCfg)...

[jachin]

I tried only on Virtual PC yet...

I am using Bartpe Netowrk Support Plugin (PeNetCfg)...

<{POST_SNAPBACK}>

I use BartPE in Virtual PC and Virtual Server on a weekly basis without any trouble at all. It is slightly slower than a physical machine but that is to be expected.

[Martin Zugec]

Could you please provide drivers you are using?

[mls15000]

I just added new broadcom gigabit drivers to my bart pe image to work with our new IBM desktops. After I added the driver, my old dell d400 will not grab an IP address until I renew it it and leave the configuration window open. The dell has a broadcom nic also, but something with the updated driver freakes it out. My old disks work great with intel pro 1000, old broadcom, intil pro 100, and a dlink driver. I use the old images on virtual PC all the time and it's really fast. no lag at all.

I use xpsp2 for the source disk, if that makes a difference. The only pluins I use are the RpcSS so i an use diskpart, I have ghost8, adaware, a3 filemanagement and i think thats it.

Edited July 26, 2005 by mls15000

[Martin Zugec]

Thx for reply, I dont use any plugin at all, except PENetCfg

I included only driver for VPC, built on XPSP2...

Could you please upload drivers for VPC? I tried one from DLink and one from Intel, but I encountered the same problems...

[mls15000]

I tried posting the drivers, but it wont let me. Something about my global limit. I just used standard XP drivers and put the inf, cat sys and dll needed files in 1 folder per driver. If you read the driver's inf file, it will tell yo uwhat files you need, the rest you can chuck away (most of the time).

[Martin Zugec]

Just to be sure: post please which files exactly (plus versions) did you use?

Thx for your help

[mls15000]

Fro the old broadcom I use: b57xp32.cat, b57xp32.inf and b57xp32.sys ver 5.30.0.0

The new broadcom netxtreme:

ver 7.97.0.0

b57win32.cat ,

*.inf,

*.pnf

b57xp32.sys

Intel Pro1000 ver 7.2.17.101

e1000325.cat

e1000325.din

e1000325.inf

e1000325.sys

e1000msg.dll

intelnic.dll

Misc intel folder:

e1e5032.di_

E1e5032.SY_

e1e5132.cat

e1e5132.di_

e1e5132.inf

E1e5132.sy_

e100a325.inf

e100ant5.inf

e100b325.cat

e100b325.di_

e100b325.inf

e100b325.sy_

e100bmsg.dl_

e100bnt5.di_

e100bnt5.sy_

e1000msg.dl_

e1000nt5.di_

E1000NT5.SY_

e1000325.cat

e1000325.di_

e1000325.inf

E1000325.sy_

EtCoInst.dl_

intelnic.dl_

ixgb325.cat

ixgb325.di_

ixgb325.inf

ixgb325.sy_

ixgb3251.di_

ixgb3251.sy_

ixgbmsg.dl_

Ncs2Setp.dl_

PROUnstl.ex_

Hope this helps some.

[Martin Zugec]

Nope, I am only interested in Virtual PC. I am using VPC 2004 SP1 if that matters...

[mls15000]

virtual PC doesn't use drivers. It just uses a virtual driver to connect through the main OS. You can specify in the virtual pc settings which nic you want to connect through.