Solved

NetWare client32 for Win95 error.

Posted on 1998-10-22
1
323 Views
Last Modified: 2008-02-01
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
Comment
Question by:Mikael012197
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
1 Comment
 

Accepted Solution

by:
jp021897 earned 100 total points
ID: 1593842
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

Featured Post

Instantly Create Instructional Tutorials

Contextual Guidance at the moment of need helps your employees adopt to new software or processes instantly. Boost knowledge retention and employee engagement step-by-step with one easy solution.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

After seeing numerous questions for Dynamic Data Validation I notice that most have used Visual Basic to solve the problem. This suggestion is purely formula based and can be used in multiple rows.
Compliance and data security require steps be taken to prevent unauthorized users from copying data.  Here's one method to prevent data theft via USB drives (and writable optical media).
Monitoring a network: why having a policy is the best policy? Michael Kulchisky, MCSE, MCSA, MCP, VTSP, VSP, CCSP outlines the enormous benefits of having a policy-based approach when monitoring medium and large networks. Software utilized in this v…
In this video you will find out how to export Office 365 mailboxes using the built in eDiscovery tool. Bear in mind that although this method might be useful in some cases, using PST files as Office 365 backup is troublesome in a long run (more on t…

628 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question