How to replace Windows XP operating system files (careful operation)

First of all, it must be stated that the purpose of writing this tutorial is not to encourage everyone to replace system files, because system files directly affect the normal operation of the system and are not properly handled, otherwise, the system becomes unstable. Otherwise, the system crashes. So,Unless you have understood the following content and clarified the meaning of each step and the possible consequences, do not try it easily..

To facilitate understanding of the following content, you must first understand some concepts and facts.

　　What is the significance of replacing system files?

The so-called system file generally refers to the file that is closely related to Windows and is inseparable from the normal operation of the system. Most of these files are stored in the System32 directory (X: WindowsSystem32) and the system file backup directory DllCache (X: WindowsSystem32Dllcache) ("X" is the partition of your XP system) they generally exist in the form of dll files, followed by cpl (Control Panel) and other formats of files. Elements (icons, bitmaps, dialogs, and texts) of Windows are stored in these files, such as Explorer) the forward and backward button pattern on the toolbar of IE exists in the form of Bitmap with the shell32.dll file. In other words, just replace the shell32.dll file containing the new bitmap element with the original file, and we can see the new button pattern. By replacing system files, we can create a personalized Windows system :)

　　What is blocking us from replacing system files?

If you think that replacing the system file can only be done by simply overwriting the original file, you would be naive, microsoft does not want to see his "beautiful" window s interface become a different one, so WFP (Windows File Protection) was added from Win2000, that is, system File Protection. The old name is used to protect system files from being modified or replaced by users. How does it implement file protection? As mentioned above, the Dllcache file backup directory (or file cache directory) is backed up to this directory in advance for Windows, once WFP detects that these important files in the System32 directory have been changed or replaced, it will automatically restore the replaced files from the backup, making you futile. This function of Windows plays a very good role in self-protection against virus and other tampering of system files, but it makes many theme players feel helpless, at present, there seems to be no way to completely invalidate WFP.

　　About SP1

The file protection mechanism of the Windows XP system installed with SP1 (Service Pack 1) remains unchanged. The difference is that there is another backup directory for the system files. During SP1 installation, Windows backs up the updated files in the Syst em32 directory and stores them in a new directory: X: WindowsServicePackFile si386, in the original Dllcache directory, unupdated files are retained. In this way, the backup folder is changed to Dllcache and i386.

As mentioned above, the purpose is to let everyone understand why it is difficult to replace system files and understand the mechanism of System File Protection, it is helpful to understand the methods and steps for replacing the system file described below. Now, let's start to replace it!

However, we need to do some preliminary work before replacement, this is to make all the hidden and protected files visible (the Dllcache directory and some other files are hidden by default). The method is simple, open any resource manager window (such as "My Computer"), select "Tools"> "Folder Options"> "View" tab in the menu bar, remove the check box before "Hide protected operating system files", select "show all files and folders", and click OK (figure 1 ). Okay. Now all the files in the system are invisible.

Figure 1

Replace system files. There are many ways to replace system files. Here I will introduce three common methods based on my own experience. The first two methods do not use any third-party software, in the third way, I will talk about how to replace system files with the Replacer software. Are you ready for the preliminary work? OK, lets go!

　　Method 1:

This is the most traditional and secure method, but it is also the most complicated and technically demanding method. Because replacing system files in xp will be blocked by file protection, but WFP takes effect only after it enters the xp system. Therefore, we can avoid this problem, in an environment where WFP cannot work, replace it with pure DOS. Be sure to use pure DOS instead of the "command prompt" program in xp. A boot disk is required to enter the pure DOS disk (both ephemeral disks and general 98/xp Mount disks provide this function ), and need to set the CD-ROM to the first boot item in the BIOS settings (if the disk is used, set Floppy as the first boot item), the specific setting method I will not say much, no, you can refer to the BIOS settings here.
After entering the DOS mode, we can replace the system files. Note that this method requires you to use some basic doscommands. The following uses the shell32. dll file as an example. Assume that the XP system is installed on the C drive, and the shell32.dll file you used to replace is placed in the D: New directory.

Step 1: Enter the DLLcache directory (the blue text is the input part ).

C:>Cd windowssystem32dllcache

Step 2: rename the shell32.dll file to shell32.bak (rename or ren can be used to rename the command ).

C:> WINDOWSsystem32dllcache>Ren Shell32.dll Shell32.bak

Step 3: copy the new shell32.dll file to the Dllcache directory.

C: WINDOWSsystem32dllcache>Copy D: Newshell32.dll

Step 4: Repeat the preceding steps to copy the new shell32.dll file to the system32 directory.

C: WINDOWSsystem32dllcache>Cd ..

C: WINDOWSsystem32>Ren Shell32.dll Shell32.bak

C: WINDOWSsystem32>Copy D: Newshell32.dll

Now, the replacement is complete. Press Ctrl + Alt + Del to restart the computer to see the effect after the replacement. We replace the shell32.dll files in the Dllcache and System 32 directories and back up the files (shell32.bak) at the same time, so that we can restore the System to the original State at any time. However, this method is not good for xp with SP1 installed, because before replacement, we must first determine whether the replaced file is in the Dllcache directory or the i386 directory (both must be in one ). Of course, you can also manually delete all the files in the Dllcache and i386 directories, but I do not recommend this.

Method 2:

The above method requires a boot disk, and it is a little complicated and cumbersome for people who are not familiar with the doscommand, is there a way to replace system files without entering DOS? Of course, the answer is yes. Assume that Windows obtains files from the specified folders Dllcache and i386 to protect the replaced system files, so what if we move or rename it to make it unable to find these files? The result is that Wind ows requires us to insert an installation disc for Windows XP (SP1) to restore the replaced file. Of course, as long as we do not do what it says :)

Step 1: Rename the Dllcache folder to any name (such as Backup) (if SP1 is installed, remember to rename the i386 folder ), then move them to any place (such as the C root directory ).

Step 2: Put the file you used as the replacement directly under the System32 directory to overwrite the original file. In this case, a warning is displayed for replacing the system file in Windows, asking you to insert the xp installation disc (this dialog box indicates that the replacement is successful), and selecting "cancel ", it also asked you if you want to keep these files and select "yes", as shown in figure 2 ). Restart and check your results :)

Figure 2

This method is especially applicable to users who often need to replace system files or replace a large number of system files at a time. The replacement process is fast and convenient without complicated and complicated steps. As long as you do not leave the xp installation CD in the optical drive, and ignore any warning information displayed on Windows, it will be OK. The replacement of these files can only be used in other ways.

　　Method 3:

This method uses a foreign tool called Replacer to replace system files. The file size is only a dozen K, but after I have used it several times, I found this little stuff is really practical, and the ability to replace system files must not be underestimated. It is easy to use and can directly replace system files under xp, regardless of whether it is a protected file or a file in use, you do not need to rename or move the Dllcache directory! Replacer download page:Click to enter, The latest test version is 2.50, and the stable version is 2.37.

The following is an example of replacing the shell32.dll file:

Step 1: extract the downloaded file and get a folder. Double-click Replacer in it. the cmd file is automatically opened in command line mode, and a temporary folder is automatically generated in the Replacer directory. replacerTemp (figure 3)

Figure 3

Step 2: Follow the prompts to drag the system file you want to replace into the window you just opened (only one can be dragged) (Figure 4) and press ENTER

Figure 4

Step 3: drag the file you used as the replacement to the window (figure 5)

Figure 5