Jeff said:
Is there a way to find out the order in which drivers and services load
in XP
SP2? I have a XP Home SP2 PC that freezes immediately after loading the
mup.sys file. I cannot figure out what driver or file is causing the
lockup,
but am sure it has to be the one right after mup.sys. Any insight would
be
greatly appreciated. Thanks!
The drivers and services don't always load in quite the same order. You
can pursuade XP to create a log file of what loads during bootup.
Can you boot into safe mode? If not can you boot into safe mode with
command line? If you can't then you will need a bootable Floppy or a CD
with a text editor on it (EDIT.COM or similar).
To force the log file, follow these steps:
* Right-click My Computer on the Start menu and choose Properties.
* On the Advanced tab, click the Settings button in the Startup And
Recovery section.
* In the Startup And Recovery dialog box, click the Edit button to open
Boot.ini in Notepad.
* Under [Operating Systems], select the entire line that contains the
settings for your default operating system choice and copy it to the
bottom of the list.
* Append the following switches to the end of the newly copied line:
/bootlog
While you are at it, you may want to create another entry and add:
/safeboot:minimal /sos /bootlog
* You may want to change the timeout value to something like 5 (seconds)
to give time for you to select the option and not too long to have to wait
for your pc.
* Change the description in quotation marks to "Windows XP - Logged Boot"
(or similar)
* If you have added the optional line call it "Windows XP - Safe Logged
Minimal" (or similar) and then save the file.
* Reboot windows.
* You should be presented with a Boot menu, select "Windows XP - Logged
Boot" and allow it to boot. As it boots windows writes a log file
BOOTLOG.TXT to the %systemroot% directory (usually C:\WINDOWS)
* If it hangs (as you suggest it will), the errant driver or file will be
the last one listed in the log file.
* If you reboot and select the optional safemode option, it may boot
enough to let you access the log file in windows otherwise you will need
to boot from the floppy or CD and examine the file with the editor.