NTFS/ExFAT/HFS Long Filenames support

Any ideas about how to improve MediaMonkey? Let us know!

Moderator: Gurus

tarasis
Posts: 67
Joined: Thu Feb 16, 2006 6:29 am
Location: Buchholz, Germany
Contact:

NTFS/ExFAT/HFS Long Filenames support

Post by tarasis » Wed Aug 31, 2016 3:51 am

Peke wrote: 255+ filenames: MMW already support that but it is disabled due the system limitations
RE MAC: It certainly should support that.
Superb Peke!

For the Windows version could you enable a registry check to see if long file paths have been enabled and the drive is NTFS/ExFAT/HFS* formatted, and then enable the support in MMW?

* Using Apple's HFS drivers for Read only access to a drive.

Peke
Posts: 13263
Joined: Tue Jun 10, 2003 7:21 pm
Location: Serbia
Contact:

Re: NTFS/ExFAT/HFS Long Filenames support

Post by Peke » Wed Aug 31, 2016 8:39 am

Hi,
I split topics to not have confusion.
tarasis wrote:For the Windows version could you enable a registry check to see if long file paths have been enabled and the drive is NTFS/ExFAT/HFS* formatted, and then enable the support in MMW?
Where do you check that registry settings I thought that as of Win 7 and NTFS v5 it is enabled by default using "\\?\" prefix for filename to force Unicode API and filenames up to 65535 chars?

You can try to check your system with this two apps:
http://www.happymonkeying.com/eSupport/ ... han255.exe
http://www.happymonkeying.com/eSupport/LongPathTest.exe

EDIT: It is important for me to note that few years ago I switched completely to NAS handle all the files and MMW is now accessing my whole 120k library over LAN and UNC paths while I never get time to look at http://www.citi.umich.edu/projects/nfsv4/windows/ and https://github.com/nekoni/nekodrive to see NFS implementation.
Best regards,
Pavle
MediaMonkey Team lead QA/Tech Support guru
Admin of Free MediaMonkey addon Site HappyMonkeying
Image
Image
How to add SCREENSHOTS to forum

tarasis
Posts: 67
Joined: Thu Feb 16, 2006 6:29 am
Location: Buchholz, Germany
Contact:

Re: NTFS/ExFAT/HFS Long Filenames support

Post by tarasis » Thu Sep 01, 2016 6:59 pm

I understand the split Peke.
Peke wrote: Where do you check that registry settings I thought that as of Win 7 and NTFS v5 it is enabled by default using "\\?\" prefix for filename to force Unicode API and filenames up to 65535 chars?

You can try to check your system with this two apps:
http://www.happymonkeying.com/eSupport/ ... han255.exe
http://www.happymonkeying.com/eSupport/LongPathTest.exe

EDIT: It is important for me to note that few years ago I switched completely to NAS handle all the files and MMW is now accessing my whole 120k library over LAN and UNC paths while I never get time to look at http://www.citi.umich.edu/projects/nfsv4/windows/ and https://github.com/nekoni/nekodrive to see NFS implementation.
You can see some bits about removing the limit here http://www.tenforums.com/windows-10-new ... 10-rs.html and here http://betanews.com/2016/05/29/long-paths-windows-10/ . Note that in the anniversary update the Policy name is different. Its now in
Computer Policy > Computer Configuration > Administrative Templates > System > Filesystem
under the title Enable Win32 long paths

I sadly don't have my music on a NAS, it lives on a Drobo formatted as HFS+ and used to be connected to a Mac Mini that has got too old. It now sits connected to my Hackintosh which dualboots between OSX and Win10. When in Windows the Drobo was mounted as a drive to read using Apple's HFS drivers; up until the Anniversary release of Win 10 which brought in different rules for driver signing so they currently don't work.

Anyway MM would balk & crash when it got into scanning folders that where nested to do. File Explorer would see those deep folders as empty even when they weren't and sharing the drive on the network and accessing it from an iOS app (nPlayer) would also see an empty folder when you went too deep.

Unfortunately due to update stopping the Apple driver working for now I can't test the programs against the drobo ... oh BUT I can test them on an exFAT drive that I use to share data back and forth between the two operating systems. I will testing that properly in the morning by setting up the path in OS X, the longest I could create in Windows on the exFAT drive was 247 according to the FindFullNamesGreaterThan255 program.

"H:\Mac Stuff\iTunes Library\Music\John Williams\The Empire Strikes Back - Enhanced Edition Limited Release\The Empire Strikes Back - Enhanced Edition Limited Release\The Empire Strikes Back - Enhanced Edition Limited Release\The Empire Strikes Bac"

However your LongPathTest program was apparently able to create a filename of 1033 character BUT File Explorer won't go deeper than folder 31, nor will the command prompt. I can see folder 32 but it won't go in it.

Code: Select all

H:\!!!TEST ROOT\1!ABCD\2!ABCD\3!ABCD\4!ABCD\5!ABCD\6!ABCD\7!ABCD\8!ABCD\9!ABCD\10!ABCD\11!ABCD\12!ABCD\13!ABCD\14!ABCD\15!ABCD\16!ABCD\17!ABCD\18!ABCD\19!ABCD\20!ABCD\21!ABCD\22!ABCD\23!ABCD\24!ABCD\25!ABCD\26!ABCD\27!ABCD\28!ABCD\29!ABCD\30!ABCD\31!ABCD>cd "32!ABCD"
The filename or extension is too long.

H:\!!!TEST ROOT\1!ABCD\2!ABCD\3!ABCD\4!ABCD\5!ABCD\6!ABCD\7!ABCD\8!ABCD\9!ABCD\10!ABCD\11!ABCD\12!ABCD\13!ABCD\14!ABCD\15!ABCD\16!ABCD\17!ABCD\18!ABCD\19!ABCD\20!ABCD\21!ABCD\22!ABCD\23!ABCD\24!ABCD\25!ABCD\26!ABCD\27!ABCD\28!ABCD\29!ABCD\30!ABCD\31!ABCD>dir
 Volume in drive H is OddsEnds
 Volume Serial Number is 54DF-28EE

 Directory of H:\!!!TEST ROOT\1!ABCD\2!ABCD\3!ABCD\4!ABCD\5!ABCD\6!ABCD\7!ABCD\8!ABCD\9!ABCD\10!ABCD\11!ABCD\12!ABCD\13!ABCD\14!ABCD\15!ABCD\16!ABCD\17!ABCD\18!ABCD\19!ABCD\20!ABCD\21!ABCD\22!ABCD\23!ABCD\24!ABCD\25!ABCD\26!ABCD\27!ABCD\28!ABCD\29!ABCD\30!ABCD\31!ABCD

02/09/2016  01:52    <DIR>          .
02/09/2016  01:52    <DIR>          ..
02/09/2016  01:52    <DIR>          32!ABCD
               0 File(s)              0 bytes
               3 Dir(s)  50,447,253,504 bytes free

Post Reply