Novell and Office Fail to Create UNC in WIN.INI or REG.DAT

 Last reviewed: September 10, 1996
Article ID: Q125866
The information in this article applies to:
  • Microsoft Office Setup for Windows, version 1.0
  • Microsoft Office for Windows, versions 4.0, 4.2, 4.3
  • Microsoft Excel for Windows, version 5.0
  • Microsoft Word for Windows, version 6.0
  • Microsoft Access, version 2.0
  • Microsoft PowerPoint for Windows, version 4.0
  • Microsoft Project for Windows, version 4.0

SUMMARY

The supporting files from Novell for the ClientWare for Netware do not work with the KRNL386.EXE from Microsoft Windows version 3.1. If you are using KRNL386.EXE from Windows version 3.1, with the ClientWare for Netware released with WINUP9 and DOSUP9, and the newer VLMUP2.EXE, NET33X.EXE, WINDR2.EXE and NWDLL2.EXE, you may experience problems when you start UNC applications.

MORE INFORMATION

To test if you are having problems with UNC application functionality, copy MSD.EXE to a network drive and try to start it from that location using UNC. For example try to start it from the following location 

   \\server\volume\test\msd.exe
(where MSD.EXE is in the TEST directory).

If MSD.EXE fails to start, you will want to ensure that the following conditions are met:

  1. You have a full upgrade of the latest drivers from Novell for the Netware Client.

  2. You have a complete installation of Microsoft Windows for Workgroups version 3.11. Ensure that the file KRNL386.EXE has a creation date and time of 11/1/93 3:11:00

KBCategory: kbsetup kbnetwork
KBSubcategory:

Additional reference words: 1.00



THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: September 10, 1996
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.