From: "Glenn Meadows" 

Yo guys.  Need some guru help here.

Have one XP SP2 machine, Athalon 2100+ system, that after the last patches
(and it did this once before), goes into a reboot loop.  Everything I've
found, so far, has been fruitless to resolve this.  I can move the HD to a
working system, and access the drive. I've done a commandline chkdsk /f/r
on the drives 2 partitions.

What I've done:

Tried to boot into SAFE mode, hangs at the display of the driver mup.sys.

Added /sos and /bootlog to the boot.ini file, as well as /basevideo  That
gets me the same displayed list of driver names, then I get a plain style
VGA screen that lists the boot OS version, etc., and then displays Boot
logging enabled.  BUT, in the spot where the boot log is supposed to be,
%systemroot%\ntblog.txt, there is only one dated back in August, not a
replaced one from today and that boot.

After that screen displays, the computer goes back to the bios start
screen, and initiates a reboot again.

How, when putting the HD into a working system, does one uninstall the
fixes that were applied during the latest patch application?

Where is the list and order of the drivers to load stored, so if the driver
that's hanging/crashing is after the one displayed, you can see what it is
to try to replace it, or rename it so you can attempt to bypass it?

Also, I am unable to get this system to boot from the CDROM of Windows XP.
The Boot from CD question appears for about 1 second, but immediately goes
right past to the HD boot.  Even if I turn OFF the HD in the Bios, the
computer STILL finds it, and tries to boot from it.

The next thing I'm going to try, is to rename mup.sys to mup.sy_ and see
what happens.  There is an older version of mup.sys in the service pack
uninstall directory, that I could try, and probably will, to see if that's
what's holding things up.

--
Glenn M.

--- BBBS/NT v4.01 Flag-5