Greg Ercolano wrote:
Dylan Penhale wrote:
Microsoft explains this error best:
http://support.microsoft.com/?kbid=156276
[..]
According to the above Microsoft page, there's a registry tweak
to "fix" this.
BTW, I just tried the above registry tweak, and it does
prevent the warning, and does allow DOS to open up in a UNC directory.
Here's a simple way to test for the problem with a one liner perl script.
On my Win2K machine, //meade/net/tmp/scenes is a valid UNC path to a directory
full of Maya scene files:
perl -e "chdir('//meade/net/tmp/scenes'); system('cmd /c dir');"
When I run that command *without* the reg tweak, that command prints
the warning, and shows a directory listing of the c:\winnt drive:
WITHOUT REG TWEAK
-----------------
C:\>perl -e "chdir('//meade/net/tmp/scenes'); system('cmd /c dir');"
CMD.EXE was started with '\\meade\net\tmp\scenes' as the current directory path. UNC paths <<
are not supported. Defaulting to Windows directory. <<
Volume in drive C has no label.
Volume Serial Number is B44F-0FBA
Directory of C:\WINNT <-- directory listing of C:\WINNT..
06/12/2006 01:16a <DIR> .
06/12/2006 01:16a <DIR> ..
[..]
If I run the same command *with* the reg tweak applied, no warning
is displayed, and it does in fact show a directory listing of the
UNC directory, as one would expect:
REG TWEAK APPLIED
-----------------
C:\>perl -e "chdir('//meade/net/tmp/scenes'); system('cmd /c dir');"
Volume in drive \\meade\net is net
Volume Serial Number is 0453-0174
Directory of \\meade\net\tmp\scenes <-- correct listing
06/09/2006 12:22p <DIR> .
06/30/2006 01:15a <DIR> ..
[..]
However, this tweak still does *not* help DOS's own 'CD' command
to work with UNC paths.. 'CD' still gives an error:
C:\>cd \\meade\net\tmp
'\\meade\net\tmp' is an invalid current directory path. UNC paths are not supported.
Obviously this reg tweak was just a stopgap for a specific user complaint.
Whatever, Microsoft.
|