It hardly needs to be hoped that will ever be created operating system, totally devoid of weaknesses, and working absolutely stable. Even assuming the idea that all developers and OS software will bollocks to make a perfect product and remove it all errors and vulnerabilities still remain an infinite number of custom configurations of computers to predict where the work is simply impossible. There will always be unfortunate combination of hardware and software that will result in the most complete intellectual confusion and thoughtful subtlety to the operating system. Moreover, the situation in the rapidly evolving and poorly controlled market, yet is that the failures are found not only in systems with unimaginable configurations and questionable programs, but even at the very modern and standard PCs with just the operating system. And Windows XP in this regard is no exception. User should be able to expect a very unpleasant surprises, as at the stage of installation of the system, and during the follow-up work with it. And, not every problem related to the actions of illiterate novice user or bad compatibility collected in artisanal conditions equipment. Even in a stable (in comparison with other versions of Windows) and advanced system, as Windows XP, has long been seen quite a number of failures, recurring from computer to computer, from configuration to the configuration. Part of this characteristic problems relatively easily avoided by the most appropriate configuration of operating system or install patches, updates, to get rid of other programs have to use independent developers or manually edit important files.

Crashes during installation
Perhaps the most unpleasant - even if the operating system is installed on the computer refuses to follow its decision is "all kinds of blue screens of death" BSOD (Blue Screen Of Death), and bug reports. Crashes at the stage of installing Windows XP can be caused by a wide variety of factors, ranging from poor memory and finishing phases of the moon. The standard, generic recommendations in such cases are: disconnect all peripherals except the video card, such as scanners, streamers, removable drives, and others in the CMOS Setup Unplug all integrated devices. Stop disperse (dispersal system - the main enemy of Windows installer), the CMOS Setup to install safer options - "BIOS Default". Upgrade BIOS.

However, this does not always work, there are a number of failures that require individual attention. For example, during the installation of Windows, its text-stage, the message may appear that the required file is lost, damaged or can not be copied from media. If you skip a copy of this file, the message reappears with each new backup to disk file. And the thing is usually not damaged in the Windows CD, as many users think. The problem arises if the drive letter for your type Iomega Jaz, or any other removable disk is preceded by the letter of the section you are installing Windows. The decision in this case simple - to temporarily remove the removable disk. However, similar setback, strangely enough, and may cause irregular memory, in which case you should taste in your CMOS Setup to install more memory-friendly modes (frequency, timings, etc.), or to temporarily replace memory modules in the notoriously reliable - low-quality memory occur very often.

Often, the installer OS "prevented" DMA mode is included for disk controllers: the system simply lose the hard disk during installation, there are continuing reports of fatal error. In order to exclude the probability of such a failure, check the settings in the CMOS Setup: install "BIOS Default", and the item "DMA default" (ie disable UDMA mode, either install a regime PIO), disable anti-virus protection, disable power management. Connect the hard drive on the first channel is the first IDE controller and check for correct installation jumper MASTER / SLAVE for all disks. Do not install any other drives on the same plume, which is the hard drive on which the system is installed. Try replacing plume, or replace 80 - provodnikovy plume at the 40 provodnikovy - sometimes it helps. Pererazbeyte drive again FDISK utility and format it - is that after following incorrect disk partitioning utility Partition Magic system refuses to work with him. If your system has a SCSI controller, double-check that terminators installed on the tyre, whether tires set speed controller and driver update. Generally, when using SCSI, RAID controllers, or just need additional disk controller in advance to prepare the floppy with drivers from the manufacturer - without it, the system will not be able to gain access to the disk.

The most common problems when loading Windows XP - the loss of the boot loader. This usually happens when I try to reinstall Windows 9x on a computer with two operating systems - Windows XP and Windows 9x. The system Windows 9x does not know how to determine the existence of the primary boot record (MBR) loader Windows XP and fully overwrote, setting its own. To restore the Windows XP boot loader do the following:

1. Click "CMOS Setup" (commonly called "DEL" button when booting PC) under "BIOS FEATURES SETUP" (depending on the BIOS name may be different) booting from the CD-ROM and download PC with the Windows XP CD. If the CD does not boot Windows, you should use the boot floppy, for the manufacture of which must be downloaded from Microsoft special program.
2. After booting the PC floppies or CD-ROM, the resulting menu, select "REPAIR" by clicking the "R".
3. Go to the new menu item "RECOVERY CONSOLE" by pressing "X".
4. You will question what must install "repair" - and the list of installed copies of Windows. In one instance, of course, we should press "1".
5. Enter the root password.
6. In the command line, type a "HELP" to see a list of all available commands, or enter the command "FIXBOOT" - boot sector, along with menu choice OS will be restored. Enter the command to "FIXMBR" for the restoration of the primary boot, which can be modified, for example, after installing Linux (Linux loader that will be removed).
7. Enter the command "EXIT" - the PC will reboot, click "DEL", and the CMOS Setup menu, select "Boot Sequence: C only" to the PC boots from the hard drive.

That is the section [Setup], but you can add the parameter "CleanBoot = 0". Create a backup of all files in the root directory of the boot disk. Then, either place the file in the folder with MSBATCH.INF distro Windows 9x, or run the installation of Windows 9x such a command: "SETUP.EXE DISK: PUT MSBATCH.INF. Boot sector Windows XP will not be erased. If necessary, restore the saved boot files Windows XP and Windows 9x, in particular, at the root of your boot disk BOOTSECT.DOS must file (a copy of the boot sector Windows 9x), and should have BOOT.INI file content types:

Often when booting OS users are faced with the error message: "swap file is missing or too small… Increase or create a new one" ( "Your system has no paging file, or the paging file is too small…"). To avoid this failure, first, to try to increase the swap file system using the "dialogue" ( "System") Control Panel. Next, install the hard disk controller driver from the vendor software (for example - Intel INF Update and Intel Application Accelerator). If the problem does not disappear, then download PC from the floppy Windows 98/Me and type "FDISK / MBR", and then remove the file PAGEFILE.SYS. If that does not help, then restore the Master Boot Record disk MBR and the Windows loader means most Windows XP: Recovery Console to run "FIXBOOT and FIXMBR. Try to give full rights to groups of users and System Administrators to access the file PAGEFILE.SYS virtual memory or disk partition, where the file is located.

These reports indicate damage or removing bushes either roster System Software - in accordance with an error. "Restoring Service System" (System Restore), in such a situation usually is powerless, so to solve the problem, try the following techniques:

* Restore the last a valid copy of a damaged registry file from the reserve if you are using third-party software for his backup (regularly make backups of the registry in Windows XP Required!).

* Executing the re-installation of Windows XP select "repair" system "Repair", while also lost part of the settings, and some programs will have to reinstall.

There is, however, and the way to restore the roster of those copies, which creates Service System Restore recovery system (unless it is off), even if Windows does not load in the mode of protection against failures (Safe Mode). System Restore creates a copy of the roster in a hidden folder System Volume Information system drive. This folder contains one or more sub-type "_restore (GUID) x RP Snapshot" - a directory of available outlets recovery (Restore Points, RP) system - it is in them and are relevant copies of the roster - files with the names:

If this does not solve the problem, then run the Device Manager (Device Manager), the menu "View" ( "View"), install hidden display devices ( "Show Hidden Devices") and the supplementary list, a device "Non-Plug and Play Drivers "check to see that you feature" NT Apm / Legacy Interface Node "(support ATX power supplies). If it's not there, set by using dialogue installing new equipment ( "Add New Hardware Wizard", the manufacturer - Microsoft in the list of devices). Try to disable APM and NT Apm / Legacy Interface Node, reboot the PC and insert them again. If the list of "Non-Plug and Play Drivers" you find the device "TPkd", try to remove it. Disconnect the auto for the CD-ROM drive.