*******************************************************
   NetWare Telephony Services
   v1.1.a 5/2/94
   Release Notes and Network Manager's Guide Errata
******************************************************

*******************
   Release Notes
*******************

4.01a NETWARE:

   *** IMPORTANT **** IMPORTANT **** IMPORTANT **** IMPORTANT ***
   If you are using version 4.01a of NetWare, you must download
   UPD3XX.EXE (XX is a version number) from CompuServe to obtain
   Telephony Services password checking. UPD3XX.EXE is an updater
   for 4.01a that permanently fixes problems in NetWare as opposed
   to "patch" NLMs that need to be loaded every time the server runs.
   
   If you are using 4.01b or later you need not perform this operation.

COMPRESSED CLIENT SOFTWARE:

   Many of the files on the client disk have been compressed. When
   these files are copied to your server during server installation,
   they remain compressed. You cannot run telephony services directly
   from these files.
   
   If you wish to install the windows workstation software on your server
   in an executable form, you must run the windows workstation setup and
   designate a server directory as the installation destination.

   1. Select "Advanced" from the "Install Options" dialog box.
   
   2. Change the "Path" field to the server directory in which you wish
      to install the workstation software.

   3. Select "OK".
   
   You may follow the same procedure from the next dialog box which asks,
   "Do you wish to install Telephony Services Administrator?" if you wish
   to copy the Administration software to the server.

UPGRADING FROM PREVIOUS VERSIONS OF TELEPHONY SERVICES:
   You must reinstall all Telephony Services components using 
   the installers on the new disks. For best results, opt for a 
   "Complete Installation" in the NetWare installer.

NOTE: Unless you delete the security database, the installer will
      never replace it with a new copy.
   
   Delete the TSRVRSRC.DTA file in each SYS:\SYSTEM\TSRV\SDB
   directory before installing. This allows the Telephony Server to
   increase the number of network resources it reserves for itself.

INSTALLATION:
   There are several important changes to installing and loading
   Telephony Services software. You should read all errata below
   concering Chapter 4, Installation before attempting installation.

SECURITY DATABASE:
   When migrating a Security Database from one server to another,
   do not copy TSRVRSRC.DTA. This file does not contain security
   database information, rather, it contains resource information
   about registered drivers.

   In addition, TSRVINFO.DTA contains preferences such as the
   High Water Mark, Error Log settings and "Restrict Users to Home
   Worktop" setting. You may copy this file by itself if you wish
   to copy these settings from one server to another.

   If you copy any of the security database from one server to
   another, you must copy the entire set of database files:

       INDICES.DTA
       USER.DTA
       WORKTOP.DTA
       DLIST.DTA
       DLISTNM.DTA
       DEVICES.DTA
       TLIST.DTA
       TSERVERS.DTA
       TLISTNM.DTA

	None of these files may be copied individually.

************
   ERRATA
***********

Format:

----....                 divider
Chapter XX _ Title       chapter
pg. 1                    pages affected

<START>                  Beginning of affected text
 ...                     AFFECTED TEXT
<FINISH>                 End of affected text

text...          	 description of correction

----------------------------------------------------------------------
Chapter 4 _ Installation
pg. 36

<START>

   NOTE: Do not rely on the installer's assessment of whether
         any windows components are newer or older than copies
         that may exist on your server.

         ...

         Before the installer replaces windows components that it
         finds on your server, it compares the source file's date
         with the destination date (to be replaced). This is how
         the installer determines whether windows components need
         to be replaced or not.

<FINISH>

The NetWare installer no longer changes the dates of files as it
copies them from source diskette to server. Even so, the second
paragraph above is still true; the installer uses file dates to decide
whether a Windows component on diskette is newer, older or the same
version as the same component on your server. As long as the files on
your server retain their original dates, the NetWare installer will
accurately determine whether or not to replace ALL files.

NOTE: The windows workstation software changes the dates of files that
      it copies to the workstation. This will not affect the original
      files, only the copies.

----------------------------------------------------------------------
Chapter 4 _ Installation
pp. 38-39

<START>

   File Commit

     Telephony Services Adminstrator performance may be very slow
     when administering files that reside on servers with the ncp
     file commit option turned on. You must turn this setting off
     on servers running NetWare 3.12 or 4.

<FINISH>

Telephony Services comes with a NetWare patch - MMACCFIX.NLM - that
fixes this problem WITHOUT requiring you to SET NCP FILE COMMIT = OFF.
This patch is automatically installed by the NetWare Telephony Services
installer.

----------------------------------------------------------------------
Chapter 4 _ Installation
pg. 43

<START>

   3. Use the Telephony Services installer to do a custom installation,
      and only install

<FINISH>

The steps required for creating an empty (new) security database are
incomplete. Change step 3 to the following:

   3. Use the Telephony Services installer to do a custom installation,
      and install all of the Telephony Server database files (.DTA).

----------------------------------------------------------------------
Chapter 4 _ Installation
pp. 47-49

<START>

   (These pages describe loading the Telephony Server and support
   components into server memory automatically and at the console
   command line.)

<FINISH>

Replace pages 47-49 in their entirety with the text below:

<START>

I N V O K I N G   T H E   T E L E P H O N Y   S E R V E R

LOADING AUTOMATICALLY

1. Edit your file server's AUTOEXEC.NCF file

   Place the following commands into your server's AUTOEXEC.NCF file.
   After doing so, type them at the console to load the Telephony
   Server without restarting. You need never type these commands
   again; they will be executed automatically every time your server
   starts up.

   1a. Add BSTART.

       Place the BSTART command immediately after the FILE SERVER NAME
	   and IPX INTERNAL NET directives (these should occur at the
	   beginning of the AUTOEXEC.NCF file). This should make BSTART the
	   third command in the AUTOEXEC.NCF file.

   1b. Add TSTART.

       Place the TSTART command anywhere after BSTART. TSTART.NCF
	   contains commands used for starting Telephony Services (but
	   not TSLIB for NetWare).

   1c. (optional) Load TSLIB for NetWare.

	   If you have applications that use TLIB for NetWare, you must
	   also add the following line to your AUTOEXEC.NCF file and
	   subsequently type it at the console:

	   LOAD TSLIB

EXAMPLE AUTOEXEC.NCF FILE

   Before installing Telephony Services, a server with an NE2000 LAN
   card might have an AUTOEXEC.NCF file such as this:
   

   FILE SERVER NAME TSRV
   IPX INTERNAL NETWORK A386
   # ADD THE BSTART DIRECTIVE
   BSTART
   
   # SET MAXIMUM ALLOC SHORT TERM MEMORY (NOT FILE COMMIT)
   SET MAXIMUM ALLOC SHORT TERM MEMORY=3500000
 
   LOAD NE2000 PORT=360 IRQ=5 FRAME=ETHERNET_802.3
   BIND IPX TO NE2000 NET=10
   LOAD MONITOR
   LOAD INSTALL
   
   # LOAD SUPPLEMENTAL PATCHES AND TELEPHONY SERVER
   TSTART
  
LOADING FROM THE CONSOLE

1. Load Btrieve by typing

   BSTART <Enter>

   If you see "This module is ALREADY loaded and cannot be loaded
   more than once" appear, you must unload any NLMs using Btrieve
   already, type "BSTOP" and press <Enter>. Then, load Btrive by
   typing "BSTART" and pressing <Enter>.

2. Start Telephony Services by typing

   TSTART <Enter>

3. Load Telephony Services drivers.

   Refer to your PBX vendors' manuals for instructions on how to load
   TSDRV modules into memory.

4. (optional) Load TSLIB for NetWare.

   If you have applications that use the NetWare version of TSLIB, you
   must load it into memory by typing

   LOAD TSLIB <Enter>

<FINISH>

----------------------------------------------------------------------
Chapter 7 _ How to Use the Tserver Administrator Client Application
pg. 86

<START>

2.   Double click on the "Tservices Admin" icon to execute the
     Tserver Administrator application.  The "Available Tservers

<FINISH>

The rest of the procedure is cut-off.  The complete item 2 should read:

2.   Double click on the "Tservices Admin" icon to execute the
     Tserver Administrator application.  The "Available Tservers"
     dialog box is displayed.  This dialog box lists all servers
     the user is currently attached to that have Tservers running
     on them.  Choose the server which contains the Tserver you
     want to administer.

----------------------------------------------------------------------
Chapter 7 _ How to Use the Tserver Administrator Client Application
pg. 110-112

<START>

2.   Choose "Delete" on the "Device Information" dialog box.
     The Device information for the previously selected device is
     displayed.

<FINISH>

The information from Step 4 beginning with

     If either a user or a worktop is associated with this device, the system
     will not allow you to delete the device...

at the top of page 111 through and including step 6 at the top of page 112 is
all a part of step 2.  Step 2 should read:

2.   Choose "Delete" on the "Device Information" dialog box.
     The device information for the previously selected device is
     displayed unless either a user or a worktop is associated with
     this device.  If either a user or a worktop is associated with
     this device, the system will not allow you to delete the device...

Step 5 should be step 2a.

Step 6 should be step 2b.

----------------------------------------------------------------------
Chapter 7 _ How to Use the Tserver Administrator Client Application
pg. 113

<START>

3.   Choose "OK" to record the addition of the Device Group in
     the Security Database, or choose "Cancel" to return to the
     "Device Group Information" dialog box without recording
     the addition you specified on the screen in the Security
     Database.

<FINISH>

Change Step 3 and add:

3.   Choose "OK" to display the "Create Device Group <NAME>" dialog
     box, or choose "Cancel" to return to the "Device Group Information"
     dialog box.

Follow the steps for "Editing a Device Group" on pages 113-115, including the
errata described below.

----------------------------------------------------------------------
Chapter 7 _ How to Use the Tserver Administrator Client Application
pg. 115

<START>

3.   Choose "Add" to move the selected devices from "Devices
     Not Currently in Group" to "Devices In Group."

<FINISH>

Add 2 new steps after step 3.  The existing step 3 is correct.  The
existing steps 4 and 5 are correct, but should be steps 6 and 7.  The
new steps 4 and 5 are:

4.   From the available choices list in the "Devices In Group" box,
     select one or more devices that you want to delete from the
     previously selected Device Group.

5.   Choose "Delete" to move the selected devices from "Devices
     in Group" to "Devices Not Currently in Group."

----------------------------------------------------------------------
Chapter 7 _ How to Use the Tserver Administrator Client Application
pg. 128

<START>

4.   If this user is to be administered for "Classes of Service,"
     continue with Step 5.  Otherwise, go to Step 7.

<FINISH>

Step 7 should be replaced with Step 9:

4.   If this user is to be administered for "Classes of Service,"
     continue with Step 5.  Otherwise, go to Step 9.

----------------------------------------------------------------------
Chapter 7 _ How to Use the Tserver Administrator Client Application
pg. 163-170

<START>

TSDRV Resources

<FINISH>

This is a Maint menu item, but is described under the Status menu.

