Mini-Setup Networking component delays for 10 mins

  • Thread starter Thread starter Brett G
  • Start date Start date
B

Brett G

Hi,

I've seen some posts regarding this issue but no explanantions or
resolutions as of yet.

Basically we are deploying a Windows XP SP1 sysprep'd image (no -pnp
or -bmsd switches while running sysprep) to ACER TravelMate laptops
(models 630/650/660)

Everything seems to run smoothly and no errors are reported, however
when mini-setup runs the networking installation it seems to chug for
approximately 10 mins before continuing normally. There does not seem
to be any ill effects on the system after this.

I'm just really curious to understand what is happening here and
resolving it. One of the logs I looked into mentioned something along
the lines of the driver signing policy reverting back to the default
(after a 10min delay). I checked the driver signing policy and it is
the default, "warn before installation".

Thanks in advance!!!

Brett
 
I haven't received a response so I thought I might add
some more info to the thread to see if I can provoke some
discussion at least!!!

This is an extract from the setupapi.log file:

[2004/02/05 11:38:22 776.173]
#-199 Executing "C:\WINDOWS\system32\setup.exe" with
command line: setup.exe -newsetup -mini
#-166 Device install function: DIF_PROPERTYCHANGE.
#I292 Changing device properties
of "ROOT\MS_PSCHEDMP\0002".
#I306 DICS_START: Device has been started.
[2004/02/05 11:46:45 1640.28]
#-198 Command line processed: "C:\WINDOWS\system32
\rundll32.exe" C:\WINDOWS\system32
\dneinobj.dll,ReInstallDne
#-166 Device install function: DIF_PROPERTYCHANGE.
#I292 Changing device properties of "ROOT\DNI_DNEMP\0000".
#I306 DICS_START: Device has been started.
[2004/02/05 11:46:45 1640.39]

And this is from the netsetup.log

02/05 11:38:15 --------------------------------------------
02/05 11:38:15 NetpDoDomainJoin
02/05 11:38:15 NetpMachineValidToJoin: 'AMM03774'
02/05 11:38:15 NetpGetLsaPrimaryDomain: status: 0x0
02/05 11:38:15 NetpMachineValidToJoin: status: 0x0
02/05 11:38:15 NetpJoinWorkgroup: joining
computer 'AMM03774' to workgroup 'WORKGROUP'
02/05 11:38:15 NetpValidateName: checking to see
if 'WORKGROUP' is valid as type 2 name
02/05 11:38:15 NetpCheckNetBiosNameNotInUse
for 'WORKGROUP' [ Workgroup as MACHINE] returned 0x0
02/05 11:38:15 NetpValidateName: name 'WORKGROUP' is valid
for type 2
02/05 11:38:16 NetpSetLsaPrimaryDomain: for 'WORKGROUP'
status: 0x0
02/05 11:38:16 NetpJoinWorkgroup: status: 0x0
02/05 11:38:16 NetpDoDomainJoin: status: 0x0
02/05 11:46:43 --------------------------------------------
02/05 11:46:43 NetpValidateName: checking to see
if 'AMM03774' is valid as type 1 name
02/05 11:46:44 NetpCheckNetBiosNameNotInUse for 'AMM03774'
[MACHINE] returned 0x0
02/05 11:46:44 NetpValidateName: name 'AMM03774' is valid
for type 1
02/05 11:46:44 --------------------------------------------


Notice from 11:38 to 11:46 there is a delay...this is what
I'm trying to work out? Is it trying to search for a
domain to join or something?

Any help???

Brett
 
Back
Top