hi,
It takes about one minute. It's too long for the operator.
Is it possible to make this command faster ?
There is a DHCP server on the lan but with or without, it's too long.
Is it the NIC detection which take time ? there is only one and always the same one in all computers (vitual nic under hyperV).
Thanks.
noël
wpeutil networkiniitalize is too slowly
Started by
noel
, Mar 30 2010 09:41 PM
3 replies to this topic
#1
noel
-
- Advanced user
-
- 178 posts
Frequent Member
- Location:nantes
-
France
Posted 30 March 2010 - 09:41 PM
#2
steve6375
-
- Developer
-
- 7566 posts
Platinum Member
- Location:UK
- Interests:computers, programming (masm,vb6,C,vbs), photography,TV,films
-
United Kingdom
Posted 17 May 2010 - 11:19 AM
does netcfg -winpe work?
#3
wimb
-
- Developer
-
- 3756 posts
Platinum Member
- Interests:Boot and Install from USB
-
Netherlands
Posted 17 May 2010 - 03:50 PM
In case of only one and known NIC to install you can try simply to use startnet.cmd withhi,
Is it the NIC detection which take time ? there is only one and always the same one in all computers (vitual nic under hyperV).
startnet.cmd
wpeinit drvload.exe X:\Windows\inf\net_yours.infhttp://www.boot-land...showtopic=11408
#4
steve6375
-
- Developer
-
- 7566 posts
Platinum Member
- Location:UK
- Interests:computers, programming (masm,vb6,C,vbs), photography,TV,films
-
United Kingdom
Posted 17 May 2010 - 05:04 PM
[tip]hi,
It takes about one minute. It's too long for the operator.
Is it possible to make this command faster ?
There is a DHCP server on the lan but with or without, it's too long.
Is it the NIC detection which take time ? there is only one and always the same one in all computers (vitual nic under hyperV).
Thanks.
noël
to speed up slightly try
wpeinit -unattend=x:\windows\system32\fred.xml
and make sure the file does not exist. This can save a few seconds as otherwise it will look for unattend.xml on all drives.
[/tip]
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users
