Cannot Load TSRs in NetWare Login Script

Last reviewed: September 13, 1995
Article ID: Q127794

The information in this article applies to:

Microsoft Windows 95

SUMMARY

If you are using the Microsoft client for NetWare networks and you are using a login script to log on to the NetWare network, any terminate-and- stay-resident (TSR) programs in the login script are not loaded.

MORE INFORMATION

This behavior is by design. You cannot load TSRs globally in the login script because there is more than one virtual machine (VM) at this time.

Some TSRs require that you be logged on to the network before the TSR can be loaded. Since you are not logged on to the network until Windows 95 starts, these TSRs cannot be loaded when the AUTOEXEC.BAT file is processed. If you need to use a TSR that must be loaded in the login script, you must use the Novell NetWare client instead of the Microsoft client for NetWare networks. If a TSR does not require that it be loaded in the login script then you can load it in the AUTOEXEC.BAT file instead.

KBCategory: kbnetwork kb3rdparty
KBSubcategory: wpp95 win95 msnets 3rdpartynet
Additional reference words: 95 nwclient

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 13, 1995
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.