Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a bunch of programming projects on my P:\ drive (on Windows 7)

I'm now doing some programming within Virtual PC Windows XP Mode and I'd like to "call" that drive, within the Win XP guest, the P: drive. I've mapped drive letter P: to "network" drive on the Host but that goes across the network so it's very slow.

I tried using the SUBST command but it wouldn't take the \tsclients\p as a parameter. Basically, the command line interpreter (is that DOS on Win 7 ??) doesn't recognize that directory (\tsclients\p)

share|improve this question

migrated from May 13 '10 at 21:50

This question came from our site for professional and enthusiast programmers.

up vote 3 down vote accepted

I tried mapping a network drive (P) to tsclient\p but it was incredibly slow accessing the drive. A blog entry on an MS blog confirmed that Virtual PC accesses a local mapped network drive slower than it would a network resource (which in itself is much slower than a local drive).

However, the NET USE command provided very fast access:

NET USE P: \\tsclient\p
Where P is the new drive letter you want to be able to use within VPC And \\tsclient\p is the UNC path to the Host

Executed from the Command line within the Virtual PC Guest) created a local P: drive linked to the Host's P drive.

Apparently, this command provides a direct "link" to between the aliased drive letter and the path, without making a round trip through the Network like a Mapped Network drive would.

You can map a drive(say Z:) to \tsclient\P so that you can use the command prompt to cd to any folder in drive p. Ie; you can type Z: in cmd.exe and work there..

share|improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .