Notework READ.ME                                   Revision 2-0-2

                        ADDITIONAL NOTEWORK INFORMATION 
                        ===============================
 
This READ.ME file includes information new or unavailable when the
manuals were printed.  It is intended to supplement your Notework
documentation, and help you take advantage of Notework's many
features.  

This disk also includes the latest edition of our Supervisor's Help 
Utility. It contains more information, and newer information, than we put in
our printed manuals. To try it out, run NWHELP from the Notework System 
Directory. The opening screen will describe how to use it, and the ESC
key backs you out.

Running Notework under MS-Windows in Standard Mode
--------------------------------------------------
Notework users who run Notework for MS-Windows in Standard mode on multiple
servers may experience mail delivery problems. We've traced this problem to
a conflict between MS-Windows and a Novell technical library. We use this
library in our Notework for Windows interface and are awaiting an upgrade. 
Until then please note the following:

If you are running under Windows in Standard mode on a single-server Notework
installation, all mail services will work properly.

In a multi-server Notework environment, mail will be sent correctly to 
recipients on the same server as the sender. Mail addressed to users on 
another server will be queued in the MAIL\RP\NWX directory.  This queued mail
can be sent to the proper recipients by running the NWRESEND utility from 
the NOTEWORK system directory. NWRESEND must be run by Supervisor or a user
with equivalent privileges. Simply issue the command \PUBLIC\NOTEWORK\NWRESEND
and all pending mail will be scanned and sent. (If your Notework system
directory is somewhere other than \PUBLIC\NOTEWORK, use the appropriate path.
NWRESEND may not work properly if copied and run from elsewhere.) We suggest
setting up a batch file to run NWRESEND periodically, with the frequency
determined by local needs.

Flash will work properly for recipients on the same server. Flashing users on
another server while running MS-Windows in Standard mode is disabled. 
 
Users running Notework for DOS or Notework for Windows in Enhanced mode are
not affected.

Features in "To Whom?" List
---------------------------
All types of addresses (local to your site, remote via MHS, fax, etc.) can
be intermixed when sending a note. There is an enhancement, called the
Address Book, which can be used to store information such as Title and
Department for all listed users. Users can search for addressees using the
additional columns of data. If a gateway option is installed, it is also
possible to add up to 500 remote users to the Address Book, making them
available to all Notework users. The Address Book is found by selecting
"þ Address Book" from the top of the "To Whom?" list. Users may tag several
names from the Address Book, mixing local users, remote users, groups, and
fax addresses, depending on which options are installed.

After installing certain options, selected users can have the ability to type
in addresses of their choice while others are limited to picking names off a
system-wide address list. If a user's selection is limited to the list, then
the "To Whom?" list will show all the local names. Users who can type in
addresses of their choice will see a different form of the "To Whom?" list,
distinguished by the heading "To Whom? (Recent Addressees)" and by an entry
for "þ Manual Entry" at the top of the list. Under Version 1, this was
called a "Pick List" in the documentation. "Recent Addressees" is meant to
convey the idea that the list has the most-recently-used names on it. The
Address Book is always present for "Recent Addressees" users, so that they
have a way to look up all the local Notework usernames.

Random Lockups and the XSTACK Utility
-------------------------------------
A flaw in Novell's network drivers causes them to overload the DOS
command processor stack.  This can result in lockups of varying
frequency depending on other drivers or TSRs present, and server
traffic volume.

In most machines, the lockup frequency is so low it practically never
occurs.  But adding a TSR can increase the lockup frequency so that
it appears the TSR is causing the lockup.  QEMM-386, in particular,
can trigger lockups in this manner.

XSTACK.COM is a lockup prevention utility which expands the stack in
Novell's NETX.  XSTACK intercepts Interrupt 8 (timer ticks) and switches
to an internal stack while the network drivers run their course.  Lockup
problems can be corrected by loading XSTACK.COM immediately after NETX.COM.
XSTACK will take up 432 bytes and it may be loaded high.

VERIFICATION:
Here is a simple test to determine if your machine needs XSTACK.
Create the following batch file in a scratch directory:

     :LOOP
     SEND "TEST" TO <your name>
     GOTO LOOP

This will repeatedly call the NetWare utility SEND to put a test message
bar at the bottom of your screen.  
Run the batch file. Press <Ctrl-Enter> as fast as you can
to clear the messages as soon as they come up on your screen.  After 
twenty or so, press <Ctrl-Break> to exit the batch file.  If you have a 
stack problem your machine will lock somewhere along the line during the 
experiment.  (Some of the SEND commands will fail because they can detect 
that the previous bar has not yet been cleared.  This indicates that your 
machine or your network is slow, but it is not an indicator of trouble.)

INSTALLATION:
XSTACK should be placed in the affected workstation's AUTOEXEC.BAT 
file, (with the XSTACK.COM file copied to the appropriate boot device).
It should be loaded directly after NETX.


 -End-
