Official eMule-Board: Overly Long File Name Issue? - Official eMule-Board

Jump to content


Page 1 of 1

Overly Long File Name Issue?

#1 User is offline   stoatwblr 

  • Member
  • PipPip
  • Group: Members
  • Posts: 17
  • Joined: 15-February 13

Posted 09 November 2020 - 09:29 PM

I'm getting a bunch of these

09/11/2020 15:09:20: Hashing file: ""
09/11/2020 15:09:20: Failed to open really.long.file.name.with.lots.of.dots.1x01.in.which.an.even.longer.title.name.is.buried.avi


These filenames are > 122 characters, and the directory path is 138 characters at 7 levels deep

Files with slightly shorter names in the same directories are read fine


Most other files are also at 7 levels of nesting, so I don't think that's the issue

Is there an arbitrary limit on file name length?
(Running 0.60a inside wine on Ubuntu)
0

#2 User is offline   stoatwblr 

  • Member
  • PipPip
  • Group: Members
  • Posts: 17
  • Joined: 15-February 13

Posted 09 November 2020 - 09:32 PM

View Poststoatwblr, on 09 November 2020 - 09:29 PM, said:

I'm getting a bunch of these


It looks like MAX_PATH is being hit - this is overrideable and only a default by the look of things
0

#3 User is offline   antonymous 

  • Member
  • PipPip
  • Group: Members
  • Posts: 41
  • Joined: 17-March 08

Posted 19 November 2020 - 10:07 AM

This is the 260 character limit enforced by NTFS. Apparently it's been removed but apps need to use the new API calls.
0

  • Member Options

Page 1 of 1

1 User(s) are reading this topic
0 members, 1 guests, 0 anonymous users