xp repair reinstall hangs at Installing Network
- From: wyocowboy <wyocowboy@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 6 Feb 2006 13:32:02 -0800
So far, nothing found on google web or groups has shed light on this problem,
and I did not get any hits when searching in this group, so here goes...
According to... http://support.microsoft.com/default.aspx?scid=kb;en-us;824125
it is possible to replace a motherboard in a working xp system with a
different motherboard. It would seem to follow that one could move a hard
drive containing a working xp installation into a new tower, carrying over
whatever PCI/AGP/AMR cards were installed, since this is essentially the same
as replacing the motherboard. In order to avoid the weeks of work that would
follow of trying to recreate these highly customized installations, that is
what we did with our two bench machines, with widely different results.
Both machines were sisters, using the same hardware (other than the CD
drives) and same on-board NIC. In the case of my machine, it all went well
and did not hang at any point. In the case of my boss's machine, he went
through a little over a week of fighting with it to get it to go. His was
experiencing the infamous hang with "32 minutes remaining, installing
network" that does not seem to have a answer. He did eventually get his to
go, using a convoluted series of kludges.
As a follow-on experiement, we kept his original machine and hard drive
intact so that we could try to figure out the cause - he had used DriveImage
to copy his working installation onto a larger hard drive and he then
performed the repair reinstall on that hard drive, after making sure that it
booted with no problems in his old tower. I did the same with my migration,
and since DriveImage did not flag any errors, we don't think this was a
factor in the problems he was seeing. FWIW, one difference between his
installation and mine was that he is using FAT32 and mine is NTFS.
For the experiment, I used my new tower, using the same motherboard in both
cases - with the image of my hard drive and the image of his. Although this
was a different motherboard than what is in his new system, the same problem
occurred, which indicates that the failure was not tied to the particular
'new' motherboard. In other words, the failure was replicated with his image
with two different motherboards.
The problem in this case is that the intallation stalls at 32 minutes,
during the "installing network" phase. No matter how long you let it sit, it
does not progress or timeout. During this time, one can use shift-F10 to get
to a command prompt and do most anything that can be done on a working
system. Taskmgr shows the system mostly idle.
Note that it makes no difference if the motherboard NIC is disabled or not,
the problem still occurs (I tried several scenarios, with fresh images of the
boss's hard drive). In the case of my upgrade, the onboard NIC was detected
by the repair reinstall and worked.
I checked the setupapi.log on the problem image, which shows the last entry
as "#I289 Removing device "root\ms_ndiswannbfout\0004" after it had been
sitting in the hung state for 15 minutes or so. Launching the compmgmt.msc
and browsing the running services shows DCOM status of "starting" as the only
apparent anomaly, but this was its status during my successful upgrade.
Setuperr.log shows multiple entries for "Error: setup encountered an error
while trying to set system security. An extended error has occurred." Since
this log does not time/date stamp the entries (thanks!) it is not possible to
correlate any of these to the problem. FWIW, the successful upgrade had just
one of these same entries in its setuperr.log.
Note that this stall has nothing to do in particular with a repair reinstall
or replacing a motherboard. It has been reported on the web with new
installs, clean reinstalls, repair reinstalls, and upgrade of 98/ME to XP,
etc, so it may have more than one cause. Since we are a repair shop it would
be nice to know how to deal with this type of hang. The good news is that we
have never run into it on a fresh install, or when upgrading the OS to XP.
Any ideas?
.
- Prev by Date: Re: Screen Resolution?
- Next by Date: Re: blue screen/reboot
- Previous by thread: blue screen/reboot
- Next by thread: Unable to rename or delete NTFS folders
- Index(es):
Relevant Pages
|
