TITLE:              TSRs and NetWare Lite
DOCUMENT ID:        TID1200476
DOCUMENT REVISION:  1
DATE:               31MAR95
ALERT STATUS:       Yellow
README FOR:         NA

NOVELL PRODUCT and VERSION:
NETWARE LITE V1.1

ABSTRACT:
NA

---------------------------------------------------------------------
DISCLAIMER: THE ORIGIN OF THIS INFORMATION MAY BE INTERNAL OR
EXTERNAL TO NOVELL.  NOVELL MAKES EVERY EFFORT WITHIN ITS MEAN TO
VERIFY THIS INFORMATION. HOWEVER, THE INFORMATION PROVIDED IN THIS
DOCUMENT IS FOR YOUR INFORMATION ONLY. NOVELL MAKES NO EXPLICIT OR
IMPLIED CLAIMS TO THE VALIDITY OF THIS INFORMATION.
---------------------------------------------------------------------

ISSUE:

TSRS AND NETWARE LITE TSR (TERMINATE AND STAY RESIDENT)

NetWare Lite is designed around two primary TSRs.

1.   SERVER.EXE, that acts as the "disperser" of requests whether it
be printing or file services.  SERVER.EXE is quite complex and
considers several issues particularly background printing,
DOS/Windows busy flags, file sharing (through Share), and
communication with other servers/clients on the network.

2.   CLIENT.EXE acts as the redirector if the request is not for DOS.

Because both SERVER.EXE and CLIENT.EXE execute as a TSR on DOS, it is
necessary to hook interrupts to provide the functionality for NetWare
Lite.

Typically, problems will be encountered when two or more TSRs attempt
to hook an interrupt and may not be aware of the other TSR hooking
that interrupt.  This, in essence, is usually the cause of TSRs not
coexisting with one another.  In a peer-to-peer network such as
NetWare Lite the issue is greatly magnified due to functionality
requirements that a peer-to-peer  LAN provides.

Novell, has not done a comprehensive test matrix regarding
compatibility with other TSRs and NetWare Lite.  However, it is
recommended that the TSR vendor be contacted for compatibility with
NetWare Lite v1.1 if problems are met.

TSRS KNOWN TO HAVE PROBLEMS

1.   Pyro (screen saver)
     Symptoms: Locks other stations when it activates.

2.   PC Support Program (3270,5250 emulation)
     Symptoms: Locks other stations and causes printing not to work.

Note:  Other resident applications such as ViewMax (with DR DOS), and
DESQview may exhibit similar problems.

SUGGESTED WORKAROUND

If problems are met and several applications or TSRs are being
loaded, you may consider the following suggestions:

1.   TSRs come in many forms such as, virus checking, screen savers,
cache drivers, mouse drivers, or hotkey (popup) type applications.

     (a)  First remove TSRs one at a time until a possible culprit is
     identified.

     (b)  Try rearranging the load order of other TSRs and NetWare
     Lite.

     (c)  If using Windows, check to see if TSRs are loaded before
     Windows or from Windows using an icon or if loading from a DOS
     box.  Depending on which method is used, you may try changing
     the load order or method.

2.   If memory management is being used, check to see where TSRs are
loading.  Sometimes a larger TSR may not have enough Upper memory
available and will load into conventional memory.  This may be
undesirable if it uses to much conventional memory.  You may try
loading different TSRs to Upper or Conventional memory to see what
works best for you.

---------------------------------------------------------------------
Any trademarks referenced in this document are the property of their
respective owners. Consult your product manuals for complete
trademark information.
---------------------------------------------------------------------