Server README.TXT for WanderLink Release 1.00 (updated 11/17/94).
Note:  This file will appear as READSRVR.TXT after installation. 

=======================================================================
NOTES ON THE WANDERLINK SERVER
=======================================================================

This file provides important information not included in the 
WANDERLINK ADMINISTRATOR GUIDE. 
 
This file is divided into the following sections: 

1. Tips & Troubleshooting 
   1.1  AIOCOMX driver "lost hardware interrupt" message appears 
   1.2  In NetWare 3.11 only: Unloading WLADS resources not released
   1.3  MONITOR.NLM reports high server utilization

2. Side-effects of Domain Filtering

3. NetWare 3.11 Files

4. WanderLink Server Memory Requirements


=======================================================================
1.  Tips & Troubleshooting 
=======================================================================
----------------------------------------------------------------------- 
1.1  AIOCOMX Driver "lost hardware interrupt" Message Appears 
----------------------------------------------------------------------- 
If you are using AIOCOMX with one or more COM ports, the following
message can occur: 

"Primary interrupt controller detected a lost hardware interrupt." 

This message is the result of increased interrupt activity and is not
a cause for concern.  AIOCOMX does not send data if the DSR is low. If
you are using COM ports, make sure your modem maintains DSR high. 
 
----------------------------------------------------------------------- 
1.2  In NetWare 3.11 only: Unloading WLADS reveals that resources were
     not released.
----------------------------------------------------------------------- 
In NetWare 3.11, under certain conditions a small "memory leak" may 
occur in the WLADS.NLM program on the server. It only occurs while 
running the WanderLink Administrator, and is most likely to occur 
while monitoring Port Statistics.

The symptom is that upon unloading WLADS, the server console reports 
that resources were not released. Also, the leak can be observed in 
MONITOR.NLM as increased usage by WLADS of "Alloc Short Term Memory".

It is highly unlikely that this memory leakage would amount to enough 
memory to cause a problem. In any case, the memory is recaptured when 
WanderLink is unloaded.

The problem seems to be due to a bug in the NetWare 3.11 Operating 
System; the problem does not appear in later versions. We are working 
with Novell to find a fix or workaround.
 
----------------------------------------------------------------------- 
1.3  MONITOR.NLM reports high server utilization
----------------------------------------------------------------------- 
Many administrators watch the Utilization value in MONITOR to see how 
different NLMs affect server loading.

You may notice that when a WanderLink connection is established, the 
utilization value jumps to a high number (like 60% or 80%), even 
when there is no data being transported over the WanderLink 
connection. Please be assured that this is not an accurate reflection 
of WanderLink's loading of the server.

THE UTILIZATION VALUE IN MONITOR IS NOT A RELIABLE MEASURE OF SERVER 
UTILIZATION (to put it bluntly). The Utilization reported by Monitor 
during use of WanderLink can vary all over the place as different 
NLMs are loaded and unloaded and as WanderLink connections are made 
and broken. MONITOR's algorithm for determining utilization seems to 
be history-dependent and easily confused.

Merely opening a WanderLink connection does not place significant load 
on the server but does alter thread switching dynamics sufficiently 
to cause MONITOR to report high utilization values. Only when data is 
actually passing over the line is there a server load of any 
significance. 

=======================================================================
2.  Side-effects of Domain Filtering
=======================================================================
If you have set up a Domain Filter for any user, there are some 
possible side-effects that you should be aware of.

   -    The SLIST command will display all servers available on the 
	network, even ones that the user is excluded from. This is due 
	to the fact that SLIST gets the names of all servers from one 
	server to which it is attached (i.e., it does not get packets 
	individually from each server). This may result in some 
	confusion for the user: if he or she attempts to attach to one 
	of the listed servers, the attempt will fail if there is a 
	domain restriction.

   -    The user must be careful not to set the preferred server for 
	NETX or VLM to a server that he or she has no access to.

   -    If there are NDS (NetWare 4) servers on the network, and the 
	user is excluded from one of them, it is possible that when 
	VLM is run it will fail to find a server. This problem will be 
	fixed in the next release. Meanwhile, as a workaround for any 
	user with this problem, make sure the "NETWARE PROTOCOLS" line 
	in the "NETWARE DOS REQUESTER" section of NET.CFG reads as 
	follows:

	NETWARE PROTOCOL = BIND NDS

	This sets the order that VLM will search for servers for its 
	initial connection to bindery first, NDS second.

=======================================================================
3.  NetWare 3.11 Files
=======================================================================
WanderLink requires that certain NLMs be available in order for it to 
run. For certain NLMs, recent versions are required.

The Supplemental Files diskette contains various NLMs that you may need 
to copy to your SYS:SYSTEM directory.

WanderLink is an ODI-compliant LAN driver, which requires certain
support files provided by Novell. If you are currently using an
ODI-compliant driver, then you already have these NLMs. If you are not,
copy the following NLMs from the Novell Files diskette to your
server's SYS:SYSTEM directory.

The following NLMs are required by any ODI LAN driver such as 
WanderLink (If you have upgraded to more recent LAN drivers, you may 
already have these files.):

PATCHMAN.NLM
ETHERTSM.NLM    (for EtherNet cards)
TOKENTSM.NLM    (for TokenRing cards)
LSLENH.NLM
MSM31X.NLM
NE2000.LAN
MONITOR.NLM     (to view ODI drivers statistics)
CLIB.NLM

The following NLMs implement Novell's AIO system:

AIO.NLM       (dynamic linkage to AIO drivers)
AIOCOMX.NLM   (AIO driver for standard serial ports)

"Burst mode" is a transmission technique that Novell has implemented 
that can dramatically improve throughput during file transfer, 
especially over remote links such as WanderLink. This capability is 
built into NetWare 3.12 and 4.xx. To make it available on a NetWare 
3.11 server, load the following NLM:

PBURST.NLM

=======================================================================
4.  WanderLink Server Memory Requirements
=======================================================================
WanderLink loads three NLMs to perform its work:  WLADS.NLM, WLAIO.NLM,
and WLHSM.NLM.  The basic memory requirements for these programs is
approximately 330 Kbytes.

For every licensed WanderLink port, approximately 25 Kbytes of memory
is allocated.

Whenever a WanderLink connection is made, additional memory is 
allocated at run-time.  The amount of memory depends on the services
required for the connection, and can range from 10 Kbytes up to
a maximum of 175 Kbytes for a connection using data compression.

The following table summarizes WanderLink server memory requirements:
-----------------------------------------------------------------------
BASIC NLM MODULES      330 KBYTES
EACH LICENSED PORT      25 KBYTES PER PORT
EACH CONNECTION         10 TO 175 KBYTES PER CONNECTION

You also need certain Novell and/or third-party supplied NLMs
to run WanderLink.  You may already have these loaded for other
applications; however, if you do not, you should make sure to account
for these modules in estimating your memory requirements.

The following table summarizes these additional required modules:
-----------------------------------------------------------------------
BTRIEVE (VERSION 6.10)  174 KBYTES
AIO     (VERSION 6.01a) 133 KBYTES
AIOCOMX (VERSION 2.12)   19 KBYTES (OR OTHER COMMUNICATIONS DRIVER)
