0
nimesh's Avatar, Join Date: Apr 2009
Invasive contributor
indiansword: the issue is not creating the folder in windows folder, but giving it the system reserved names
you would get the same error in whichever directory you create it.
you would get the same error even if you create it in externel devices.
0
vignesh1988i's Avatar
Banned
just know wat it is that's all... and one more thing.... i need to ask... as nimesh told i refered how to create the folder by the command it has specified...... now Mr. Nimesh , can be please tell me what is the INTERNAL Meaning of that command line string (mkdir \\.\d:\con)... pl. say the meaning .........
0
SaswatPadhi's Avatar, Join Date: May 2009
~ Б0ЯИ Τ0 С0δЭ ~
Quote:
Originally Posted by vignesh1988i View Post
...now Mr. Nimesh , can be please tell me what is the INTERNAL Meaning of that command line string (mkdir \\.\d:\con)... pl. say the meaning .........
LOL, tell the "internal" meaning, but don't tell the meaning
Now, what does that mean ?? What exactly is "internal" here ??

Well, I will try to explain the meaning (not sure if it's "internal") :

It is because of the UNC Path (http://en.wikipedia.org/wiki/Univers...ing_Convention). The Universal Naming Convention, or UNC, specifies a common syntax to describe the location of a network resource, such as a shared file, directory, or printer.Since, these conventions didn't exist under pure DOS, they are not backward compatible. The UNC syntax for Windows systems is as follows..

\\RemoteHost\sharedfolder\resource

where RemoteHost is the computer name / IP address of the computer that you wish to connect through remotely for accessing shared folder. The rest is the path.

By providing the path in UNC syntax, you make DOS ignore the old system (because UNC was not supported earlier) of reserving the folder names like CON, LPTx etc ..
nimesh like this