I have a big script that is completely dependent on PUSHD. However, when I type pushd \\server1\dir1 , I get:
C:\Documents and Settings\userNameHere>pushd \\server1\dir1 ' ' CMD does not support UNC paths as current directories.
OK, I know that CMD does not support UNC paths. That is why I use PUSHD. When I search for this, I find many posts that say: "When you come across this UNC path message, you should use PUSHD!" Well shit, I come across this message and use PUSHD.
I tried using CMD /E:ON because PUSHD is only active when command extensions are enabled. The same result.
I looked to see if I had any letters from the drive (since PUSHD starts with Z: and goes back to find the drive letter). Nope.
I tried running my cmd in c: \ dir ( cd c:\ , then pushd \\server1\dir1 ).
I confirmed that there is a disk, and I have access to it through Windows Explorer.
And now I have no ideas.
Link Pushd: Link
dos batch-file
jcollum
source share