xp
-
Fastfast.sys file missing - xp boot fault handling series 15 The Fastfast.sys file is missing or corrupt: Windows cannot start because the following files are damaged or missing: \System32\Drivers\Fastfat.sys You can use the original boot floppy disk or CD-ROM To start the windows installer and repair this file again and again. On the first screen, select&# 39 -
The vgaoem.fon file is missing - the fourteenth of the xp startup fault handling series When we boot up, the computer prompts that the vgaoem.fon file is missing: Windows cannot start because the following files are damaged or missing: \WINDOWS\SYSTEM\vgaoem.fon You can use the original boot floppy disk or CD-ROM To start the windows installer and repair this file again and again. On the first screen, select&# -
Do not display the system selection list - xp boot fault handling series 13 When we boot up the xp system, we often have a selection interface. How to change it to boot up and directly enter the xp system, such as the first xp system. As shown in the figure: ... -
System file missing - xp boot failure handling series 12 When we start up xp, the system file (not the folder...) is lost: Windows cannot start because the following files are damaged or missing: \WINDOWS\SYSTEM32\CONFIG\SYSTEM You can use the original boot floppy disk or CD-ROM To start the Windows Installer and repair this file again -
Bootmgr is missing xp Startup Fault Handling Series XI Here we assume that system disk c: system disk, disk d: active partition, non system disk. My computer system is xp system, but it displays "Bootmgr -
The kernel32.dll file is missing - xp boot failure handling series 10 The computer turns on and displays a blue screen (code): stop:c0000135 unknown hard error unknown hard error The blue screen will be displayed after the Windows XP welcome screen appears, or you can directly restart back and forth halfway through startup. As shown in the figure: Here is a case. This may be the kernel of the xp system -
Xp boot blue screen (one): STOP: 0x0000007B-xp boot fault handling series 9 When the xp system starts up, it starts to the windows xp welcome screen, and the blue screen will appear: STOP: 0x0000007B (0x....), as shown in the figure: Cause: Most of the time, your hard disk is a SATA hard disk, and your hard disk interface mode is set to AHCI mode without setting other attributes. There is no SATA control in the general XP system (original) -
Xp system login password forgotten - xp startup fault handling series 8 Many times when we re enter the system without using the computer for a long time, we find that our login password for the Xp system has been forgotten. What should we do? It is not necessary to reinstall the system. It is not a simple method. Here we only introduce a method to crack the xp password. (Be civilized.) Solution: Enter the PE system. Open the password unlocking software (NTPWEDIT 0.2) ( -
Display the full English interface when selecting the system during startup - xp Startup Fault Handling Series 7 When we start up xp and select the system, the full English interface is displayed: the phenomenon is as follows: Cause: The bootfont.bin file in the active partition is missing. This document is the function of sinicization. Solution: Copy the bootfont.bin file in the active partition from another xp system to the root directory of the active partition (of course, this file can also be absent, which does not affect the normal operation of the system -
Hal.dll Lost - xp Startup Fault Handling Series 6 Xp Startup Fault Handling Series 6: Hal.dll Lost Phenomenon: When you turn on the computer and enter the system, Windows cannot start because the following files are damaged or missing:<windows root> system32 hal.dll. Please reinstall the copies of the above files. As shown in the figure: terms of settlement: The first way -
The ntoskrnl.exe file is missing or damaged - xp boot failure handling series 5 After the xp system is powered on, it displays the loss of the ntoskrnl.exe file: windows cannot start because the following files are damaged or missing:<windows root> system32 ntoskrnl.exe. Please reinstall the copy of the above files Solution: After entering the PE system, turn the normal X -
Failing to enter the xp welcome screen and restart back and forth - xp startup failure handling series 4 Failure handling series 4 of xp startup: unable to enter the xp welcome screen and restart back and forth. Even the welcome screen of Windows XP system cannot enter after the computer is turned on. Restart back and forth, which may be NTDETECT The COM file may be missing. Solution: After entering the PE system, find the normal system or download the file NTDETECT from the website COM files ( -
Operating system not found xp The third part of the xp startup fault handling series: Operating system not found. (One of them!) After xp is powered on, the system cannot be improved. The display shows: Operating system not found Solution: After entering the PE system, open the partition -
NTLDR loss xp startup fault handling series II After the xp system is powered on, NTLDR files are lost: NTLDR is missing Press any key to restart, as shown in the figure: Environment: The computer has two drive letters: c and d. There are two solutions: The first case: after entering the PE system, check that disk c is not the active partition, disk d is the active partition, system disk, and disk d is the active partition -
The boot.ini file is illegal - one of the xp boot fault handling series It is better to understand the xp startup process before dealing with such problems. The specific process can be seen in the process of xp system startup on this site, which is introduced in detail. About the website -
Introduction to Converting XP System to WIN7 System April 8, 2014 is coming soon. Everyone knows that the arrival of this day means that Microsoft's technical support for the xp system will end. Of course, you can continue to use the xp system, but since then your system will