title: what could cause PUSHD to fail?
body: <p>I've got a great big script that is entirely reliant on PUSHD. However suddenly when I type <code>pushd \\server1\dir1</code> I'm getting:</p>
  
  <pre><code>C:\Documents and Settings\userNameHere&gt;pushd \\server1\dir1
  ' '
  CMD does not support UNC paths as current directories.
  </code></pre>
  
  <p>OK, I'm aware that CMD doesn't support UNC paths. That's why I'm using PUSHD. When I search for this I find lots of posts that say "When you encounter this message about UNC paths, you should use PUSHD!". Well crap, I'm encountering that message <em>and</em> using PUSHD. </p>
  
  <p>I tried using <code>CMD /E:ON</code> because PUSHD is only active when Command Extensions are enabled, apparently. Same result. </p>
  
  <p>I looked to see if somehow I was out of drive letters (since PUSHD starts at Z: and goes backward to find a drive letter). Nope. </p>
  
  <p>I tried starting my cmd at the c:\ dir (<code>cd c:\</code> then <code>pushd \\server1\dir1</code>). </p>
  
  <p>I confirmed that the drive is there and I have access to it, via Windows Explorer. </p>
  
  <p>And now I'm out of ideas.</p>
  
  <p>Pushd reference: <a href="http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/pushd.mspx?mfr=true" rel="noreferrer">Link</a></p>