These release notes, last updated December 18th, describe installation issues and known problems in Communicator 4.5. For an overview of the new features provided by Communicator 4.5, see the Tour of New Features. For release notes on Mission Control Desktop tools and technology, see Mission Control Desktop 4.5.

These notes are updated as we receive feedback, so please check back for new information.

Before You Install

General Issues Roaming Access

Mail, Address Books, and Pinpoint Addressing

Navigator International

Windows

Palm-Compatible Synchronization Tools (Windows Only)

Mac OS

Java and JavaScript Unix Installing Digital Unix

This section applies if you are installing Communicator 4.5 on Digital Unix versions prior to 4.0D. If you are running Digital Unix versions prior to 4.0D, you need to install the shared C++ libraries against which Communicator 4.5 was built.

Systems running DIGITAL UNIX Version 4.0D and higher already have  /usr/shlib/libcxx.so, which contains the support needed for DIGITAL C++ Version 6.1, so it's not necessary to install any additional C++ libraries on systems running 4.0D and higher.

Communicator 4.5 was built against C++ shared libraries that you need to install from this location:

ftp://ftp.digital.com/archive/private/netscape/CXXREDIST600V01.tar
If you don't install the C++ shared libraries before installing Communicator 4.5, errors of this kind will appear during Communicator installation: To install the C++ shared libraries:
1. Check which CXX subsets are installed:
For Digital Unix versions prior to V4.0D, the libcxx subset and the redistribution subset both install /usr/lib/cmplrs/cxx/libcxx.so to avoid overwriting the version of libcxx.so installed by the operating system (/usr/shlib/libcxx.so). When linking, the compiler pass -rpath /usr/lib/cmplrs/cxx -L/usr/lib/cmplrs/cxx to ld. This causes ld to search /usr/lib/cmplrs/cxx before searching the system libraries, and the loader to search for libraries in that directory when loading code for execution. If you specify -rpath explicitly, you need to make sure to specify /usr/lib/cmplrs/cxx in the path string in addition to any other directories that you want searched.
 

Using the Quality Feedback Agent with Automatic Proxy Configuration

If you are using automatic proxy configuration, and you want to use the Full Circle Talkback Quality Feedback Agent to send incident reports to Netscape, you need to replace the talkback.ini file with one that contains the appropriate proxy configuration information:
1.  If you are using an HTTP proxy, or both an HTTP and SOCKS proxy, create a file named talkback.ini, containing  these three lines, using your proxy host name, domain, and port:
UseUserHTTPProxyInfo=1
UserHTTPProxyHost="yourproxy.yourdomain.com" UserHTTPProxyPort=xxxx
   If you are using a SOCKS Proxy, create a file with these three lines:
UseUserSOCKSInfo=1
UserSOCKSHost="yourproxy.yourdomain.com"
UserSOCKSPort=xxxx