[p4] Windows file name length issues

Ivey, William william_ivey at bmc.com
Fri Aug 17 09:16:40 PDT 2007

We've run into this. I just tell users, put the repository
close to the root.

If that's not feasible, you might try using SUBST to assign
a logical drive letter to the root path and use that in the

Even if there wasn't a limit, there's always something to
be said for keeping the length of file/directory names
sensible and applying the fine arts of creating readable
contractions, removing redundancy, etc. After all, someday,
someone may have to actually type that path...


-----Original Message-----
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of Albrecht, Matt

Recently, the Windows users at my office have started experiencing the
Windows file name length limit, where, due to the length of their client
root directory, the Perforce client cannot sync the file to the local
client due to the total local file name length being more than 255
characters (or right around there). They are all running on Windows XP.

The current answer I have is to either change the file names so that
they're more compatible with everyone's system (not a good answer), or
to shorten the client root (seems like a short term fix).

Does anyone know of a better, long term solution, or if Perforce on
Vista has the same problem?  Thanks.

perforce-user mailing list  -  perforce-user at perforce.com

More information about the perforce-user mailing list