Yes, Windows will barf on paths longer than 255. I can't remember what it says, but it gives some mysterious error message and doesn't let you go any deeper.

There is a workaround: the subst command

Say you've mapped a share on the filer to the F: drive, and your G: drive letter is available. You need to get into a path longer than 255. You can do

subst G: F:\path\path\path\path\path\path\path\path....

and then when you open G: you're already pretty far down.

We had a mysterious "bottomless pit" of folders once, nobody remembered how it got there but it never ended. Couldn't delete it because of Windows barfing at the path depth. Eventually figured out this subst workaround...

Tom

On Fri, 25 Jan 2002, neil lehrer wrote:

wee are converting from nfs/unix to cifs/ntfs on filer. some of our path lengths exceed the windows limit of 260[?]. i expect the filer won't care, but maybe the client sw will.

has anybody had experience with this?

thanks