Article ID: 140400
Article Last Modified on 2/20/2007
APPLIES TO
- Microsoft Windows 2000 Service Pack 1
- Microsoft Windows 2000 Service Pack 2
- Microsoft Windows 2000 Service Pack 1
- Microsoft Windows 2000 Service Pack 2
- Microsoft Windows NT Workstation 3.51
- Microsoft Windows NT Workstation 4.0 Developer Edition
- Microsoft Windows NT Server 3.51
- Microsoft Windows NT Server 4.0 Standard Edition
This article was previously published under Q140400
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
Files or directories created in 8.3 file format on a NetWare server using Client Services for NetWare (CSNW) or Gateway Service for NetWare (GSNW) appear in uppercase only when the OS/2 Name Space service is installed.
CAUSE
If OS/2 Name Space is installed on a NetWare server, CSNW or GSNW should allow you to create files or directories in any character case. This works correctly for files or directories in long filename convention.
RESOLUTION
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 correct this problem, apply the fix mentioned below and then do the following:
- Run the Registry Editor (REGEDT32.EXE).
- From the HKEY_LOCAL_MACHINE subtree, go to the following key:
\System\CurrentControlSet\Services\NWRDR\parameters
- From the Edit menu, choose Add Value.
- Add the following:
Value Name: FavourLongNames
Data Type: REG_DWORD
Data: 0x1 (Hex)
NOTE: The default data value is 0 (which favors 8.3 file format)
- Choose OK and quit Registry Editor.
- Shut down and restart Windows NT.
STATUS
Microsoft has confirmed this to be a problem in Windows NT version 3.51. This problem was corrected in the latest Windows NT 3.51 U.S. Service Pack. For information on obtaining the Service Pack, query on the following word in the Microsoft Knowledge Base (without the spaces):
S E R V P A C K
Additional query words: prodnt nbipx NWCS Novell LFN fpnw 4.0
Keywords: kbprb KB140400
