          Total Control Manager - Accouting Upgrade 5.0
                           -- Release Notes --

===============================================================
Output files (.CON,.RAD.NMC) renamed for year 2000 issues:
===============================================================
Some minor changes were made to the accounting server to 
avoid problems with the year 2000.  Formerly, files would be
created with a YYMMDD name, and then the .CON, .RAD, or .NMC 
extension.  In this version, these files now use four digits
for the year, .i.e., YYYYMMDD.  

In addition, some of the date formats in OUTDEF.DAT now allow
four digits for year specification, rather than two digits.

Tf this change is not desired, the old accounting server is available
as ACCTSERV.OLD.  Rename this to ACCTSERV.EXE to use the old one.
Be aware you may cause year 2000 problems due to the use of two digits
for the year in the old version.


===============================================================
OUTDEF.DAT changed from v4.2, be sure it was uninstalled:
===============================================================

The OUTDEF.DAT file changed format from version v4.2.  When 
running the uninstall from v4.2, the OUTDEF.DAT file can 
sometimes fail to be removed.  The uninstall program will comment
if this happens that some files were not removed, and must be
removed manually.  OUTDEF.DAT must be removed manually if this
happens.  If the file isn't removed, it may not be updated
by the v4.3 or v5.0 installation.

Be sure that the OUTDEF.DAT file from a prior v4.2 file is 
deleted before the install for v4.3 or v5.0 occurs.  Strange data
formatting can occur if this file isn't removed

===============================================================
What to do if the SERVICES file wasn't modified (Win 3.1 Only):   
===============================================================

The automated installation program normally can modify your SERVICES file.
However, sometimes it isn't able to do this.  If the Setup program states
that it was unable or did not modify the SERVICES file, you will need to 
perform the steps below to insure the proper setup for the Accouting server.

TCM's Accounting and Logging capabilities use UDP port 1646, and must also 
be registered.

1. If you already have a TCP/IP SERVICES file, add the following lines to 
   your file:

    radacct  1646/udp

   Then skip to step 3

2. Establish a SERVICES file using SERVICES.SMP (or NET\SERVICES.SMP) as 
   a sample:

   a. Create a directory to hold the TCP configuration files, such as 
      C:\USRSUITE\NET\TCP

   b. Add the following line to your NET.CFG file:

    PATH TCP_CFG    C:\USRSUITE\NET\TCP

   c. Copy SERVICES.SMP to the TCP configuration directory as 
      SERVICES (with no extension).

3. Exit windows and reboot your computer so that your system recognizes the
   new TCP/IP services.


Please refer to your LAN WorkPlace users manual for the format of the 
"SERVICES" file discussed in the sections below.


===============================================================
Using SLIP connections with TCM (Windows 3.1 Only)
===============================================================

If you plan on using SLIP to connect TCM to remote chassis, the following 
steps must be complete to ensure the proper setup:

1. Locate the directory that contains your LSL.COM, SLIP_PPP.COM and 
   TCPIP.EXE files.  If you do not already have these established, use 
   the ones provided by this upgrade.

2. Copy (or rename) one of the following files to NET.CFG:

    SLIP_C1.CFG     - For use with COM1
    SLIP_C2.CFG     - For use with COM2

3. Edit the new NET.CFG to ensure the following lines are correct for 
   your network installation:

   PATH TCP_CFG    c:\net\tcp      <- path containing TCP/IP configuration files
   ip_netmask      ???.???.???.??? <- Your netmask
   ip_address      ???.???.???.??? <- Your IP address

4. Please remove all references to the COM port you are using in the 
   386Enh section of the SYSTEM.INI file by remarking out the 
   following lines.

   [386Enh]

   ;COMxBase=
   ;COMxIrq=
   ;COMxAutoAssign=  


5. Modify your AUTOEXEC.BAT file to load the stacks for proper operation using 
   the commands:

   CD C:\USRSUITE\NET      <- Or your appropriate directory
   LSL
   SLIP_PPP
   TCPIP
   DOSDIALR


===============================================================
Other Useful Information
================================================

- Windows 95 and Windows NT: You must install a TCP/IP stack for this
  product to work.  Microsoft provides a TCP/IP setup option in the 
  Control Panel of both operatiing systems, via the Network applette.
  If you haven't installed the TCP/IP stack, you may see error messages
  concerning winsock's inability to start.

- Windows 3.1 Only: U.S. Robotics management applications are 100% compatable 
  with Novell's WINSOCK.DLL.  The WINSOCK.DLL shipped with other products may 
  be incompatible with the WINSOCK.DLL shipped by U.S. Robotics.  Another 
  WINSOCK.DLL can cause the Accounting Server to fail to locate the SERVICES 
  file.  The Accounting Server then reports the error message: 

    "Could not locate entry for ____ in services file".  

  To correct this problem, be sure that the U.S. Robotics' WINSOCK.DLL 
  is loaded, rather than another WINSOCK.DLL.  One way to do this is to 
  place a WINSOCK.DLL in the directory with the Accounting Server, and to 
  run the Accouting Server before any other application that uses 
  WINSOCK.DLL.

- The accounting sample programs use Microsoft Access to produce sample 
  reports.  One section of each of these samples rely upon Microsoft Graph 
  having been installed as part of the MS Access installation.    If the
  button to display accounting information reports errors, you need to
  run the MS Access setup program and install the MS Graph option.

- For this release, some values in ACCTDICT.DAT and OUTDEF.DAT were 
  renamed to use the '_' character rather than the '-' character.  If
  you retain an OUTDEF.DAT from a prior release, you will need to change
  these values manually.  Start the accounting server with the '-w -d -v'
  to see which values need to be renamed.
