The bug has been tried and tested in both Windows XP Home and Professional. If you try to make a folder named "CON" (case insensitive), Windows XP renames it back to what it was. So creating a new folder with the name "CON" just renames it to "New Folder".
The bug seems like a variable that got treated as a string or vice-versa. Trying to create the folder from a cmd prompt failed with an error "The directory name is invalid.".
This also works when you try to create a file called "CON", or "CON.". ".CON" shows up the way it should.
If you create a folder named "CON" on a linux filesystem say, and open up a samba share of it, the "CON" directory shows up as being "CSHOFG~F". A "CON." file or folder shows up as "CRW2KU~B"! Very Strange! But this is not about linux we should be talking about!!!
its only possible to name a directory as 'con' if you put something between any of the alphabets, like a space, or a punctuation, but that defeats the purpose totally right??!!??
Somebody at Microsoft willing to explain?
Picking pebbles on the shore of the networking ocean
a plausible reason that i think is right
13 years 1 week ago #10676