The \??\ notation works unless one is forced to write code for win9x. On
NT one can always use the unicode version of the call and go beyond 260
chars.
Win9x compatibility is a poor excuse to write software that goes into
infinite loops or crashes trying to iterate on folders with a total length
of more than MAX_PATH.
Rick
“Tony Hoyle” wrote in message news:xxxxx@ntfsd…
> Tony Mason wrote:
>> As to the last point, I’m honestly not quite sure what it means. WHICH
>> OS defined constant? It seems to me that the problem is the OS defines
>
> Pretty much no C/C++ code can exceed MAX_PATH because the runtime is
> hardcoded to limit to that - so everyone uses that for example. It’s a
> real OS limit.
>
> Also until CreateFile, etc. are fixed of course nobody can even change the
> constants, because they reflect real API limits. the \??\ notation is
> documented to work in ‘most’ cases - which implies there are cases were
> even that simply won’t work to extend the path.
>
> Tony
>