Windows2 tips

1. Windows useful file replacement commands, bypassing file protection replaces replace, even files being used can also be replaced. Very invincible. For example: in C: / Request a directory, C: / AAA then copy a MP3 to C: / AAA and named c: /aa/a.mp3 and then copy another song to c: /a.mp3 Then use Media Player to play C: /aa/a.mp3 Enter: Replace C: /a.mp3 c: / aaa After a while, is it played to another. Replace the system file with this command is really cool, and XP system file protection is also invalid. No need to replace the file in security mode 2.Windows file system vulnerability - small vulnerability, big use Everyone knows in Windows "/" symbol is the separator symbol of the path, such as "c: / windows /" means C The Windows folder in the partition is the meaning of the system.exe file in the Windows folder in the C partition, so that we will continue to be assumed: If there is a "/" symbol in the file name how is it? If "S /" is the name of a folder, this folder is located in: "f: /", his path is "f: / s /", when we try to access, Windows will be wrong, think we have to open. The file is the s folder of the C partition so that Windows cannot open and return an error because the above path does not exist. Maybe you are trying to create a "S /" file now, but Windows will prompt you: "/" The symbol is not the name of the file, the folder. It seems that Windows still thinks this. OK We continue, do not believe that files containing "/" symbols cannot be established. Now open your computer, we have to do some very interesting attempts. After entering Windows, click: Start> Run and enter "CMD" and the car (if you are win98, enter "command"), then you will see Windows command console, we just want to use it to complete our remaining test The following contains a lot of characters in {} are my comment:

Quote:

Microsoft Windows XP [Version 5.1.2600]

(C) Copyright 1985-2001 Microsoft Corp.

F: / test> Mkdir s / {Our first trial, the result of Windows only created S folder "/" is ignored}

F: / test> mkdir s / s1 / {still failed, Windows first created a S folder, then create S1 folder} in S

F: / test> mkdir s. / {"S. /" Is analyzed into s "./" is ignored.

Sub directory or file s. / Already exists.

F: / test> mkdir s ../ {Finally, now you can see "s." But can't open / delete} in the Explorer.

F: / test> mkdir s ... / {successfully, can see "s .." in the resource browser can be opened but cannot be deleted.

Why is this this? Let us first say this "S." folder you see, he can't open it, you can't delete it, can't open because his actual path is "f: / test / s ../" (we can create it yourself Determine his actual path) But the name in the Windows Explorer becomes "S." That is to say, when you try to open it, Windows actually tries to open "f: /test/s./", of course, can not open , The file does not exist, so Windows will report an error. Can't delete because of this, Windows parses an actually existing file path to a non-existing path, and the operation is of course unfinished. This file is said, this file can be opened, but it can't be deleted. Wait ... Open? Do you think that Windows really opens the "s ... /" file we created? You will understand the following test. Or the old rule {} is my annotation convenient for everyone: quote:

Microsoft Windows XP [Version 5.1.2600]

(C) Copyright 1985-2001 Microsoft Corp.

F: / test> echo 1> txt1.txt {Create "f: /test/txt1.txt" file}

F: / test> Copy txt1.txt s ../ {copy the file you just created to "s ../", it is the "S." of the resource manager.

1 file has been copied.

F: / test> echo 2> txt2.txt {Create "f: /test/txt2.txt" file}

F: / test> copy txt2.txt s ../ {copy the file you just created to "s ... /", the resource manager "s .."}

1 file has been copied.

F: / test>

Now return to your resource manager to open "s .." folder, what did you see? How will "txt1.txt" file here? We just replicated to "S."? Do we turn on "s .." folder actually open "S."? Nice fact is like this. In fact, if you create a "S" folder "S." to open, but actually open "S". "How should I delete it?", It is not difficult to delete it, but the conventional method is absolutely deleted. There are two ways to choose from: 1; enter DOS deletion (not recommended). 2; or enter the command prompt and enter the "RMDir directory name". The directory name is the name when you created. If you have forgotten you, you can view it first in the Explorer, and add "./". If prompted "Folder is not empty" should add "/ s" parameters. Delete instance:

Quote:

Microsoft Windows XP [Version 5.1.2600]

(C) Copyright 1985-2001 Microsoft Corp.

F: / test> DIR

The volume in the driver F is BGTING

The serial number of the volume is 2C8E-FE1C

F: / test catalog

Journal of China].

2003-09-11 17:50