| The term boot comes from the word bootstrap and describes the method by which the laptop becomes operational. Just as you pull on a large boot by the small strap attached to the back, a laptop loads a large operating system by first loading a small program that can then pull the operating system into memory. The chain of events begins with the application of power and finally results in a fully functional computer system with software loaded and running. Each event is triggered by the event before it and initiates the event after it. How does understanding the boot process help you solve problems? Well, for one, if you can't start your system, then tracing the system boot process might help you find the location of a problem if you examine the error messages the system displays when the problem occurs. Additionally, Windows can generate a bootlog that you can then use to trace exactly when a failure occurred. If you see an error message that is displayed by only a particular program, you can be sure the program in question was at least loaded and partially running. Combine this information with the knowledge of the boot sequence, and you can at least tell how far the system's startup procedure had progressed before the problem occurred. You usually should look at whichever files or disk areas were being accessed during the failure in the boot process. Error messages displayed during the boot process and those displayed during normal system operation can be hard to decipher. However, the first step in decoding an error message is knowing where the message came fromwhich program actually generated or displayed it. The following programs and devices are capable of displaying error messages during the boot process. Operating system independent: Operating system dependent. DOS and Windows 9x/Me use the following files during system startup: -
System files ( IO.SYS/IBMBIO.COM and MSDOS.SYS/IBMDOS.COM ) -
Device drivers (loaded through CONFIG.SYS or the Windows Registry SYSTEM.DAT ) -
Shell program ( COMMAND.COM in DOS) -
Programs run by AUTOEXEC.BAT , the Windows Startup group , and the Registry -
Windows ( WIN.COM ) Windows NT/2000/XP use the following files during system startup: -
Ntldr -
Boot.ini -
Bootsect.dos (multiple-boot systems only) -
Ntbootdd.sys (loaded only for SCSI drives ) -
Ntdetect.com -
Ntoskrnl.exe -
Hal.dll -
Files in systemroot \System32\Config (Registry) -
Files in systemroot \System32\Drivers (drivers) The first portion of the startup sequence is operating system independent , which means these steps are the same for all laptops, no matter which operating system is installed. The latter portion of the boot sequence is operating system dependent , which means those steps can vary depending on which operating system is installed or being loaded. The following section examines the operating systemindependent startup sequence and provides a detailed account of many of the error messages that might occur during this process. I also provide solutions to these error messages so you can get your system working as quickly as possible. The Boot Process: Operating System Independent If you have a problem with your system during startup and can determine where in this sequence of events your system has stalled, you know which events have occurred and probably can eliminate each of them as a cause of the problem. The following steps occur in a typical system startup regardless of which operating system you are loading: -
You switch on electrical power to the system. -
The power supply performs a Power On Self Test (known as the POST). When all voltages and current levels are acceptable, the supply indicates that the power is stable and sends the Power_Good signal to the motherboard. The time from switch-on to Power_Good is normally between .1 and .5 seconds. -
The microprocessor timer chip receives the Power_Good signal, which causes it to stop generating a reset signal to the microprocessor. -
The microprocessor begins executing the ROM BIOS code, starting at memory address FFFF:0000. Because this location is only 16 bytes from the very end of the available ROM space, it contains a JMP (jump) instruction to the actual ROM BIOS starting address. -
The ROM BIOS performs a test of the central hardware to verify basic system functionality. Any errors that occur are indicated by audio "beep" codes because the video system has not yet been initialized . If the BIOS is Plug and Play (PnP), the following steps (steps 69) are executed; if not, skip to step 10. -
The Plug and Play BIOS checks nonvolatile random access memory (RAM) for input/output (I/O) port addresses, interrupt request (IRQ) lines, direct memory access (DMA) channels, and other settings necessary to configure PnP devices on the computer. -
All Plug and Play devices found by the Plug and Play BIOS are disabled. -
A map of used and unused resources is created. -
The Plug and Play devices are configured and reenabled, one at a time. If your computer does not have a Plug and Play BIOS, PnP devices are initialized using their default settings. These devices can be reconfigured dynamically when Windows starts. At that point, Windows queries the Plug and Play BIOS for device information and then queries each Plug and Play device for its configuration. -
The BIOS performs a video ROM scan of memory locations C000:0000C780:0000 looking for video adapter ROM BIOS programs contained on a video adapter found either on a card plugged into a slot or integrated into the motherboard. If the scan locates a video ROM BIOS, it is tested by a checksum procedure. If the video BIOS passes the checksum test, the ROM is executed; then the video ROM code initializes the video adapter and a cursor appears onscreen. If the checksum test fails, the following message appears: C000 ROM Error Because laptop computers don't use removable video cards (the video circuit is either integrated into the motherboard's chipset or a separate chip is built in to the motherboard), this error means you need to have your system serviced. -
If the BIOS finds no video adapter ROM, it uses the motherboard ROM video drivers to initialize the video display hardware, and a cursor appears onscreen. -
The motherboard ROM BIOS scans memory locations C800:0000DF80:0000 in 2KB increments for any other ROMs located on any other adapter cards (such as SCSI adapters). If any ROMs are found, they are checksum-tested and executed. These adapter ROMs can alter existing BIOS routines and establish new ones. -
Failure of a checksum test for any of these ROM modules causes this message to appear: XXXX ROM Error Here, the address XXXX indicates the segment address of the failed ROM module. If you have a PC Card or CardBus card installed, shut down the system, remove the card and then restart the system. If the error is no longer displayed, the ROM built in to the card is defective, and the card should be replaced . If the error message still appears, your system should be serviced, because the error is probably coming from ROM on the motherboard. -
The ROM BIOS checks the word value at memory location 0000:0472 to see whether this start is a cold start or a warm start. A word value of 1234h in this location is a flag that indicates a warm start, which causes the BIOS to skip the memory test portion of the POST. Any other word value in this location indicates a cold start, and the BIOS performs the full POST procedure. Some system BIOSes let you control various aspects of the POST procedure, making it possible to skip the memory test, for example, which can be lengthy on a system with a lot of RAM. -
If this is a cold start, the full POST executes; if this is a warm start, a mini-POST executes, minus the RAM test. Any errors found during the POST are reported by a combination of audio and displayed error messages. Successful completion of the POST is usually indicated by a single beep (with the exception of some Compaq computers, which beep twice). See Chapter 16, "Problem Solving and Troubleshooting," for information about error messages, beep codes, and solutions. -
The ROM BIOS searches for a boot record at cylinder 0, head 0, sector 1 (the very first sector) on the default boot drive. At one time, the default boot drive was always the first floppy disk (A:) drive. However, the BIOSes on today's systems often enable you to select the default boot device and the order in which the BIOS will look for other devices to boot from, if necessary, using a floppy disk, hard disk, or even a CD-ROM drive in any order you choose. This sector is loaded into memory at 0000:7C00 and tested. If a disk is in the drive but the sector can't be read, or if no disk is present, the BIOS continues with step 19. Tip If you do want to boot from a CD-ROM, be sure the CD-ROM drive is specified before the hard disk in the boot devices menu in your BIOS setup. To ensure that you can boot from an emergency CD or floppy disk, I recommend setting the CD-ROM drive as the first boot device and the floppy drive as the second boot device. A hard disk containing your operating system should be the third device in the boot device list. This enables you to always be ready for an emergency. So long as you do not boot with a CD or floppy loaded, the BIOS bypasses both the CD-ROM and floppy disk drives and boots from the hard drive. Note that not all operating system CDs are bootable. Windows 95 CDs are not bootable; however, with Windows 98, Microsoft made the operating system CD bootable, but only for OEM (original equipment manufacturer) versions. This does not extend to retail versions of these Windows CDs. Windows NT 4.0 and later, including Windows 2000 and XP, are shipped on bootable CDs. See Chapter 10, "Removable Storage," for information on how to make a bootable CD. Most recovery CDs packaged with laptop computers can also be used to boot the system and start the software/operating system reinstallation process. -
If you are booting from a floppy disk and the first byte of the volume boot record is less than 06h, or if the first byte is greater than or equal to 06h and the first nine words contain the same data pattern, this error message appears and the system stops: 602-Diskette Boot Record Error If you've left the floppy disk in the drive by mistake, remove it and restart the system. If the floppy disk is supposed to be bootable, reformat it with the /S (system) or Boot Files option and restart your system with it (use the File menu in Windows Explorer of a working system to access the Format option). -
If the volume boot record can't find or load the system files, or if a problem was encountered loading them, one of the following messages appears: Non-System disk or disk error Replace and strike any key when ready Non-System disk or disk error Replace and press any key when ready Invalid system disk_ Replace the disk, and then press any key Disk Boot failure Disk I/O Error All these messages originate in the volume boot record (VBR) and relate to VBR or system file problems. The exact error message you see depends upon the BIOS version used by your laptop. The most common cause for these error messages is leaving a floppy disk in drive A:. Remove the floppy disk and press a key to retry the boot process. -
If no boot record can be read from drive A: (such as when no disk is in the drive), the BIOS then looks for a master boot record (MBR) at cylinder 0, head 0, sector 1 (the very first sector) of the first hard disk. If this sector is found, it is loaded into memory address 0000:7C00 and tested for a signature. -
If the last two (signature) bytes of the MBR are not equal to 55AAh, software interrupt 18h (Int 18h) is invoked on most systems. This causes the BIOS to display an error message that can vary for different BIOS manufacturers, but it's often similar to one of the following messages, depending on which BIOS you have. IBM BIOS: The IBM Personal Computer Basic_ Version C1.10 Copyright IBM Corp 1981 62940 Bytes free_ Ok_ Most IBM computers since 1987 display a strange character graphic depicting the front of a floppy drive, a 3 1/2'' disk, and arrows prompting you to insert a disk in the drive and press the F1 key to proceed. AMI BIOS: NO ROM BASIC - SYSTEM HALTED Compaq BIOS: Non-System disk or disk error replace and strike any key when ready Award BIOS: DISK BOOT FAILURE, INSERT SYSTEM DISK AND PRESS ENTER Phoenix BIOS: No boot device available - strike F1 to retry boot, F2 for setup utility or No boot sector on fixed disk - strike F1 to retry boot, F2 for setup utility Note that although some of these messages are similar to those caused by leaving a floppy disk in drive A: (step 18), some are different. Although the messages vary from BIOS to BIOS, the cause for each relates to specific bytes in the MBR, which is the first sector of a hard disk at the physical location cylinder 0, head 0, sector 1. The problem involves a disk that either has never been partitioned or has had the master boot sector corrupted. During the boot process, the BIOS checks the last two bytes in the MBR (the first sector of the drive) for a signature value of 55AAh. If the last two bytes are not 55AAh, an interrupt 18h is invoked, which calls the subroutine that displays one of the error messages just shown, which basically instructs the user to insert a bootable floppy to proceed. The MBR (including the signature bytes) is written to the hard disk by the FDISK or DISKPART program (which are used by various versions of DOS or Windows to partition the hard disk). Immediately after a hard disk is low-level formatted, all the sectors are initialized with a pattern of bytes, and the first sector does not contain the 55AAh signature. In other words, these ROM error messages are exactly what you see if you attempt to boot from a hard disk that has been freshly low-level formatted but has not yet been partitioned. You should see an error message like this only if you have replaced the original hard disk in your laptop with another hard disk that has not yet been partitioned. -
The MBR searches its built-in partition table entries for a boot indicator byte marking an active partition entry. -
If none of the partitions are marked active (bootable), the BIOS invokes software interrupt 18h, which displays an error message (refer to step 20). This error could happen if you partition a hard disk into a primary and extended partition with FDISK and forget to mark the primary partition as active. -
If any boot indicator byte in the MBR partition table is invalid, or if more than one indicates an active partition, the following message is displayed and the system stops: Invalid partition table This error could indicate physical damage to your drive or problems caused by a computer virus. If your drive contains valuable data, you should use a data-recovery program or service to retrieve any readable data from the drive. See "Laptop Data Recovery" later in this chapter. -
If an active partition is found in the MBR, the partition boot record from the active partition is loaded and tested. If the partition boot record is read successfully, proceed to Step 27. -
If the partition boot record can't be read successfully from the active partition within five retries because of read errors, the following message is displayed and the system stops: Error loading operating system -
The hard disk's partition boot record is tested for a signature. If it does not contain a valid signature of 55AAh as the last two bytes in the sector, the following message is displayed and the system stops: Missing operating system -
The volume boot record is executed as a program. This program looks for and loads the operating system kernel or system files. To see what happens next , go to the appropriate boot process section for your operating system. -
If the volume boot record can't find or load the system files, or if a problem was encountered loading them, one of the following messages appears: Non-System disk or disk error Replace and strike any key when ready Non-System disk or disk error Replace and press any key when ready Invalid system disk_ Replace the disk, and then press any key Disk Boot failure Disk I/O Error All these messages originate in the volume boot record (VBR) and relate to VBR or system file problems. Check the following to recover from these problems: -
If you want to boot from the hard disk, remove any floppy disk in drive A: and restart the computer. -
If you have recently opened the system, make sure the hard disk is properly connected to the data/power cable and the motherboard. -
Boot the system with an emergency boot/system disk or CD and attempt to read the contents of the hard disk. If the hard disk can be read, use the appropriate remedy to transfer your boot files: -
With DOS or Windows 9x, use the Sys C: command to transfer the boot files. -
With Windows Me, rerun the Setup program to transfer the boot files. -
With Windows 2000/XP, start the Recovery Console from the Windows CD and run Fixboot. If the hard disk's contents can't be read and the drive contains valuable data, you should use a data-recovery program or service to retrieve any readable data from the drive. See "Laptop Data Recovery" later in this chapter. From this point forward, what happens depends on which operating system you have. The operating systemdependent boot procedures are discussed in the next several sections. The DOS Boot Process If you use an older laptop that runs Windows 3.x or Windows for Workgroups 3.x, it actually boots up with DOS before Windows starts. Here's the boot process used by DOS: -
The initial system file (called IO.SYS with MS-DOS or IBMBIO.COM with IBM DOS) is executed. -
The initialization code in IO.SYS/IBMBIO.COM copies itself into the highest region of contiguous DOS memory and transfers control to the copy. The initialization code copy then relocates MSDOS.SYS over the portion of IO.SYS in low memory that contains the initialization code because the initialization code no longer needs to be in that location. -
The initialization code executes MSDOS.SYS (or IBMDOS.COM ), which initializes the base device drivers, determines equipment status, resets the disk system, resets and initializes attached devices, and sets the system default parameters. -
The full DOS file system is active, and control is returned to the IO.SYS initialization code. -
The IO.SYS initialization code reads the CONFIG.SYS file multiple times. -
When CONFIG.SYS is loaded, the DEVICE statements are first processed in the order in which they appear. Any device driver files named in those DEVICE statements are loaded and executed. Then, any INSTALL statements are processed in the order in which they appear; the programs named are loaded and executed. The SHELL statement is processed and loads the specified command processor with the specified parameters. If the CONFIG.SYS file contains no SHELL statement, the default \COMMAND.COM processor is loaded with default parameters. Loading the command processor overwrites the initialization code in memory (because the job of the initialization code is finished). During the final reads of CONFIG.SYS , all the remaining statements are read and processed in a predetermined order. Therefore, the order of appearance for statements other than DEVICE , INSTALL , and SHELL in CONFIG.SYS is of no significance. An incorrectly spelled command in CONFIG.SYS or a reference to a driver file that doesn't exist in the specified location triggers an error message, but the computer will boot anyway. -
If AUTOEXEC.BAT is present, COMMAND.COM loads and runs AUTOEXEC.BAT . After the commands in AUTOEXEC.BAT have been executed, the DOS prompt appears (unless AUTOEXEC.BAT calls an application program or shell of some kind, such as Win.com [the Windows loader], in which case the user might operate the system without ever seeing a DOS prompt). An incorrectly spelled command in AUTOEXEC.BAT or a reference to a file that doesn't exist in the specified location triggers an error message, but the computer will boot anyway. -
If no AUTOEXEC.BAT file is present, COMMAND.COM executes the internal DATE and TIME commands, displays a copyright message, and displays the DOS prompt. Some minor variations from this scenario are possible, such as those introduced by other ROM programs in the various adapters that might be plugged into an expansion slot. Also, depending on the exact ROM BIOS programs involved, some of the error messages and sequences can vary. Generally, however, a computer follows this chain of events while "coming to life." You can modify the system startup procedures by altering the CONFIG.SYS and AUTOEXEC.BAT files. These files control the configuration of DOS and allow special startup programs to be executed every time the system starts. The Windows 9x/Me Boot Process Many older laptops use Windows 9x/Me. Knowing exactly how Windows 9x and Millennium Edition (Me) load and start can be helpful when troubleshooting startup problems. The Windows 9x boot process can be broken into three phases: -
The IO.SYS file is loaded and run. (Windows 9x's IO.SYS combines the functions of DOS's IO.SYS and MSDOS.SYS .) -
Real-mode configuration takes place. -
The WIN.COM file is loaded and run. Phase 1: Loading and Running the IO.SYS File -
The initialization code initializes the base device drivers, determines equipment status, resets the disk system, resets and initializes attached devices, and sets the system default parameters. -
The file system is activated, and control is returned to the IO.SYS initialization code. -
The Starting Windows message is displayed for n seconds, or until you press a Windows function key. The amount of time the message is displayed is determined by the BootDelay=< n > line in the MSDOS.SYS file; the default is 2 seconds. -
The IO.SYS initialization code reads the MSDOS.SYS configuration file. If you have multiple hardware profiles (a likely situation if you have a laptop and you use a docking station or port replicator), you receive the message Windows cannot determine what configuration your computer is in. and must choose a hardware configuration to use from the menu displayed. To learn more about docking stations and port replicators, refer to Chapter 14, "Portable System Accessories." -
The LOGO.SYS file is loaded and displays a startup image onscreen. -
If the DRVSPACE.INI or DBLSPACE.INI file exists, it is loaded into memory. IO.SYS also automatically loads HIMEM.SYS , IFSHLP.SYS , and SETVER.EXE . -
The IO.SYS file checks the system Registry files ( SYSTEM.DAT and USER.DAT ) for valid data. -
IO.SYS opens the SYSTEM.DAT file. If the SYSTEM.DAT file is not found, the SYSTEM.DA0 file is used for startup. If Windows 9x/Me starts successfully, the SYSTEM.DA0 file is copied to the SYSTEM.DAT file. -
The DBLBUFF.SYS file is loaded if DoubleBuffer=1 is in the MSDOS.SYS file or if double buffering is enabled under the following Registry key: HKLM\System\CurrentControlSet\Control\WinBoot\DoubleBuffer Note Windows 9x Setup automatically enables double buffering if it detects that it is required.
-
If you have multiple hardware profiles, the hardware profile you chose is loaded from the Registry. -
In Windows 9x/Me, the system looks in the Registry's Hkey_Local_Machine\System\CurrentControlSet key to load the device drivers and other parameters specified there before executing the CONFIG.SYS file. Note If you see error messages during startup or if your system doesn't start properly, restart the system, press the Ctrl (Windows 95) or F8 (Windows 98/Me) key to bring up the startup menu, and select Logged to create a file called Bootlog.txt . This file records events during startup and can help you determine which files or processes are not loading correctly.
Phase 2: Real-Mode Configuration Some older hardware devices and programs require that drivers or files be loaded in real mode (16-bit mode) for them to work properly. To ensure backward compatibility, Windows 9x processes the CONFIG.SYS and AUTOEXEC.BAT files if they exist: -
The CONFIG.SYS file is read if it exists, and the statements within it are processed, including the loading of drivers into memory. If the CONFIG.SYS file does not exist, the IO.SYS file loads the following required drivers: -
IFSHLP.SYS -
HIMEM.SYS -
SETVER.EXE IO.SYS obtains the location of these files from the WinBootDir= line of the MSDOS.SYS file and must be on the hard disk. -
Windows reserves all global upper memory blocks (UMBs) for Windows 9x operating system use or for expanded memory support (EMS). -
The AUTOEXEC.BAT file is processed, if present, and any terminate-and-stay resident (TSR) programs listed within are loaded into memory. Phase 3: Loading and Running the WIN.COM File -
WIN.COM is loaded and run. -
The WIN.COM file accesses the VMM32.VXD file. If enough RAM is available, the VMM32.VXD file loads into memory; otherwise , it is accessed from the hard disk (resulting in a slower startup time). -
The real-mode virtual device driver loader checks for duplicate virtual device drivers (VxDs) in the WINDOWS\SYSTEM\VMM32 folder and the VMM32.VXD file. If a VxD exists in both the WINDOWS\SYSTEM\VMM32 folder and the VMM32.VXD file, the duplicate VxD is "marked" in the VMM32.VXD file so that it is not loaded. -
VxDs not already loaded by the VMM32.VXD file are loaded from the [386 Enh] section of the WINDOWS\SYSTEM.INI file. Required VxDs Some VxDs are required for Windows to run properly. These required VxDs are loaded automatically and do not require a Registry entry. Windows 9x requires the following VxDs: | *BIOSXLAT | *CONFIGMG | *DYNAPAGE | | *DOSMGR | *EBIOS | *IFSMGR | | *INT13 | *IOS | *PAGESWAP | | *SHELL | *V86MMGR | *VCD | | *VCACHE | *VCOMM | *VCOND | | *VDD | *VDMAD | *VFAT | | *VKD | *VMCPD | *VPICD | | *VTD | *VTDAPI | *VWIN32 | | *VXDLDR | | | |
-
The real-mode virtual device driver loader checks that all required VxDs loaded successfully. If they aren't, it attempts to load the drivers again. -
After the real-mode virtual device driver loading is logged, driver initialization occurs. If any VxDs require real-mode initialization, they begin their processes in real mode. -
VMM32 switches the computer's processor from real mode to protected mode. -
A three-phase VxD-initialization process occurs in which the drivers are loaded according to their InitDevice instead of the order in which they are loaded into memory. -
After all the VxDs are loaded, the files KRNL32.DLL , GDI.EXE , USER.EXE , and EXPLORER.EXE (the default Windows 9x GUI shell) are loaded. -
If a network is specified, the network environment and multiuser profiles are loaded. The user is prompted to log on to the network installed. Windows 9x/Me enables multiple users to save their custom desktop settings. When a user logs on to Windows, her desktop settings are loaded from the Registry. If the user does not log on, the desktop configuration uses a default desktop. -
Programs in the StartUp group and the RunOnce Registry key are run during the last phase of the startup process. After each program in the RunOnce Registry key is started, the program is removed from the key. Note If your laptop is running programs and services at startup that slow down the computer or make it unstable, you can use the MSConfig program in Windows 98/Me or Windows XP to selectively disable some startup programs and processes. For details, view the Windows Help System entry for MSConfig.
Windows NT/2000/XP Startup When you start a Windows NT, 2000, or XP system (which are all based on the same set of integral code), the boot process is different from that of a DOS or Windows 9x/Me system. Instead of the IO.SYS and MSDOS.SYS files used by Windows 9x/Me, Windows NT/2000/XP use an OS loader program called Ntldr. The basic Windows NT/2000/XP startup process is described in the following step-by-step procedure: -
The partition boot sector loads Ntldr (NT Loader). It then switches the processor to protected mode, starts the file system, and reads the contents of Boot.ini . The information in Boot.ini determines the startup options and initial boot menu selections (dual-booting, for example). If dual-booting is enabled, and a non-NT/2000/XP OS is chosen , Bootsec.dos is loaded. If SCSI drives are present, Ntbootdd.sys is loaded, which contains the SCSI boot drivers. -
Ntdetect.com gathers hardware-configuration data and passes this information to Ntldr. If more than one hardware profile exists, Windows uses the correct one for the current configuration. If the ROM BIOS is compliant with the Advanced Configuration and Power Interface (ACPI), Windows uses ACPI to enumerate and initialize devices. -
The kernel loads. Ntldr passes information collected by Ntdetect.com to Ntoskrnl.exe . Ntoskrnl then loads the kernel, the Hardware Abstraction Layer ( Hal.dll ), and Registry information. An indicator near the bottom of the screen details progress. -
Drivers load and the user logs on. Networking- related components (for example, TCP/IP) load simultaneously with other services, and the Begin Logon prompt appears onscreen. After a user logs on successfully, Windows updates the Last Known Good Configuration information to reflect the current configuration state. -
Plug and Play detects and configures new devices. If new devices are detected , they are assigned resources. Windows extracts the necessary driver files from Driver.cab . If the driver files are not found, the user is prompted to provide them. Device detection occurs simultaneously with the operating system logon process. The following files are processed during Windows NT/2000/XP startup: -
Ntldr -
Boot.ini -
Bootsect.dos (multiple-boot systems only) -
Ntbootdd.sys (loaded only for SCSI drives) -
Ntdetect.com -
Ntoskrnl.exe -
Hal.dll -
Files in systemroot \System32\Config (Registry) -
Files in systemroot \System32\Drivers (drivers) Note If you see error messages during startup or if your system doesn't start properly, restart the system, press the F8 key (Windows 2000/XP only) to bring up the startup menu, and select Enable Boot Logging to create a file called Ntbtlog.txt . This file records events during startup and can help you determine which files or processes are not loading correctly.
 |
