	     Lotus cc:Mail View for Windows Release 1.02


CONTENTS
========
  System Requirements
  Installation
  Status Bar Messages
  Object Information Boxes
  Notification
  Printing
  Reports: Launching
  Reports: Exiting
  Reports: Selecting
  Reports: Printing
  cc:Mail View for Windows Release 1.02 Changes
  Contacting Technical Support
  Appendix: Installing VIM for cc:Mail View

=================================================================

The "cc:Mail View Administrator's Guide" explains how to install
cc:Mail View and how to properly configure your cc:Mail system.
It is an update to a number of topics in Help.  In particular,
Chapter 4, "Configuration," updates the Configuration topic in
cc:Mail View Help.  This README.TXT file contains important, new
information that is not contained in either the manual or online
Help.

System Requirements
-------------------
cc:Mail View runs on Windows 3.1x and Windows for Workgroups
3.1x.  It is certified for Novell 3.1x networks, but should run
on any network that supports the cc:Mail implementation of VIM.

You must be running Router 5.12 or later on every Post Office
in your system that you wish to monitor.

Installation
------------
Shared components.  cc:Mail View contains components that are
  shared with other Lotus applications.  Because cc:Mail View
  may need to update some of those shared components, they
  cannot be in use when the cc:Mail View installer is running.
  Therefore, close any open Lotus applications, including
  SmartCenter, while you are installing cc:Mail View.

Updating AUTOEXEC.BAT.  The installer may ask twice if you want
  your AUTOEXEC.BAT file updated, once for VIM and once for
  SHARE.  These updates are independent.  If the installer
  changes your AUTOEXEC.BAT file, remember to reboot before you
  start cc:Mail View.  Otherwise, the program may not be able to
  find all its executable components.

Windows swap file and 32MB of RAM.  If you have 32MB of memory
  on your Windows machine, you should turn off any permanent or
  temporary Windows swap file.  Failing to do so may result in
  out of memory error conditions when running cc:Mail View or
  Approach, especially if you have other applications running.

ATI Mach32 video boards.  Verify that your Windows video driver
  matches the requirements of your video adapter.  We have found
  that running the 8514/a driver (bundled with Windows)
  occasionally generates system errors when used with ATI
  Graphics Ultra (Mach32) boards.  Use the ATI driver instead of
  the 8514/a driver.

  We have also had reports of problems between After Dark 2.0
  and the ATI Mach32 video card.  The problem appears in
  Approach when displaying some of the cc:Mail View charts.  The
  charting code will first jumble up the chart labels, then fail
  with an error.  Shortly thereafter, After Dark will fail with
  a system error.  We recommend that you not run After Dark with
  cc:Mail View.

SHARE and VSHARE.386.  You must be running SHARE so that cc:Mail
  View and Approach can access the cc:Mail View database
  concurrently.  See the Troubleshooting section in Help for
  more information on database sharing.  If you get an alert box
  that says "Database Error: (-999) Internal error," it is most
  likely because SHARE is not running.  When running Windows in
  Enhanced mode, you may run VSHARE.386 instead.

Status Bar Messages
-------------------
The status bar at the bottom on the application window displays
informative operational messages.  In Super VGA mode, you may
find that the text in parts of the status bar is truncated.
Shift to using smaller fonts.  For example, if you are using the
"8514/a" video driver, switch to using the "8514/a (Small
fonts)" driver.

Object Information Boxes
------------------------
Some of the longer text labels in the dialog boxes may be
truncated on the right.

Notification
------------
You must enable both "Process Statistics Messages" in the Tools
menu and "Enable Notification" in the Notification menu before
cc:Mail View will test and apply notifications.  By default,
"Process Statistics Messages" is on, but "Enable Notification"
is off.

Printing
--------
Changing the default printer inside the cc:Mail View Print Setup
dialog box prevents subsequent printing in that session.

Reports: Launching
------------------
If cc:Mail View cannot locate Approach to run reports (for
example, if Approach is not installed or if you have moved
Approach to a new directory), it displays the following alert:

    No valid application path is available for running reports.
    Please specify the execution path below.

You can enter the appropriate path for your Approach file, or
you can use the Browse button.

Reports: Exiting
----------------
Use the F10 key to exit from a report or a chart.  There is a
small (non-printing) reminder that appears on each report page.

Exiting from a report takes you back to the Main Menu instead of
to the Reports menu.  Exiting from a chart takes you back to the
Main Menu instead of the Charts menu.

Reports: Selecting
------------------
If you make no selections in the Report Options screen, you have
to press Enter twice.

In the Report Options screen for many of the reports and
charts, you may optionally select a specific Post Office.  When
you click in the selector field, the field will be blank.  Use
the up or down arrow key to step through your choices, or use
the Alt+Up or Alt+Down arrow key to see the list.  This bug has
been fixed in a subsequent release of Approach.

In the "Select a Post Office (Optional)" field of the Report
Options, if you choose a Post Office, you will see the name
replaced by a number.  This is normal behavior for the Approach
macro.

In the "Connection Report Options" screen, you can choose to
show data only for Mobile users by selecting "Mobile Users" for
"Select User Type".  This option restricts the data in the
report to Mobile users only.  However, it does not display
additional information about mobile connections that is
available in the database.

Reports: Printing
-----------------
"Print report series" printing may be prematurely interrupted.
If no data is available for a specified report, the batch macro
stops and displays up a dialog box.  To minimize the negative
effect this has (not running your batch mode print job), we have
placed at the end of the sequence the two reports that are most
likely to produce this error, namely, Daily ADE Activity and
Notification Status Messages.

The reporting period for all reports printed through the "Print
report series" option is the last 30 days, including the current
day.  You cannot change this time period.

Printed graphical reports (charts) do not correctly translate
color to make distinguishable black-and- white renditions. 

When printing to a 600dpi PostScript printer, the text in
reports is chopped in half vertically.  This is a known problem
in Approach.  Print using 300dpi mode instead.

cc:Mail View for Windows Release 1.02 Changes
---------------------------------------------
Release 1.02 is primarily a maintenance release.  Most of the
changes are internal, but users will notice the following
differences from Release 1.0.

- The splash screen now displays user registration information.

- Status bar messages are stamped with the current date and
  time and are now written to a log file named STATUS.LOG in the
  cc:Mail View db directory.

- The order of messages in the Status History list is now
  correct with the most recent at the bottom.

- The program now aggressively attempts to recover from VIM
  contention problems (a sign of a very active WAMM mailbox).
  Contention problems are noted in the status bar when they
  occur.  If the program cannot successfully read the mailbox
  after 10 retries, it will quit with a Mail General Failure
  message.

- Information ADE messages are no longer tracked for
  SENT/APPLIED status.  The unapplied message count is not
  incremented or decremented for Info messages.

- The notification for late status messages no longer occurs if
  notification is disabled.

- This release fixes a problem that sometimes caused the program
  to stop reading messages from the WAMM mailbox after it did
  its midnight bookkeeping operations.

- Another bug was fixed that prevented WAMM message processing
  from being turned off after the first complete midnight
  bookkeeping operation.

Contacting Technical Support
----------------------------
For further Technical Support, contact your local sales representative.

Lotus cc:Mail provides additional Support Services as listed below.

Automated Services (for technical information only; not support forums):
    Support Facts (Fax-on-Demand service)  415-966-4951
    Support Services BBS (N81)  415-691-0401

On-Line Services:
    Compuserve (GO LOTUSC)
    Anonymous FTP Server (ftp.ccmail.com)

========================================================================

Appendix: Installing VIM for cc:Mail View

cc:Mail View relies on the cc:Mail implementation of VIM to
access the WAMM mailbox.  The most recent version of VIM for
cc:Mail is part of the cc:Mail View release.  The cc:Mail View
installer will update your VIM files if necessary.

The installer looks for an existing version of VIM by checking
the [cc:Mail] section of your WIN.INI file for a "ProgramPath"
definition.  If the installer finds that variable, then it
checks the associated path for a version of the VIM files.  If
it finds a set and they are older than the set on the cc:Mail
View release disks or if it does not find a file set, then the
installer copies the VIM files from the release disk to that
directory.

The VIM set on the cc:Mail View release disks are considered
newer than an existing VIM set if and only if ANY of the files
in the former have a later version number than the corresponding
file in the latter.

If there is no [cc:Mail] section or ProgramPath variable, or if
the path named by ProgramPath doesn't exist, then the installer
creates a new "VIM" subdirectory in the cc:Mail View home
directory and copies the VIM file set there.

If the installer fails to update the VIM set because the target
directory is read-only or because it is a network path but you
aren't logged on to any network, then it puts the VIM files into
the "VIM" subdirectory of the cc:Mail View home directory.  You
will have to manually update the VIM files.

In all cases, the installer checks if the path that contains VIM
appears in your PATH environment variable.  If not, it will ask
you if you want to have your AUTOEXEC.BAT file updated.

 - If you answer Yes, then the VIM path is added to the
   beginning of the PATH statement in the AUTOEXEC.BAT.  You are
   reminded to reboot your machine.

 - If you answer No, then AUTOEXEC.BAT is not modified, but you
   are reminded to make the modification manually.

Troubleshooting VIM

cc:Mail View may display a VIM error or a "DLL not found" error.
If so, then one of the following may be the cause:

  - Your PATH environment variable does not contain a directory
    with VIM on it.  Add the directory containing VIM to your PATH.

CAUTION!  Avoid copying VIM to the directory containing the
	  CCMVIEW.EXE file as it may cause VIM problems if you
	  upgrade to new versions of VIM or cc:Mail.

  - A directory in your PATH variable contains VIM but it is not
    accessible because you are off the network.

  - You forgot to reboot your machine after cc:Mail View
    modified the PATH statement in your AUTOEXEC.BAT file.

  - Your PATH statement is too long and DOS is truncating it.

  - The files that comprise the VIM set are not matched.  VIM is
    always shipped as a matched set of files.  They cannot be
    mixed between versions.  You should update the entire
    existing VIM set.
  
  - You are running cc:Mail View and a cc:Mail desktop client at
    the same time, but they each use different, mismatched
    versions of the MAILENG.DLL, which is part of VIM.  You
    should make sure that you only have one version of VIM
    installed and that it is the latest version.  If you have
    cc:Mail installed, VIM should be located in the cc:Mail
    program directory, and that directory should be on your
    PATH.

  - If you occasionally receive "General Failure" errors from
    cc:Mail View while it is running, be sure that only one
    program is logged into the WAMM mailbox that you are using.
    This includes any cc:Mail desktop clients, as well as other
    instances of cc:Mail View that may be running on other computers.

Note that Windows searches the following directories in this
order when looking for DLLs (VIM is a set of DLLs):

  - the current directory (cc:Mail View home directory)
  - the Windows directory (usually WINDOWS)
  - the Windows system directory (usually WINDOWS\SYSTEM)
  - the directory containing the executable file for the current
    task (same as the current directory in this case)
  - the directories listed in the PATH environment variable, in
    the order that they appear
  - the list of directories mapped in a network

You may see the following alert just after you start cc:Mail
View:

	The version of VIM is not for cc:Mail. Only
	cc:Mail VIM is supported. New statistic
	messages will not be processed.

The alert indicates that cc:Mail View has found another,
non-cc:Mail version of VIM (for example, Notes VIM).  Check the
order of directories in your PATH to make sure that cc:Mail View
finds a cc:Mail version of VIM.  For example, if you have a
NOTES directory in your path, it should come after any directory
that contains cc:Mail or cc:Mail Mobile executables.

If you have other VIM-related problems, please contact Technical
Support for assistance.
