                  Release Notes for
          McAfee(R) ePolicy Orchestrator(R)
               Version 3.0.2a Patch 7
           Copyright (C) 2004 McAfee, Inc.
                 All Rights Reserved

==========================================================
This Patch is build number:
3.0.2.298.

This release was developed and tested with:

- ePolicy Orchestrator: 3.0.2a

Make sure you have installed this version before
using this release.

    IMPORTANT:
    IN ADDITION TO APPLYING THIS PATCH TO THE
    ePOLICY ORCHESTRATOR SERVER, BE SURE TO APPLY
    THIS PATCH TO ALL REMOTE CONSOLE MACHINES AS
    WELL. USING A REMOTE CONSOLE WITH A VERSION THAT
    IS DIFFERENT FROM THE ePOLICY ORCHESTRATOR
    SERVER WILL HAVE UNKNOWN RESULTS.

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


Thank you for using ePolicy Orchestrator(R)
software. This file contains important information
regarding this release. We strongly recommend that
you read the entire document.

The attached files are provided as is, and with no
warranty either expressed or implied as to their
suitability for any particular use or purpose.
McAfee, Inc. assumes no liability for damages
incurred either directly or indirectly as a result
of the use of these files, including but not limited
to the loss or damage of data or systems, loss of
business or revenue, or incidental damages arising
from their use. Patch files should be applied only
on the advice of McAfee Technical Support, and only 
when you are actually experiencing the issue being 
addressed by the Patch. Patch files should not 
be proactively applied in order to prevent potential 
product issues. You are responsible for reading and 
following all instructions for preparation, configuration, 
and installation of Patch files. Patch files are not a
substitute or replacement for product Service Packs
which may be released by McAfee, Inc. It is a
violation of your software license agreement to
distribute or share these files with any other
person or entity without written permission from
McAfee, Inc. Further, posting of McAfee
Patch files to publicly available Internet sites is
prohibited. McAfee, Inc. reserves the right to
refuse distribution of Patch files to any company or
person guilty of unlawful distribution of McAfee
software products. Questions or issues with McAfee
Patch files should be directed to McAfee Technical
Support.



__________________________________________________________
WHAT'S IN THIS FILE

-   About This Release
   -   Purpose
   -   Resolved Issues
   -   Previously Resolved Issues
-   Installation
   -   Installation Requirements
   -   Installation Steps
   -   Removing This Release
-   Contact Information
-   Copyright And Trademark Attributions
-   License and Patent Information
   -   License Agreement
   -   License Attributions
   -   Patent Information


__________________________________________________________
ABOUT THIS RELEASE

*************************
* IMPORTANT INFORMATION *
*************************

Installing this Patch is required on both ePolicy
Orchestrator servers and any ePolicy Orchestrator
remote consoles to maintain full functionality.
Please be sure to patch both server and console
machines with this release.

PURPOSE

This Patch replaces server files in ePolicy
Orchestrator to resolve the issues listed below.


RESOLVED ISSUES

1.  ISSUE:
    In certain circumstances, a SITELIST.XML with
    incorrect information is created and pushed to
    clients, resulting in agents not being able to
    communicate to the ePolicy Orchestrator server.

    RESOLUTION:
    This issue was originally fixed in a previous
    Patch.  This Patch addresses another issue in a
    different code path that could cause the same
    result.

2.  ISSUE:
    In certain cases, there is a problem in the
    caching of server tasks that could cause
    NAIMSERV to crash.

    RESOLUTION:
    Improvements have been made in the way caching
    of server tasks is handled to avoid causing the
    crash.

3.  ISSUE:
    Incoming events to the ePolicy Orchestrator
    server may be processed slowly when under a
    large load.

    RESOLUTION:
    Improvements have been made to improve event
    processing performance.

4.  ISSUE:
    If an ePO user name includes a space in the
    name, that user name cannot be used to log onto
    ePolicy Orchestrator.

    RESOLUTION:
    This issue was introduced in another fix from
    ePolicy Orchestrator 3.0.2a Patch 4, and was
    caused by incorrect parsing of the HTTP header
    when looking for the authentication header. If
    the name included a space, only a portion of the
    name was returned. The user name information is
    now parsed correctly.

5.  ISSUE:
    If you are running the Small Business licensed
    version of ePolicy Orchestrator 3.0.2a, the
    Patch 6 installation fails and subsequently you
    cannot check in software packages.

    RESOLUTION:
    This issue has been identified and resolved so
    that Patch 7 and newer releases can be installed
    on Small Business licensed versions of ePolicy
    Orchestrator, and software packages can be
    checked in.

6.  ISSUE:
    When performing a DAT pull, "SPAM" filtering
    packages were downloaded into the repository
    whether or not SpamKiller is used in the
    environment.

    RESOLUTION:
    "SPAM" filtering packages are now downloaded
    only if SpamKiller is used in the current
    environment. This functionality requires this
    Patch; without it, the SpamKiller packages will
    still be downloaded.


PREVIOUSLY RESOLVED ISSUES

1.  ISSUE:
    On rare occasions, when using the local or
    remote console and System Compliance Profiler is
    checked into the master repository, no
    deployment task for System Compliance Profiler
    appears.

    RESOLUTION:
    This issue was caused by invalid entries in the
    database for System Compliance Profiler. The
    invalid entries have been corrected.

2.  ISSUE:
    In certain cases, individual System Compliance
    Profiler reports were not visible in the
    console. Only the high-level name "System
    Compliance Profiler" was shown in the reporting
    tree.

    RESOLUTION:
    The console was looking in the incorrect
    location for the System Compliance Profiler
    reports. The console now looks in the correct
    location for these reports.

3.  ISSUE:
    In rare cases after a successful repository
    replication, some files in the operating system
    folder were deleted.

    RESOLUTION:
    On certain versions of Microsoft Windows NT
    operating system, if a temporary variable was
    not set, it was reported to ePolicy Orchestrator
    that the temporary directory was the Operating
    System folder. This resulted in the cleanup
    after a successful repository replication, where
    extra files were deleted. ePolicy Orchestrator
    no longer removes files from invalid temporary
    directories that were passed to it by the
    operating system.

4.  ISSUE:
    When importing an agent policy from a
    SuperAgent, the SuperAgent repository was not
    listed as a repository.

    RESOLUTION:
    This issue was caused by incorrect notification
    during the policy import procedure, which
    triggered the SuperAgent to be added as a
    repository. Now the agent policy import
    correctly adds the SuperAgent as a repository.

5.  ISSUE:
    In some cases, certain NAP files could not be
    checked into the master repository, and
    replications to distributed repositories stopped
    working.

    RESOLUTION:
    This issue was caused by ePolicy Orchestrator
    incorrectly handling products whose product
    package included the product NAP file. The
    ePolicy Orchestrator software now handles all
    NAP files found in the master repository as part
    of the product package.

6.  ISSUE:
    In certain environments it was necessary for the
    SQL Server Service to be stopped for correct
    ePolicy Orchestrator server operation, with the
    following error messages placed in the
    SERVER.log.

    ENAIMSERV Connection cleared successfully.
    IDAL About the attempt to connect to database
    EDAL COM Error :80004005 in OpenConx
    EDAL Meaning = Unspecified error
    EDAL Source = Microsoft OLE DB Provider for SQL

    RESOLUTION:
    Reconstructing the SQL database connections for
    various ePolicy Orchestrator database
    transactions could cause this issue. The ePolicy
    Orchestrator software no longer has this issue.

7.  ISSUE:
    On occasion, distributed and SuperAgent
    repositories containing an EXTRA.DAT file would
    not replicate the latest version of the
    EXTRA.DAT file from the master repository.

    RESOLUTION:
    This issue was caused by incorrectly determining
    that the EXTRA.DAT file in the distributed
    repositories was a newer version. The EXTRA.DAT
    file in the master repository is now correctly
    identified as the newer version.

8.  ISSUE:
    When using the local or remote console to
    configure uninstall command-line parameters in
    the deployment task settings for any product,
    the command-line parameters are not stored.

    RESOLUTION:
    This issue was caused by incorrectly storing the
    uninstall command-line parameters. They are now
    stored correctly.

9.  ISSUE:
    If you configured an FTP replication task to use
    anonymous login and you used the local or remote
    console to do this, if you edited the
    replication task the user name was blank.

    RESOLUTION:
    This issue was caused by the user interface
    storing --but incorrectly displaying -- the user
    login. The user login is now shown correctly.

10. ISSUE:
    Under certain circumstances, when using the
    local or remote console to perform the task
    "Sort Computers by IP", after you accept the
    value in the wizard, the console closes.

    RESOLUTION:
    This issue was caused by incorrectly handling
    the data in the IP address properties. Now the
    data in the IP address properties are handled
    correctly.

11. ISSUE:
    When using the local or remote console to run
    the "Product Events by Severity" report, the
    legend list may show a number instead of the
    correct text replacement.

    RESOLUTION:
    In certain cases, the report was defaulting to a
    number instead of getting the correct text
    replacement. This report now retrieves the
    correct text replacement.

12. ISSUE:
    In rare cases, agents could not communicate to
    the ePolicy Orchestrator server due to the
    server passing the agents a SITELIST.XML file
    that erased the server IP address or the
    communication port, or both.

    RESOLUTION:
    This was caused by the ePolicy Orchestrator
    server attempting to generate a new SITELIST.XML
    file when the SITEINFO.INI file was in use by
    other server processes. The ePolicy Orchestrator
    server only generates a new SITELIST.XML when
    SITEINFO.INI is not in use by other server
    processes.

13. ISSUE:
    Under certain circumstances, when using the
    local or remote console running coverage
    reports, "NO DATA FOUND" appears in the report.

    RESOLUTION:
    The branch node tables included orphaned
    entries. These orphaned entries are now removed
    to allow the coverage reports to run correctly.

14. ISSUE:
    When using the local or remote console with ePO
    authentication to log into reporting, the
    following error may occur, avimsnap pop-up
    error:

    "Subquery returned more than one value. This is
    not permitted when the subquery follows =, !=,
    <, <=, >, >= or when the subquery is used as an
    expression. The statement has been terminated."

    RESOLUTION:
    A stored procedure was unable to handle
    duplicate entries in the ReportVersionClient
    table. The stored procedure now handles
    duplicate entries correctly.

15. ISSUE:
    Under certain conditions, NAIMSERV.EXE had
    instability issues, which resulted in an access
    violation error that could cause the server to
    crash.

    RESOLUTION:
    NAIMSERV.EXE has been modified and will no
    longer crash in these cases.

16. ISSUE:
    When using an FTP repository on a Microsoft
    Windows 2003 Server running Microsoft IIS
    version 6.0 FTP services, and the banner started
    with four or more blank spaces, replication
    would fail due to a login failure.

    RESOLUTION:
    The four or more extra spaces were processed as
    an FTP status code. The ePolicy Orchestrator
    software now correctly determines FTP status
    codes.

17. ISSUE:
    When using localized clients to view disk space
    and free disk space in the system section on the
    Properties tab in the console, an incorrect
    value would be shown instead of the true disk
    space and free disk space.

    RESOLUTION:
    The ePolicy Orchestrator server was not
    correctly parsing the localized language number
    separators. The server now correctly parses the
    number separators.


18. ISSUE:
    After checking in the McAfee GroupShield 6.0 NAP
    file to the repository, then using the console
    to administer the McAfee GroupShield 6.0
    product, the console would become
    non-responsive.

    RESOLUTION:
    When the McAfee GroupShield 6.0 NAP file was
    checked into the repository, Java Runtime
    Environment (JRE) version 1.4.1 was installed.
    The JRE 1.4.1 version experienced compatibility
    problems with ePolicy Orchestrator. The ePolicy
    Orchestrator software is now compatible with
    version 1.4.1 of JRE.

19. ISSUE:
    McAfee ePolicy Orchestrator may stop replicating
    to repositories and may display the error "DAL
    ePO 3.0 DAL exit" in the SITEMGR.LOG.

    RESOLUTION:
    This issue stemmed from two causes:

   -   NAREPL32.EXE used default DCOM permissions to
       operate correctly. If default DCOM
       permissions were altered, NAREPL32.EXE would
       not function correctly. NAREPL32.EXE is now
       registered with explicit DCOM permissions.

   -   The state in SITEMGR.INI set the task status
       to a value that resulted in replication tasks
       freezing when they were scheduled too close
       together, which caused the running task to be
       terminated by the scheduler without resetting
       the status in the SITEMGR.INI file. This
       would cause future tasks not to run. This
       issue no longer occurs.

20. ISSUE:
    When replicating to repositories using ePolicy
    Orchestrator, replications may fail with the
    message "Error occurred while verifying file
    delta.ini" placed in the SITEMGR.LOG.

    RESOLUTION:
    On rare occasions, when repositories were being
    replicated, it was possible that extra
    characters were appended to the end of the files
    in the repository. Repository replication no
    longer appends extra characters to the end of
    files in the repositories.

21. ISSUE:
    The DAT version for Norton Antivirus was not
    being reported correctly to ePolicy
    Orchestrator; this resulted in incorrect
    properties and reports.

    RESOLUTION:
    This Patch places a new NAP file and plug-in for
    Norton Antivirus in the repository that now
    correctly formats the DAT version from the
    Norton Antivirus products.

22. ISSUE:
    This release addresses the ePolicy Orchestrator
    Remote Command Execution Vulnerability;
    vulnerability identifier:  CAN-2004-0038.

    RESOLUTION:
    This vulnerability no longer exists.

23. ISSUE:
    When the ePolicy Orchestrator server is busy,
    the remote console login process may be slow.

    RESOLUTION:
    The console login and package check-in have been
    changed so that they now process synchronously.

24. ISSUE:
    In certain low bandwidth environments, the
    ePolicy Orchestrator server did not process
    socket I/O optimally, causing the HTTP
    connections to reach the limit specified in the
    server settings and start rejecting any
    additional connections.

    RESOLUTION:
    The ePolicy Orchestrator server now handles all
    socket I/O in blocking mode. Now when agent
    connections come to the server, the worker
    thread picks up the connection and waits on read
    or write operations for 15 seconds. If data
    doesn't come in during that period, the server
    puts the socket back in the work queue and the
    worker thread processes the next request.

    ADDITIONAL INFORMATION:
    There are now four new performance counters for
    tracking socket read and write time-outs.

    The following new performance counters have been
    added:

    -   Number of socket read watches
    -   Number of socket read time-outs
    -   Number of sockets write watches
    -   Number of sockets write time-outs

25. ISSUE:
    The time-out connection logic sometimes caused
    the HTTP connections to build up over extended
    periods of time.

    RESOLUTION:
    Now, if a value is defined for
    "ConnectionTimeout=" in SERVER.INI, the time-out
    for inactive sockets uses this figure.
    Otherwise, 15 minutes is the time-out value.

    ADDITIONAL INFORMATION:
    To specify a connection time-out in SERVER.INI,
    do the following:

   1.  In a text editor, open SERVER.INI. This file
       is located in the DB folder in the
       installation directory. The default
       installation directory is:

       C:\PROGRAM FILES\NETWORK ASSOCIATES\EPO\3.0.1

   2.  Type the following line in SERVER.INI, then
       save the file:

       ConnectionTimeout=NNN

       Where NNN equals the number of seconds. For
       example, ConnectionTimeout=900

   3.  In the "Service" dialog box, select the
       "McAfee ePolicy Orchestrator 3.0.1 Server"
       service, click "Stop," then click "Start" to
       restart the service.


26. ISSUE:
    Replication tasks using FTP would result in
    partial or incomplete replications.

    RESOLUTION:
    Changes to the FTP communication subsystems make
    them more reliable and fault tolerant in a
    variety of environments.

27. ISSUE:
    A limitation on the number of sites within the
    directory tree caused the console to close when
    someone clicked "Create user" or "Modify user."

    RESOLUTION:
    There is no longer a limit on the number of
    sites in the directory tree.

28. ISSUE:
    A duplicate path delimiter was being added
    during the generation of all agent file paths,
    which caused an entry in the sitemgr.log, such
    as "Failed to verify file size for agent.ini".

    RESOLUTION:
    The agent file paths are generated correctly.

__________________________________________________________
INSTALLATION

INSTALLATION REQUIREMENTS

To use this release, you must have ePolicy
Orchestrator 3.0 and Service Pack 2a software
installed on the computer you intend to update with
this release.

    NOTE:
    This release does not work with earlier versions
    of ePolicy Orchestrator software.


INSTALLATION STEPS

1.  Create a temporary folder on the hard drive of
    the ePolicy Orchestrator server.

2.  Extract the EPO3027.ZIP file to the temporary
    folder that you created in Step 1.

    WARNING:
    Close the Windows Services dialog box to avoid
    installation issues.

3.  Back up ePolicy Orchestrator databases.

    If you are using Microsoft SQL Server as the
    ePolicy Orchestrator database, see the SQL
    Server product documentation.

    If you are using Microsoft Data Engine (MSDE) as
    the ePolicy Orchestrator database, you can use
    the Database Backup Utility (DBBAK.EXE) to back
    up ePolicy Orchestrator MSDE databases on the
    database server. For instructions, see "Backing
    up ePolicy Orchestrator MSDE databases" in the
    ePolicy Orchestrator 3.0 Product Guide.

4.  Log on to the desired computer using a user
    account with local administrator permissions.

5.  Close all ePolicy Orchestrator consoles.

6.  On the taskbar, click the "Start" button, then
    select "Run" from the start menu. The "Run"
    dialog box appears.

7.  In "Open," type the path where the Setup program
    (SETUP.EXE) is located, then click "OK." The
    "ePolicy Orchestrator 3.0.2 Patch 7 Setup"
    wizard appears.

8.  Click "Next" to begin the installation.

9.  Click "Finish" to complete the installation.

10. In the "Services" dialog box, select the "McAfee
    ePolicy Orchestrator 3.0.2 Server" service and
    edit the service to change the account back to
    the original setting. For example, if you
    specified a domain administrator account during
    the initial installation, you need to provide
    that account information again. The account is
    not automatically restored.

11. For all remote consoles, perform Steps 4  9.

12. For customers affected by Previously Resolved
    Issue number 1, do not remove System Compliance
    Profiler. Re-install the System Compliance
    Profiler files as if you were installing for the
    first time. Your System Compliance Profiler
    rules and tasks will not be lost by
    re-installing.


REMOVING THIS RELEASE

To remove this Patch from your computer, uninstall,
and then reinstall ePolicy Orchestrator.

    NOTE:
    We recommend that you do NOT remove the Patch
    files once you install them. If you reinstall
    the ePolicy Orchestrator software, we recommend
    that you also reinstall the Patch.


__________________________________________________________
CONTACT INFORMATION

Technical Support
    Home Page
       http://www.mcafeesecurity.com/us/support/technical_support

    KnowledgeBase Search
       https://knowledgemap.mcafeesecurity.com/phpclient/homepage.aspx

    PrimeSupport Service Portal
       https://mysupport.mcafeesecurity.com

    Login credentials required.


McAfee Beta Program
    Beta Web Site
       http://www.mcafeesecurity.com/us/downloads/beta/mcafeebetahome.htm

    E-mail
       avbeta@mcafee.com


Security Headquarters -- AVERT (Anti-Virus &
Vulnerability Emergency Response Team)
    Home Page
       http://www.mcafeesecurity.com/us/security/home.asp

    Virus Information Library
       http://vil.nai.com

    AVERT WebImmune - Submit a Virus Sample
       https://www.webimmune.net/default.asp

    AVERT DAT Notification Service
       http://vil.mcafeesecurity.com/vil/join-DAT-list.asp


Download Site
    Home Page
       http://www.mcafeesecurity.com/us/downloads/

    DAT File and Engine Updates
       http://www.mcafeesecurity.com/us/downloads/updates/default.asp

       ftp://ftp.mcafeesecurity.com/pub/antivirus/datfiles/4.x

    Product Upgrades
       https://secure.nai.com/us/forms/downloads/upgrades/login.asp

    Valid grant number required.
    Contact Customer Service


Training
    On-Site Training
       http://www.mcafeesecurity.com/us/services/security/home.htm
    McAfee University
       http://www.mcafeesecurity.com/us/services/education/mcafee/university.htm


Customer Service
    US, Canada, and Latin America toll-free:
   Phone:     +1-888-VIRUS NO or +1-888-847-8766
              Monday - Friday, 8 a.m. - 8 p.m.,
              Central Time

   E-mail:    https://secure.mcafeesecurity.com/us/forms/support/request_form.asp

   Web:       http://www.mcafee.com/us/default.asp
              http://www.mcafeesecurity.com/us/support/default.asp

For additional contact information  including
addresses and toll-free numbers for worldwide
offices - see the CONTACT file that accompanied your
original product release.


_____________________________________________________
COPYRIGHT AND TRADEMARK ATTRIBUTIONS

Copyright (C) 2004 Networks Associates Technology,
Inc. All Rights Reserved. No part of this
publication may be reproduced, transmitted,
transcribed, stored in a retrieval system, or
translated into any language in any form orbyany
means without the written permission of Networks
Associates Technology, Inc., or its suppliers or
affiliate companies. To obtain this permission,
write to the attention of the McAfee legal 
department at:
5000 Headquarters Drive, Plano, Texas 75024, or call
+1-972-963-8000.


TRADEMARKS

Active Firewall, Active Security, ActiveSecurity
(and in Katakana), ActiveShield, AntiVirus Anyware
and design, Clean-Up, Design (Stylized E), Design
(Stylized N), Entercept, Enterprise SecureCast,
Enterprise SecureCast (and in Katakana), ePolicy
Orchestrator,  First Aid, ForceField, GMT,
GroupShield, GroupShield (and in Katakana), Guard
Dog,  HomeGuard, Hunter, IntruShield, Intrusion
Prevention Through Innovation, M and Design, McAfee,
McAfee (and in Katakana), McAfee and Design,
McAfee.com, McAfee VirusScan, NA Network Associates,
Net Tools, Net Tools (and in Katakana), NetCrypto,
NetOctopus, NetScan, NetShield, Network Associates,
Network Associates Colliseum, NetXray, NotesGuard,
Nuts & Bolts, Oil Change, PC Medic, PCNotary,
PrimeSupport, RingFence, Router PM, SecureCast,
SecureSelect, SpamKiller, Stalker, ThreatScan, TIS,
TMEG, Total Virus Defense, Trusted Mail,
Uninstaller, Virex, Virus Forum, Viruscan,
Virusscan, Virusscan (And In Katakana), Webscan,
Webshield, Webshield (And In Katakana), Webstalker,
WebWall, Whats The State Of Your IDS?, Whos
Watching Your Network, Your E-Business Defender,
Your Network. Our Business. are registered
trademarks or trademarks of McAfee, Inc. and/or its
affiliates in the US and/or other countries. Red in
connection with security is distinctive of McAfee(R)
brand products.  All other registered and
unregistered trademarks herein are the sole property
of their respective owners.



_____________________________________________________
LICENSE & PATENT INFORMATION

LICENSE AGREEMENT

NOTICE TO ALL USERS: CAREFULLY READ THE APPROPRIATE
LEGAL AGREEMENT CORRESPONDING TO THE LICENSE YOU
PURCHASED, WHICH SETS FORTH THE GENERAL TERMS AND
CONDITIONS FOR THE USE OF THE LICENSED SOFTWARE. IF
YOU DO NOT KNOW WHICH TYPE OF LICENSE YOU HAVE
ACQUIRED, PLEASE CONSULT THE SALES AND OTHER RELATED
LICENSE GRANT OR PURCHASE ORDER DOCUMENTS THAT
ACCOMPANIES YOUR SOFTWARE PACKAGING OR THAT YOU HAVE
RECEIVED SEPARATELY AS PART OF THE PURCHASE (AS A
BOOKLET, A FILE ON THE PRODUCT CD, OR A FILE
AVAILABLE ON THE WEB SITE FROM WHICH YOU DOWNLOADED
THE SOFTWARE PACKAGE). IF YOU DO NOT AGREE TO ALL OF
THE TERMS SET FORTH IN THE AGREEMENT, DO NOT INSTALL
THE SOFTWARE. IF APPLICABLE, YOU MAY RETURN THE
PRODUCT TO MCAFEE OR THE PLACE OF PURCHASE FOR A
FULL REFUND.


LICENSE ATTRIBUTIONS

This product includes or may include:
*Software developed by the OpenSSL Project for use
in the OpenSSL Toolkit (http://www.openssl.org/).
*Cryptographic software written by Eric A. Young
and software written by Tim J. Hudson. *Some
software programs that are licensed (or sublicensed)
to the user under the GNU General Public License
(GPL) or other similar Free Software licenses which,
among other rights, permit the user to copy, modify
and redistribute certain programs, or portions
thereof, and have access to the source code. The GPL
requires that for any software covered under the GPL
which is distributed to someone in an executable
binary format, that the source code also be made
available to those users. For any such software
covered under the GPL, the source code is made
available on this CD. If any Free Software licenses
require that Network Associates provide rights to
use, copy or modify a software program that are
broader than the rights granted in this agreement,
then such rights shall take precedence over the
rights and restrictions herein.  *Software
originally written by Henry Spencer, Copyright 1992,
1993, 1994, 1997 Henry Spencer.  *Software
originally written by Robert Nordier, Copyright
(C)1996-7 Robert Nordier.  *Software written by
Douglas W. Sauder.  *Software developed by the
Apache Software Foundation (http://www.apache.org/).
A copy of the license agreement for this software
can be found at
www.apache.org/licenses/LICENSE-2.0.txt.
*International Components for Unicode ("ICU")
Copyright (C)1995-2002 International Business
Machines Corporation and others.  *Software
developed by CrystalClear Software, Inc., Copyright
(C)2000 CrystalClear Software, Inc. *FEAD(R)
Optimizer(R)  technology, Copyright Netopsystems AG,
Berlin, Germany. *Outside In(R)  Viewer Technology
(C)1992-2001 Stellent Chicago, Inc. and/or Outside
In(R) HTML Export, (C)2001 Stellent Chicago, Inc.
*Software copyrighted by Thai Open Source Software
Center Ltd. and Clark Cooper, (C)1998, 1999, 2000.
*Software copyrighted by Expat maintainers.
*Software copyrighted by The Regents of the
University of California, (C)1989.  *Software
copyrighted by Gunnar Ritter.  *Software
copyrighted by Sun Microsystems(R), Inc. (C)2003.
*Software copyrighted by Gisle Aas. (C)1995-2003.
*Software copyrighted by Michael A. Chase,
(C)1999-2000.  *Software copyrighted by Neil
Winton, (C)1995-1996.  *Software copyrighted by
RSA Data Security, Inc., (C)1990-1992.  *Software
copyrighted by Sean M. Burke, (C)1999, 2000.
*Software copyrighted by Martijn Koster, (C)1995.
*Software copyrighted by Brad Appleton,
(C)1996-1999.  *Software copyrighted by Michael G.
Schwern, (C)2001.  *Software copyrighted by Graham
Barr, (C)1998.  *Software copyrighted by Larry
Wall and Clark Cooper, (C)1998-2000.  *Software
copyrighted by Frodo Looijaard, (C)1997.
*Software copyrighted by the Python Software
Foundation, Copyright (C)2001, 2002, 2003. A copy
of the license agreement for this software can be
found at www.python.org.  *Software copyrighted by
Beman Dawes, (C)1994-1999, 2002.  *Software
written by Andrew Lumsdaine, Lie-Quan Lee, Jeremy G.
Siek (C)1997-2000 University of Notre Dame.
*Software copyrighted by Simone Bordet & Marco
Cravero, (C)2002.  *Software copyrighted by
Stephen Purcell, (C)2001.  *Software developed by
the Indiana University Extreme! Lab
http://www.extreme.indiana.edu/).  *Software
copyrighted by International Business Machines
Corporation and others, (C)1995-2003.  *Software
developed by the University of California, Berkeley
and its contributors.  *Software developed by Ralf
S. Engelschall <rse@engelschall.com> for use in the
mod_ssl project (http://www.modssl.org/).
*Software copyrighted by Kevlin Henney,
(C)2000-2002.  *Software copyrighted by Peter
Dimov and Multi Media Ltd. (C)2001, 2002.
*Software copyrighted by David Abrahams, (C)2001,
2002. See http://www.boost.org/libs/bind/ bind.html
for documentation.  *Software copyrighted by Steve
Cleary, Beman Dawes, Howard Hinnant & John Maddock,
(C)2000.  *Software copyrighted by Boost.org,
(C)1999-2002.  *Software copyrighted by Nicolai M.
Josuttis, (C)1999.  *Software copyrighted by
Jeremy Siek, (C)1999-2001.  *Software copyrighted
by Daryle Walker, (C)2001.  *Software copyrighted
by Chuck Allison and Jeremy Siek, (C)2001, 2002.
*Software copyrighted by Samuel Krempp, (C)2001.
See http://www.boost.org for updates, documentation,
and revision history.  *Software copyrighted by
Doug Gregor (gregod@cs.rpi.edu), (C)2001, 2002.
*Software copyrighted by Cadenza New Zealand Ltd.,
(C)2000.  *Software copyrighted by Jens Maurer,
(C)2000, 2001.  *Software copyrighted by Jaakko
Jrvi (jaakko.jarvi@cs.utu.fi), (C)1999, 2000.
*Software copyrighted by Ronald Garcia, (C)2002.
*Software copyrighted by David Abrahams, Jeremy
Siek, and Daryle Walker, (C)1999-2001.  *Software
copyrighted by Stephen Cleary (shammah@voyager.net),
(C)2000.  *Software copyrighted by Housemarque Oy
<http:// www.housemarque.com>,(C)2001.  *Software
copyrighted by Paul Moore, (C)1999.  *Software
copyrighted by Dr. John Maddock, (C)1998-2002.
*Software copyrighted by Greg Colvin and Beman
Dawes, (C)1998, 1999.  *Software copyrighted by
Peter Dimov, (C)2001, 2002.  *Software copyrighted
by Jeremy Siek and John R. Bandela, (C)2001.
*Software copyrighted by Joerg Walter and Mathias
Koch, (C)2000-2002.


PATENT INFORMATION

Protected by US Patents 6,470,384; 6,493,756;
6,496,875; 6,553,377; 6,553,378.




V3.0.1
