Home of the Squeezebox™ & Transporter® network music players.
Page 2 of 2 FirstFirst 12
Results 11 to 14 of 14
  1. #11
    Junior Member
    Join Date
    Jan 2017
    Posts
    5
    You are absolutely right! The new SSD drive has 8dot3name disabled. It's working now and thank you very much for the advice.

    For reference, here are the commands that I used in Windows 10 (d: is new SSD, f: is old HDD):

    1. Run Command prompt as Administrator

    2. Compare settings of each volume (0 is enabled, 1 is disabled, 2 is default)
    >fsutil 8dot3name query d:
    The volume state is: 1 (8dot3 name creation is disabled).
    The registry state is: 2 (Per volume setting - the default).

    Based on the above two settings, 8dot3 name creation is disabled on d:

    >fsutil 8dot3name query f:
    The volume state is: 0 (8dot3 name creation is enabled).
    The registry state is: 2 (Per volume setting - the default).

    Based on the above two settings, 8dot3 name creation is enabled on f:

    3. Enable on new SSD drive
    >fsutil 8dot3name set d: 0
    Successfully enabled 8dot3name generation on d:

    4. Copy the music files again from HDD to SSD.

    5. Rescan the music folder. Now the Chinese and Japanese songs are available for playback!

    CASE CLOSED.

    Quote Originally Posted by DJanGo View Post
    i think (better know) thats a kind of myth ;-)

    Why should M$ add a tool - formerly just supplied by the Winblows Reskits - called robocopy to Winblows when exploider is most common and practical?

    Are you sure, everything is the same on the new drive?
    Are these drives both ntfs?

    Are both drives supporting 8.3 filename support?
    Last edited by soloaudio; 2017-01-30 at 17:41.

  2. #12
    Junior Member
    Join Date
    Jan 2019
    Posts
    1

    UTF-8 for legacy apps

    Just for the shake of completion, in Windows 10 now you can set UTF-8 for legacy apps (BETA). This solve the issue for non 8dot3 names and filesytems that don't support it (i.e. ReFS)


    Control Panel -> Regiˇn -> Administrative -> Change system Locale.
    Name:  Capture.PNG
Views: 212
Size:  25.6 KB

    Hope it helps.

  3. #13
    Member
    Join Date
    Nov 2005
    Location
    London, UK
    Posts
    41
    Quote Originally Posted by Lain_OTN View Post
    Just for the shake of completion, in Windows 10 now you can set UTF-8 for legacy apps (BETA). This solve the issue for non 8dot3 names and filesytems that don't support it (i.e. ReFS)


    Control Panel -> Regiˇn -> Administrative -> Change system Locale.
    Name:  Capture.PNG
Views: 212
Size:  25.6 KB

    Hope it helps.
    Many thanks for that Lain_OTN, works great now on my Windows 10 machine.

  4. #14
    Junior Member
    Join Date
    Jun 2021
    Posts
    1
    Quote Originally Posted by Lain_OTN View Post
    Just for the shake of completion, in Windows 10 now you can set UTF-8 for legacy apps (BETA). This solve the issue for non 8dot3 names and filesytems that don't support it (i.e. ReFS)


    Control Panel -> Regiˇn -> Administrative -> Change system Locale.
    Name:  Capture.PNG
Views: 212
Size:  25.6 KB

    Hope it helps.
    Just wanted to thank you for this. I had the same problem - LMS would not scan any song titles with Asian characters. This now allows LMS to scan and include these tracks. However, LMS doesn't display the correct characters.

    I have the language packs installed and the characters display correctly in File Explorer.

    Any ideas?

Tags for this Thread

Posting Permissions

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