Long path names (>260) works with some file browsers

  1. jimbo45's Avatar
    Posts : 10,503
    Windows / Linux : Arch Linux
       #1

    Long path names (>260) works with some file browsers


    Hi folks

    Some file browsers now work with the long file names but "bog standard file explorer" plus applications based on the old explorer api will still fail. - You set long file names via reg key -- it's in the tutorials.

    Anyway for example FILEZILLA (an FTP client) running on Windows can show correct files on a NAS server. File explorer fails.

    Here's the screenshot

    Long path names (>260) works with some file browsers-longfiles.png

    Files transferred successfully no names lost and can be seen with FILEZILLA on the LOCAL (windows machine) properly


    Long path names (>260) works with some file browsers-longfiles2-png.png

    After transfer the files can still be viewed correctly also in File explorer because the path length is shorter than 260 but it's a start to at least transferring files with long path names from a NAS server to windows. Files also play correctly.

    Long path names (>260) works with some file browsers-longfiles3.png

    Note : the basic problem is that the path name on the NAS server could well be quite long -- this NAS server has 20TB of HDD on it - around 4 - 5 TB of music. The destination path on windows won't include the whole NAS path length but you probably want the folder and music files which will pretty well always be <260 chars in path name lengths)

    File explorer breaks down if you merely use it for copying these files vis "Connect Network drive" as it can't display the NAS directory properly as shown.



    C'mon Ms can't you FIX file explorer please instead of getting involved in things like icons and live tiles . !!!!!!

    Cheers
    jimbo
    Last edited by jimbo45; 04 Mar 2020 at 05:03.
      My Computer


  2. Posts : 264
    Windows 10
       #2

    I guess it is because not enough people use paths with a depth of over 200 characters. But yes, it is about time they do that right.
      My Computer

  3. jimbo45's Avatar
    Posts : 10,503
    Windows / Linux : Arch Linux
    Thread Starter
       #3

    xaccell said:
    I guess it is because not enough people use paths with a depth of over 200 characters. But yes, it is about time they do that right.
    Hi there
    You are mainly right -- the main problem as I see it is getting files from NAS to Windows-- if Windows file explorer can then display the paths properly then there would be no problem (usually) in copying files as copying FROM NAS to WINDOWS it's usually copy from NAS on \\verylongpathname\directoryname to Windows e.g D:\shorterdirectory\filenames

    Cheers
    jimbo
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 00:42.
Find Us




Windows 10 Forums