Misschien heb je hier iets aan (van een website geplukt)
Opening up a command prompt, navigate to the suspect sub-directory. From
there, run DIR, using the /X switch. This gives you 8.3 equivalent of the
long filename. So, our "com1 " will look something like this:\
09/19/2001 11:48a <DIR COM1~002 com1
This is important, because to delete the file, you'll need that COM1~002
name to do it. If you try to delete "com1", NT can't find that file and
you get an error message.
I had to use the POSIX utilities in Microsoft Windows NT Server 4.0
Resource Kit to kill those directories. I just needed the command rmdir -
a simple solution once I figured out which command to use. I later found
another way to eliminate the hacked directories. Issue the command:
RD \\?\d:\inetpub\wwwroot\_vti_txt\tagged\by\###morpheus###\com1~002
Substitute the offending name, com1, prn, etc. The \\?\ tells RD to use
POSIX support when dealing with this file and directory. One other thing,
since they like to use long strings of characters for subdirectory names,
rename as many of them as you can. It just makes it easier to get rid of
them. So, you could rename the stuff above to something eaiser to type,
like:
RD \\?\d:\inetpub\wwwroot\1\2\3\4\com1~002
To empty out the files, I used DEL d:\inetpub\wwwroot\_vti_txt\*.* /S -
the /S switch tells DEL to take out everything in every subdirectory and
that part pretty much works as advertised. I had trouble with one bizarre
file, but the RD procedure above took care of that one. I'm not sure what
they did to it to make it harder to delete, I'm just glad it's gone.