XnView Software

metal450 wrote: Fri Dec 16, 2022 3:58 pm So then by "i've tried [...] all is ok...", is he trying to say "I cannot reproduce the behavior in the same mode/configuration as shown in the video"? If so, I'm not sure how else I can communicate the bug. I just tried it on a 2nd PC, & the behavior is the same.

xnview wrote: Sun Dec 18, 2022 9:27 am which pathname/filename do you have?

D:\_Pics+Vids_\PicsToSort\2020-02) Covid (Covey,Kingston,Iceland,Kauai,Baltic)\2022-07-26) EU (UK,Finland,Estonia,Lithuania,Belarus,Poland)\2022-08-04) Estonia - Tallinn Pharmacy; Creative City; Prison; Coastal Bikeride (Compressed)\4803 - 20220804_120509 (Glo).jpg

\\?\D:\_Pics+Vids_\PicsToSort\2020-02) Covid (Covey,Kingston,Iceland,Kauai,Baltic)\2022-07-26) EU (UK,Finland,Estonia,Lithuania,Belarus,Poland)\2022-08-04) Estonia - Tallinn Pharmacy; Creative City; Prison; Coastal Bikeride (Compressed)

https://learn.microsoft.com/en-us/windows/win32/fileio/naming-a-file#win32-file-namespaces wrote:For file I/O, the "\\?\" prefix to a path string tells the Windows APIs to disable all string parsing and to send the string that follows it straight to the file system. For example, if the file system supports large paths and file names, you can exceed the MAX_PATH limits that are otherwise enforced by the Windows APIs. For more information about the normal maximum path limitation, see the previous section Maximum Path Length Limitation.

Because it turns off automatic expansion of the path string, the "\\?\" prefix also allows the use of ".." and "." in the path names, which can be useful if you are attempting to perform operations on a file with these otherwise reserved relative path specifiers as part of the fully qualified path.

Many but not all file I/O APIs support "\\?\"; you should look at the reference topic for each API to be sure.

Note that Unicode APIs should be used to make sure the "\\?\" prefix allows you to exceed the MAX_PATH