China DOS Union

There should be quite a few people using Win2000 now, right? I suppose everyone has had this kind of experience: under Win2000, sometimes when you want to delete some documents or folders, a dialog box pops up saying “Unable to delete folder ***. Sharing violation. The source file or destination file is in use.” This is the annoyance caused by Win2000’s file protection mechanism. Although it can protect some important documents, more often it just brings inconvenience. After repeated trial and error, I’ve summed up some experience and am posting it here for everyone to discuss.
　1. Cause: For folders, it’s because some file inside the folder has been copied into another folder, so the system protects this folder.
　2. Solutions:　　⑴ Log off, then log back in, and you can delete it.　　⑵ Set the parent folder of this folder to shared, then delete it through Network Neighborhood.　　⑶ Use FTP sharing and delete it by logging in through FTP.
　If none of the above methods work, you can also delete it through hacker software such as Glacier. But you must use it with caution; if someone takes the opportunity to attack you, the loss would outweigh the gain. Through the above methods, this problem can generally be solved. Microsoft’s stuff is sometimes really strange: something that is forbidden to be deleted locally can actually be deleted over the network.
--

It seemed to be a problem with creating directories on IIS FTP.
For some reason, a directory appeared with an empty name.
Inside it were two directories, _core... and com1 (the names shown by Win2000),
and under them there were still other directories, all names like _core.. and com1.
When deleting them, it would show errors like “Unable to read disk,”
and they couldn't be deleted.

The solution is as follows:
1, download and install Total Commander
2, run Total Commander, in Option under Operation,
uncheck the Use long names checkbox
3, go to that undeletable directory, and you'll find the directory name has become a string of numbers plus ~~1
4, rename it, for example to 1234, then delete it
5, after some warning messages, finally one directory, com1, was deleted,
but the other one, _core.., still couldn't be deleted
6, then I had no choice but to go into directory 1234 and rename this _core..~1 to something like core11
7, then enter its directory, and rename it again to something simple, one layer at a time; it's best not to use duplicate names
8, when you get to the last directory level, after renaming it to a simple directory name, you can delete it
9, then delete outward one level at a time

That completely deleted it.
This is a problem I personally ran into; I referred to articles in the digest area and posts on the board,
hope this helps with this kind of problem )

Hehe, I know how to delete this kind of directory.