Related Information in C#.NET

Encoder QR Code 2d barcode in C#.NET Related Information

For more information about troubleshooting concepts, see 27, Understanding Troubleshooting. For more information about enabling, disabling, and managing devices, see 9, Managing Devices. For more information about troubleshooting disk or file system problems, see 28, Troubleshooting Disks and File Systems and 12, Organizing Disks. For more information about Microsoft Windows XP Professional troubleshooting tools, see Appendix C, Tools for Troubleshooting.

To diagnose and correct a startup problem, you need to understand what occurs during startup. The first step in isolating startup problems is for you to determine whether the problem occurs before, during, or after Microsoft Windows XP Professional starts up. The root cause of startup failure, including contributing factors, can stem from a variety of problems, such as user error, application faults, hardware failures, or virus activity. If the condition is serious enough, you might need to reinstall Windows XP Professional or restore files from backup media.

Part V:

In x86-based systems, startup failures that occur before the operating system loader (Ntldr) starts could indicate missing or deleted files, or it could indicate damage to the hard disk master boot record (MBR), partition table, or boot sector. If a problem occurs during startup, the system might have incompatible software or drivers, incompatible or improperly configured hardware, or corrupted system files. The startup process for x64-based computers is the same as that of x86-based computers.

The Windows XP Professional startup process closely resembles that of Microsoft Windows NT version 4.0, Microsoft Windows 2000, and Microsoft Windows Server 2003, but it significantly differs from Microsoft MS-DOS , Microsoft Windows 95, Microsoft Windows 98, and Microsoft Windows Millennium Edition (Windows Me). All computers running Windows XP Professional share the same startup sequence:

Power-on self test (POST) phase Initial startup phase Boot loader phase Detect and configure hardware phase Kernel loading phase Logon phase

The preceding startup sequence applies to systems started or restarted after a normal shutdown, and it does not apply when you bring your computer out of hibernation or standby. See Resolving Power Management Problems later in this chapter for more information about problems that might occur when you bring your computer out of standby or hibernation. For Windows XP Professional to start, the system and boot partitions must contain the files listed in Table 29-1.

Disk Location Root of the system partition Root of the system partition Description The operating system loader. A file that specifies the paths to Windows XP Professional installations. For multiple-boot systems, Boot.ini contains the operating system choices that display on the startup menu. A hidden system file that Ntldr loads for a Windows XP Professional multiple-boot configuration that includes MS-DOS, Windows 95, Windows 98, or Windows Me. Bootsect.dos contains the boot sector for these operating systems.

Bootsect.dos (multiple-boot systems only)

29:

Disk Location Root of the system partition Root of the system partition (required for SCSI or Advanced Technology Attachment [ATA]controllers with firmware disabled or that do not support extended INT-13 calls). systemroot\System32 Description The file that passes information about the hardware configuration to Ntldr. The device driver used to access devices attached to a SCSI or ATA hard disk whose adapter is not using BIOS. The contents of this file depend on the startup controller used.

The core (also called the kernel) of the Windows XP Professional operating system. Code that runs as part of the kernel does so in privileged processor mode and has direct access to system data and hardware. During installation on single processor systems, Windows XP Professional Setup copies Ntoskrnl.exe from the operating system CD. During installation on multiprocessor systems, Windows XP Professional Setup copies Ntoskrnlmp.exe and renames it Ntoskrnl.exe.