Re: Filename limits

2004-10-28 Thread Chuck McDevitt
Shankar Unni wrote: > > The Unicode versions of several functions permit a maximum path length > of 32,767 characters, composed of components up to 255 characters in > length. To specify such a path, use the "\\?\" prefix. For example, > "\\?\D:\". To specify such a UNC path, use the "\\?\UNC\"

Re: Filename limits

2004-10-28 Thread Colin JN Breame
Shankar Unni wrote: The Unicode versions of several functions permit a maximum path length of 32,767 characters, composed of components up to 255 characters in length. To specify such a path, use the "\\?\" prefix. For example, "\\?\D:\". To specify such a UNC path, use the "\\?\UNC\" prefix. F

Re: Filename limits

2004-10-28 Thread Shankar Unni
Colin JN Breame wrote: As I understand, relative paths in windows suffer from a 255 character limit (or something like that). It's not based on relative vs absolute: it's which API you use. I've quoted a bit from the MSDN documentation (Platform SDK: Storage: Naming a file). Not being intimate

Filename limits

2004-10-27 Thread Colin JN Breame
As I understand, relative paths in windows suffer from a 255 character limit (or something like that). However, I have heard rumour that absolute paths in windows are limited to 32k characters. Would it not solve the problem of the "File name too long" errors if paths were first converted to