Subj : Re: NET USE Switches
To   : All
From : Jonathan de Boyne Pollard
Date : Wed Mar 06 2002 02:18 am

From: Jonathan de Boyne Pollard <J.deBoynePollard@tesco.net>

AD> '\\sonscentral\users\adefaria'
AD> CMD.EXE was started with the above path as the current directory.
AD> UNC paths are not supported.  Defaulting to Windows directory.
AD> [...]
AD> '\\sonscentral\users\adefaria'
AD> CMD does not support UNC paths as current directories.

PR> Try 'pushd \\sonscentral\users\adefaria' instead of 'cd ....'

PUSHD does not do the same thing as CD, there are at least two distinct side 
effects to such a PUSHD command that CD does not have.  Moreover, the intended 
result is not achieved.  The current directory does not end up as being a UNC 
name.

Win32 itself supports processes having UNC names as current directories quite 
happily.  There are no differences between the various Win32 API flavours that 
would prevent CMD from being able to attempt to set a UNC name as the current 
directory.  It is a shame, therefore, that it does not allow the CD command to 
do this, and in fact explicitly recognises and prevents attempts to use UNC 
names.

--- BBBS/NT v4.01 Flag-2
 * Origin: Mach2 Systems (1:342/3)

.