Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 334
  • Last Modified:

NetWare client32 for Win95 error.

Hi.

When I installed the Client32 (I think it´s the one that comes with the OS CD.) I got the following error on reboot: NWDRV -3.00-30: Initialization of the unicode tables failed.
Country ID=46, code page=1252, DLL=LOCWIN16.DLL
The unicode table couldn´t be initialized.

Why? What does it mean? I would like a comprehensiv explanation, if possible.

Thanks

Mikael
0
Mikael012197
Asked:
Mikael012197
1 Solution
 
jp021897Commented:
Mikael,
If you go to support.novell.com and click and KnowledgeBase and search for NWDRV-3.00-30 you will find many references to your problem.  Basically, some unicode files didn't get to where they were expected (i.e. \WINDOWS\NLS\ directory).  Try doing what I copied below and if that doesn't fix another of the suggestions is to re-install the client.  It's a good idea to use the default directories.  Shortcuts and personal preferences screw me up many a time.

NWDRV 3.00-30 unicode error message  (Last modified: 06DEC1996)

     This document (2917963) is provided subject to the disclaimer at the end of this document.
         Forward this document to a colleague
        Submit comment about this document to its author

     Symptom

     A customer installed the german version of Client 32 for Windows 95 v2.11. When restarting the
     machine he receives an error message:

     NWDRV 3.00-30 Die Initialisierung der Unicode Tabelle schlug fehl
     Landes ID = 49 Codeseite = 1252 DLL=NWLOCALE.DLL

     which means:
     NWDRV 3.00-30 initialization of unicode table failed
     Country ID = 49 Codepage = 1252 DLL=NWLOCALE.DLL

     The same message appeared with DLL=LOCWIN16.DLL

     Cause

     Checked the local NLS-directory. Not all unicode files were in the C:\WINDOWS\NLS directory:
     the file UNI_COL.049 was missing.

     Solution

     Copied the missing file UNI_COL.049 into the WINDOWS\NLS solved the problem.

     The following files are required in the WINDOWS\NLS-directory:

     UNI_1252.049
     1252_UNI.049
     UNI_COL.049
     UNI_MON.049

Good luck,

Jerry
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now