[p4] P4V cannot resolve a file

[Jeff Grills]

I've done this sort of thing before using subst (although not to get around
path length limitations), and it works well.  If you do subst a drive like
this, you can make perforce aware of the multiple mappings by using the
client's AltRoots field, and perforce will behave properly no matter which
path you use to get to the files.

j

-----Original Message-----
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of Victor Johnson
Sent: Thursday, February 23, 2006 9:51 AM
To: perforce-user at perforce.com
Subject: Re: [p4] P4V cannot resolve a file


All,

A handy workaround for this lamentable shortsightedness is the vestigial DOS
'subst' command (from the days of the single/dual floppy drive machines that
may or may not have a hard drive).

See http://www.computerhope.com/substhlp.htm

It is a handy way to dynamically substitute some long path with a short
"x:\" specification when things like PATH, CLASSPATH, etc. become too long.
A "subst" drive will not survive a reboot so a quick 'substitutes.bat'
script in the accounts' Startup folder will make them persistent.  Note that
you cannot 'subst' a network drive.

Cheers,
VLJ