Results 1 to 5 of 5
  1. #1
    Join Date
    Oct 2010
    Posts
    53

    Question Why does BC allow very long paths/names when Explorer doesn't?

    When I copy or move files with deep paths and/or long names, Windows Explorer will sometimes report that the path would be too long. In these cases, there is a limit to the depth and length, which is being exceeded.

    However, I can use Beyond Compare to copy/move the files instead and it works OK.

    how come?
    Last edited by arjaydavis; 17-Dec-2013 at 03:55 PM.

  2. #2
    Join Date
    Oct 2007
    Location
    Madison, WI
    Posts
    2,524

    Default

    Beyond Compare supports paths up to 65,000 characters. Explorer is limited to 260 characters because of backwards compatibility requirements.
    ZoŽ P Scooter Software

  3. #3
    Join Date
    Oct 2010
    Posts
    53

    Default

    Thanks for responding so quick! So NTFS itself supports longer than 260, Explorer is just imposing an 'artificial' limit then?

  4. #4
    Join Date
    Oct 2007
    Location
    Madison, WI
    Posts
    2,524

    Default

    Exactly. Most applications have the 260 character limit because that was the limit Windows had for a long time and you need to jump through some hoops to support the longer ones. BC supports them where it can, but certain things like deleting to the recycle bin still have the shorter limit. If you do run into a case where the shorter limit is in effect there should be an obvious error message to that effect.
    ZoŽ P Scooter Software

  5. #5
    Join Date
    Oct 2010
    Posts
    53

    Default

    Thanks!

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •