[p4] Windows file name length issues
jgrills at drivensnow.org
Fri Aug 17 16:05:22 PDT 2007
We've had problems where the filename is valid on the client, but it won't
submit to the server because the path on the server would be too long. I
don't think this has anything to do with Office. We don't have a good
solution for this ourselves and would welcome ideas. (To defend ourselves,
the obscenely long filenames are coming from a third party, not being
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of Robert Cowham
Sent: Friday, August 17, 2007 11:42 AM
To: 'Albrecht, Matt'; perforce-user at perforce.com
Subject: Re: [p4] Windows file name length issues
I don't think it is a Windows OS limitation, but instead an Office
limitation - i.e. versions of Word/Excel can't cope.
Thus no Vista solution!!
Shortening Client root/mapping can help...
> -----Original Message-----
> From: perforce-user-bounces at perforce.com
> [mailto:perforce-user-bounces at perforce.com] On Behalf Of
> Albrecht, Matt
> Sent: 17 August 2007 16:26
> To: perforce-user at perforce.com
> Subject: [p4] Windows file name length issues
> 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.
More information about the perforce-user