Hi,
We have extensively tested that and I even created application for testing/searching that behavior. Unfortunately we have found it very very unstable and current approach is best we can do for now :(

You can download it at http://www.happymonkeying.com/eSupport/LongPathTest.exe (created 1024 long path and you need to delete it using Windows explorer) and for search of mapped drives you can use http://www.happymonkeying.com/eSupport/FindFullNamesGreaterThan255.exe

Please report results.

EDIT: just to be clear we already use https://msdn.microsoft.com/en-us/library/aa365247%28VS.85%29.aspx for whole MMW 4.1 and short paths needs to be manually used see http://www.mediamonkey.com/wiki/index.php/SDBFileSystem for scripts

I can't comment on the anniversary update, it's not the first time I see mentioned that Path can be longer, but I've had issues in the past with Windows chocking on long Paths even on networked devices. As MediaMonkey provides the tools to accomplish this I prefer to remain with Paths less than 255 characters for maximum compatibility.

[url]https://msdn.microsoft.com/en-us/library/aa365247(VS.85).aspx[/url]

From the Article;

"The Windows API has many functions that also have Unicode versions to permit an extended-length path for a maximum total path length of 32,767 characters. This type of path is composed of components separated by backslashes, each up to the value returned in the lpMaximumComponentLength parameter of the GetVolumeInformation function (this value is commonly 255 characters). To specify an extended-length path, use the "\\?\" prefix. For example, "\\?\D:\very long path"."

I think the misunderstanding is that NTFS can handle "255 UTF-16 Code Units," not "Characters."

You are confusing NTFS, and the Windows API. the Windows API and the "MAX_PATH" setting are what limits Windows to 260 (255 usable) characters for a path. NTFS has a much higher limitation.

Unless you really are talking about "NFS" in which case, the limit was 40 characters.

This isn't correct. NFS can't handle Path longer than 255.
So in case of network paths Windows can handle.

So it is a bug.

Windows Server 2016, and Windows 10 Anniversary has the ability to override this limitation.

The Insider Preview for Windows 10 from a few months ago added this functionality. There are already Store apps, and some Win32 apps that take advantage of this. I'm told.

Windows doesn't handle Paths longer than 255 characters. This means that although even in Windows you can create Paths longer various problems start propping up when you have Paths longer than 255 characters.

I'm using the latest and yes the path can be lnger than 255 characters.
I did a mapped drive now to shorten the path in this case and it's working.

This isn't good implemented and is in my opinion a bug.

Thanks for your help

Which version of MediaMonkey? Could the Path be really long (>255 characters)?

Hi guys,

I'm struggling with importing my music from a NAS.
Most of my music is imported well but there still some files Mediamonkey can’t import. If I move these files to my local disc the import is working fine.
I have tried UNC with name or IP or mapped drive. Everything is the same.

Thanks in advance
chokdee