Could you please enlighten us as to the purpose of LOCWIN16.DLL?
Articles and Tips: qna
01 Sep 1997
Q.
Dear Ab-end: A colleague of mine had Unicode problems on his workstation, which he resolved by replacing the LOCWIN16.DLL file on his computer with one from a different PC. Neither of us is quite sure why this worked. Could you please enlighten us as to the purpose of LOCWIN16.DLL?
-- In the Dark in Dublin
A.
Dear Dark: The LOCWIN16.DLL file is a library containing all of the Unicode API library calls. These make reference calls to the Unicode files that are installed in the \NLS directories under the startup directories on Windows, Windows 95, Windows NT, and OS2 workstations. If this file becomes corrupted, or if an installed application overwrites this LOCWIN16.DLL file with a different version or date, your workstation client software may not load. If you have multiple LOCWIN16.DLL files and a different version of this file is placed in a directory that is called from the PATH statement before your client requester is, you can also have Unicode problems.
The best way to install Novell's client software is through the client software's own installation process, which places a uniform number of files with matching dates and versions in the appropriate directories. Unfortunately, it can't do much about applications that later overwrite or load a version in the PATH before it. The version of the file that your friend "borrowed" from another workstation must have matched the version needed.
Another tool to help you troubleshoot this kind of problem is Novell Workstation Diagnostic utility (NWD2.EXE) that is found in the DIAGTOOL directory when you download the IntranetWare Client for Window 95 software and expand its corresponding directory structures (it's also found on a number of client CD-ROMs that you can get from Novell). The NWD2.EXE file will show you the version number/ date/ times and directory path of all Novell-related files. (For information about NWD2.EXE, see the NetNote "Using NWD2.EXE, Novell's Workstation Diagnostic Utility" found in this issue.)
* Originally published in Novell AppNotes
Disclaimer
The origin of this information may be internal or external to Novell. While Novell makes all reasonable efforts to verify this information, Novell does not make explicit or implied claims to its validity.