Windows NT boot problems
23 July 2004
Profile XP Service Manual
35
LastKnownGood is loaded in when the user presses the space bar at the prompt before
Windows NT begins to load.
It is important to remember that when you invoke LastKnownGood, any system
configuration changes made since the last successful start up are discarded. And once
you successfully log on, the configuration used becomes LastKnownGood
Windows NT boot problems
Possible problems that occur during the Windows NT boot sequence are listed in the
following table. These problems can be repaired using the emergency repair process
described later in this chapter.
Problem
Probable cause
Windows boots without displaying Boot Loader Menu
or
Problem in Windows NT Path
This will occur if Boot.ini is missing. If Boot.ini is
missing NTLDR will boot from the \winnt directory by
default. If this is the correct directory, Windows NT
boots automatically. If not, the following message
appears:
Windows NT could not start because the following
file is missing or corrupt:
\winnt root\system32\ntoskrnl.exe
Please reinstall a copy of the above file.
New boot loader operating system menu item appears
If the path for the default operating system in the boot
loader section of the boot.ini file does not match any
paths in the operating system portion of the file a new
entry, “NT (default)” will be added to the operating
system portion of the file. This new entry will be
highlighted and used to boot NT if user does not make
a selection.
The following message is displayed:
OS Loader V4.0
Windows NT could not start because of a computer disk
hardware configuration. Could not read from the selected
boot disk. Check boot path and disk hardware. Please check
the Windows NT (TM) documentation about hardware disk
configuration and your hardware reference manuals for
additional information.
Invalid device (Name, for instance) in Windows NT
path in boot.ini.
The following error message is displayed:
Boot: Couldn’t find NTLDR
Please insert another disk
NTLDR file is corrupt or missing
The following error message is displayed:
NTDETECT V1.0 Checking Hardware…
NTDETECT failed
Ntdetect.com file is corrupt or missing
The following error message is displayed:
Windows NT could not start because the following file is
missing or corrupt:
\winnt root\system32\ntoskrnl.exe
Please re-install a copy of the above file.
Ntoskrnl.exe file is corrupt or missing
The following error message is displayed:
I/O Error accessing boot sector file
multi (0) disk (0) rdisk (0) partition (1):\bootsect.dos
Bootsect.dos file is corrupt or missing
Summary of Contents for Profile XP PVS1000
Page 4: ...Product Support 4 Profile XP Service Manual 23 July 2004 ...
Page 28: ...Preface 28 Profile XP Service Manual 23 July 2004 ...
Page 32: ...Chapter 1 Characterizing the problem 32 Profile XP Service Manual 23 July 2004 ...
Page 50: ...Chapter 4 Troubleshooting audio problems 50 Profile XP Service Manual 23 July 2004 ...
Page 54: ...Chapter 5 Troubleshooting timecode problems 54 Profile XP Service Manual 23 July 2004 ...
Page 66: ...Chapter 6 Troubleshooting storage system problems 66 Profile XP Service Manual 23 July 2004 ...
Page 76: ...Chapter 7 Troubleshooting video network problems 76 Profile XP Service Manual 23 July 2004 ...
Page 82: ...Chapter 9 Troubleshooting channel control problems 82 Profile XP Service Manual 23 July 2004 ...
Page 88: ...Chapter 10 Routine maintenance 88 Profile XP Service Manual 23 July 2004 ...
Page 129: ...Viewing subsystem properties 23 July 2004 Profile XP Service Manual 129 ...
Page 150: ...Appendix A Diagnostic Tools 150 Profile XP Service Manual 23 July 2004 ...
Page 152: ...Appendix A Diagnostic Tools 152 Profile XP Service Manual 23 July 2004 ...
Page 156: ...Appendix A Diagnostic Tools 156 Profile XP Service Manual 23 July 2004 ...
Page 172: ...Index 172 Profile XP Service Manual 23 July 2004 ...