A Free Trial That Lets You Build Big!
Start building with 50+ products and up to 12 months usage for Elastic Compute Service
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. Therefore, unless you have understood the following content and clarified the meaning of each step and the possible consequences, do not try it easily.
As I have not been involved in this field for a long time and lack of experience, it is inevitable that there will be omissions and errors in the Process of narration. please correct me in time. To facilitate understanding of the following content, you must first understand some concepts and facts.
Meaning 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 under DllCache
(X: WindowsSystem32Dllcache) ("X" is the partition where your XP system is located) They are generally based on dll files
Format, followed by cpl (Control Panel) and other formats of files. Elements (icons, bitmap, dialog box, text
Files, such as the forward and backward buttons on the Explorer and IE Toolbar, are saved as bitmaps.
Exist in the shell32.dll file. In other words, you only need to replace the shell32.dll file containing the new bitmap element with the original file.
You can see the new button pattern. By replacing system files, we can create a personalized Windows system :)
Something is blocking us from replacing system files
If you think that replacing system files can only be done by simply overwriting the original file, you will be naive. Microsoft does not want to see his "beautiful" window
The s interface is changed to another form, so WFP (Windows File
This 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?
What about it? As mentioned above, the Dllcache file backup directory (or file cache directory) is used in advance for all system files that are considered important by Windows.
Copy to this directory. 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
You are 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 stuck.
And it seems that there is no way to completely invalidate WFP.
SP1 (Service Pack
1) The file protection mechanism of the XP system remains unchanged. The difference is that there is another backup directory for the system files. When installing SP1
The updated file in the em32 directory is backed up and stored in a new directory: X: WindowsServicePackFile si386
The original Dllcache directory retains unupdated files. In this way, the backup folder is changed to Dllcache and i386.
As mentioned above, the purpose is to let everyone understand the reasons for the difficulty of replacing system files, to understand the mechanism of system file protection, and to understand the replacement system text described below
Methods and steps are very good. Now, let's start to replace it!
However, before replacement, we need to make some preliminary work to make all the hidden and protected files visible (Dllcache directory and other files ).
It is hidden by default. The method is simple. Open any resource manager window (such as "My Computer") and select "tool"> "file" in the menu bar.
Folder Options-> View tab, 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.
Replacing 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, the third method I will talk about how to Replacer the software to replace system files. Are you ready for the preliminary work? OK, lets go!
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 only
It takes effect only after entering the XP system, so we can avoid it and replace it in a pure DOS environment where WFP cannot work. Note
If it is pure DOS, rather than 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 can contain this disk.
Function), and you need to set the CD-ROM In the BIOS settings to the first boot item (if you are using a Floppy disk, set Floppy as the first boot item), the specific setting method I
I won't say much about it. If you don't know, you can refer to here for instructions on BIOS settings and click to view details.
After entering the DOS mode, we can replace the system files. Note that this method requires you to use some basic doscommands. Replace shell32.
The dll file is used as an example. Assume that the Windows 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 ).
Step 2: rename the shell32.dll file to shell32.bak (rename or ren can be used to rename the command ).
C:> WINDOWSsystem32dllcache> ren
Step 3: copy the new shell32.dll file to the Dllcache directory.
C: WINDOWSsystem32dllcache> copy
Step 4: Repeat the preceding steps to copy the new shell32.dll file to the system32 directory.
C: WINDOWSsystem32dllcache> cd ..
C: WINDOWSsystem32> ren
C: WINDOWSsystem32> copy
Now, the replacement is complete. Press Ctrl + Alt + Del to restart the computer to see the effect after the replacement. We set the Dllcache and System
The shell32.dll file under the 32 directory is replaced and all files are backed up (shell32.bak), so that we can restore the system to the original 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
In the i386 directory (either of them is required ). Of course, you can also manually delete all the files in the Dllcache and i386 directories, but I do not recommend this.
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 use the boot disk without entering DOS?
How can we replace system files? Of course, the answer is yes. Let's imagine that Windows is a specific text from Dllcache and i386.
Obtain files in the folder to protect the replaced system files. What if we move or rename the files so that they cannot be found? The result is: Wind
Ows requires us to insert a Windows XP (SP1) installation disc 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). However
And 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, Windows prompts a warning that the system file is replaced and asks you
Insert the xp installation CD (the replacement is successful when you see this dialog box), select "cancel", and ask if you want to retain these files. Select "yes (
Figure 2 ). Restart and check your results :)
Method 3 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
Do not leave the xp installation CD in the optical drive, and ignore any warning information displayed in Windows. However, this method has some disadvantages:
The system files that are being used cannot be overwritten (such as shell32.dlland assumer.exe). You can only use other methods to replace these files.
This method uses a foreign tool called Replacer to replace system files. The file size is only a dozen K, but after I used it several times, I found this
Xiao Dongdong 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 in xp, regardless of whether it is
Protect files that are still in use, and 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)
Step 2: drag the system file you want to replace into the window you just opened (only one can be dragged) as prompted (Figure 4)
, Press ENTER
Step 3: drag the file you used as the replacement to the window (figure 5)
Step 4: Press enter to display the information shown in Figure 6. Ask if you want to replace it. Enter Y (yes) and press Enter.
Step 5: The following process will be automatically completed: Back up the system file (the file suffix is. backup, for example, the backup of the shell32.dll file is shell32
. Backup, put in the same directory as the original file), delete the original system file, copy the new system file to the directory where the original system file is located, and backup containing the file
. In this process, files in the Temporary Folder are used. After the replacement is successful, it will prompt you to restart. The Windows System Protection dialog box is also displayed.
Then kill it and follow the above method to cope with it (Figure 7)
After the restart, you can immediately see the effect after the replacement (Figure 8). How is it easy? :)
If you think it is not good to change one by one, you can replace multiple files by writing a script file. This script is actually a text
File, and it is easy to write and does not need any knowledge. For more information, see Figure 9.
Open notepad. The first line is required. Just write it. The lines that are left blank are just for the sake of clear paragraphs. Then there is the main content. The format of each row is
It is a "replaced file + comma + file used for replacement". It is written based on the file you want to replace. You can add comments after a semicolon. Save the file after writing it. The name can be any one.
E.txt ). Put the replacement file to the Replacer directory, and drag the script file to Replacer. cmd for execution (Figure 10 ),
Start building with 50+ products and up to 12 months usage for Elastic Compute Service