Microsoft KB Archive/811617

From BetaArchive Wiki
Knowledge Base


The file migration utility cannot handle Japanese file or folder names from a NetWare Macintosh volume

Article ID: 811617

Article Last Modified on 2/17/2007



APPLIES TO

  • Microsoft Windows 2000 Server
  • Microsoft Windows 2000 Advanced Server
  • Microsoft Windows Services for NetWare 5.0



IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry


SYMPTOMS

Support was added in Services for NetWare 5.0 Service Pack 1 (SP1) to migrate Macintosh files from NetWare volumes. However, the migration utility cannot handle Japanese file or folder names correctly. Some Japanese file or folder names are not correct after being migrated.

For additional information about Services for NetWare 5.0 SP1, click the following article number to view the article in the Microsoft Knowledge Base:

316094 List of Problems That Are Fixed in Services for NetWare 5.0 Service Packs


WORKAROUND

WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
To work around this problem:

  1. Add a registry key that is named File migrate Options to the following registry key:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSDSS\Parameters

  2. Add the following registry value:

    Key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSDSS\Parameters\File migrate Options
    Name: MacFileName
    Data type: REG_DWORD
    Value: 0


STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

This problem was corrected in Windows 2000 Service Pack 4.

Keywords: kbpending kbbug KB811617