RE: [Gnu-arch-users] Amendment to Path Problems

[Parker, Ron]

> -----Original Message-----
> From: Michael Grubb [mailto:address@hidden

> This is no command length issue(well it may be 
> a combination 
> of the two), it is a depth problem.  Windows doesn't seem to 
> support more 
> than 23-24 directories deep.

I'm not trying to be a jerk, refuting everything you're posting, but this is
also wrong.  Just running cmd.exe I was able to create nested directories on
the root of my F: drive name 'a' to a depth of 144 before receiving the
equivalent of ENAMETOOLONG:

        
F:\a\a\a\a\a\a\a\a\a\a\a\a\a\a\a\a\a\a\a\a\a\a\a\a\a\a\a\a\a\a\a\a\a\a\a\a\a
\a\a
        
\a\a\a\a\a\a\a\a\a\a\a\a\a\a\a\a\a\a\a\a\a\a\a\a\a\a\a\a\a\a\a\a\a\a\a\a\a\a
\a\a
        
\a\a\a\a\a\a\a\a\a\a\a\a\a\a\a\a\a\a\a\a\a\a\a\a\a\a\a\a\a\a\a\a\a\a\a\a\a\a
\a\a
        \a\a\a\a\a>mkdir a && cd a
        The filename or extension is too long.

At this point the path length is ~252 characters and assume someone made the
mistake of adding sizeof(wchar_t) * strlen('\\?\') to the path length before
checking it against MAX_PATH instead of just the 4-bytes needed by '\\?\'.
'\\?\' is used when converting a filename into a device namespace path.