Re: FindFirstFileExW and MAX_PATH
- From: "Remy Lebeau" <no.spam@xxxxxxxxxxx>
- Date: Fri, 4 Jan 2008 15:46:26 -0800
"Egbert Nierop" <egbert_nierop@xxxxxxxxxxxxxx> wrote in message
news:eRuk1nyTIHA.4696@xxxxxxxxxxxxxxxxxxxxxxx
I find it so interesting, that even a 64 bit OS, still uses that API,
limited to 260 (249 in fact) characters for directories and files.
The complete path and filename together is limited to MAX_PATH characters by
default, yes.
FindFirstFileExW tells us about the \\?\ prefix, to overcome that
limit, BUT the WIN32_FIND_DATA structure, contains just
260 characters for the cFilename section! :)
The cFilename member receives just the filename, not the complete path
leading up to the filename. When '\\?\' is used, individual components of a
path (aka each subfolder and file name) are each limited to 255 characters
max. So receiving such a filename still fits within a buffer of MAX_PATH
size regardless of whether '\\?\' is used or not.
Gambit
.
- Follow-Ups:
- Re: FindFirstFileExW and MAX_PATH
- From: Egbert Nierop
- Re: FindFirstFileExW and MAX_PATH
- References:
- FindFirstFileExW and MAX_PATH
- From: Egbert Nierop
- FindFirstFileExW and MAX_PATH
- Prev by Date: FindFirstFileExW and MAX_PATH
- Next by Date: bad_alloc
- Previous by thread: FindFirstFileExW and MAX_PATH
- Next by thread: Re: FindFirstFileExW and MAX_PATH
- Index(es):
Relevant Pages
|