Last updated: July 18, 2000 [These notes are updated as we receive feedback, so please check back for new information.]

These release notes describe installation issues and known problems in Communicator 4.74.
Contents include:

For release notes on Mission Control Desktop tools and technology, see Mission Control Desktop.

**Notice to Calendar Users**

*As of version 4.72 of Netscape Communicator, the Netscape Calendar client will no longer be included in the installation package, but will be available from enterprise.netscape.com. Please visit http://enterprise.netscape.com/index.html for more information on how to download and install the standalone Calendar client for use with Communicator 4.72.

What's New in This Release (4.74)

Changes Since 4.5

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/Linux
  • Solaris 2.6 only: Solaris 2.6/OpenWindows Communicator 4.0x does not render fonts properly. OpenWindows 3.6 patch 105633-05 fixes this problem, and is available from http://sunsolve.sun.com. Alternatively, you can add the following lines to your $HOME/.xinitrc file:

  • xset +fp /usr/openwin/lib/X11/fonts/75dpi/
    xset fp rehash
    CDE users on 2.6 will need to add the first of the two lines above to their HOME/.dt/sessions/session etc (be sure the permissions on this file are 755). Exit Communicator and then restart.

    Using the Quality Feedback Agent with Automatic Proxy Configuration

    (Note: This is available for Windows only.) 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 [your proxy port number]
    If you are using a SOCKS Proxy, create a file with these three lines:
    UseUserSOCKSInfo=1
    UserSOCKSHost="yourproxy.yourdomain.com"
    UserSOCKSPort=xxxx [your SOCKS port number]