Option to always use UNC versions of local drive paths, to force long filename/path handling

/Option to always use UNC versions of local drive paths, to force long filename/path handling

Option to always use UNC versions of local drive paths, to force long filename/path handling

Can there be an option to force the use of storage paths/APIs that handle long paths/long filenames, as relevant for the OS (especially Windows)

For example on one well-known Windows hashing program I use, one has to put \?D:PATHTOFILE…. rather than D:PATHTOFILE…. if there might be long paths, otherwise some files with long paths aren’t “seen”.

By | 2017-06-11T18:27:25+00:00 June 10th, 2017|1 Comment

About the Author:

One Comment

  1. Ted 11/06/2017 at 18:30 - Reply

    Please see the manual. Quickhash, unlike your other preferred utility, automatically deals with long path names and can find files, and copy files, in folders up to 32K characters long.

    On Windows, as of v2.6.4, files that live in a folder whose length exceeds 260 characters
    should now be found by QuickHash…

Leave a Reply