XP: how to achieve the effect of SUBST yet allow volume label?

[trs51x]

I have a lot of client project folders that I want to map to aliases to
increase "friendly name" visibility and decrease drill-down times while
working.

Currently I am using:

SUBST y: "e:\client projects\foo"

But the resultant y: takes the same volume label as the e: drive. As the
goal here is to increase visibility of key folders/files, that doesn't
really help me. I want it to have label "FOO".

I also tried Map Network Drive, trying to point to "\\localhost\e$\client
projects\foo" etc. I use this technique every day to do this with networked
folders (which allow labels!), but this doesn't appear to work at all with
local drives.

Any insight, workarounds, etc. would be much appreciated!

Thanks!

PS Sorry if this is wrong group, but given what I see being discussed in
here vs. any of the alternatives, this seemed like the best place. (And of
course the miserable taxonomy of MS newsgroups is a discussion all it's
own...)

 

[Mark Blain]

I have a lot of client project folders that I want to map to aliases
to increase "friendly name" visibility and decrease drill-down times
while working.

Currently I am using:

SUBST y: "e:\client projects\foo"

But the resultant y: takes the same volume label as the e: drive. As
the goal here is to increase visibility of key folders/files, that
doesn't really help me. I want it to have label "FOO".

I also tried Map Network Drive, trying to point to
"\\localhost\e$\client projects\foo" etc. I use this technique every
day to do this with networked folders (which allow labels!), but this
doesn't appear to work at all with local drives.

Any insight, workarounds, etc. would be much appreciated!

Thanks!

PS Sorry if this is wrong group, but given what I see being discussed
in here vs. any of the alternatives, this seemed like the best place.
(And of course the miserable taxonomy of MS newsgroups is a discussion
all it's own...)

You can use Map Network Drive if you change your path from
"\\localhost\e$\client projects\foo" to
"\\127.0.0.1\e$\client projects\foo"

If sharing the target folder seems too risky or complex to maintain,
create local shortcuts to folders with friendly names instead, or
investigate MOUNTVOL and LINKD:
http://support.microsoft.com/kb/205524