                  Release Notes for
          McAfee(R) ePolicy Orchestrator(R)
                 Version 3.6 Patch 1
           Copyright (C) 2005 McAfee, Inc.
                 All Rights Reserved


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

This Patch is build number:
3.6.0.556.

This release was developed and tested with:

- ePolicy Orchestrator: 3.6

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 SYSTEMS. USING
    A REMOTE CONSOLE WITH A DIFFERENT VERSION THAN
    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
    -  Additional Changes Included for McAfee Host
        Intrusion Prevention 6.0
-   Installation
    -  Installation Requirements
    -  Installation Steps
    -  Removing This Release
-   Participating in the McAfee Beta Program
-   Contact Information
-   Copyright & Trademark Attributions
-   License & Patent Information


__________________________________________________________
ABOUT THIS RELEASE

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

To maintain full functionality, installing this
Patch is required on ePolicy Orchestrator servers
and all ePolicy Orchestrator remote consoles. Be
sure to patch both server and console systems with
this release.


CHECKING THE NTLM VERSION

NTLM version 2 is currently not supported because of
JTDS driver limitations. Before continuing, ensure
that you are using NTLM version 1, or switch to SQL
Authentication using CFGNAIMS.EXE.

To check the NTLM version:
From the Start menu, select Administrative Tools |
Local Security Policy | Local Policies | Security
Options | Network Security: LAN Manager
authentication level. Make sure this is set to "Send
LM & NTLM responses" on your ePolicy Orchestrator
(ePO) server, the SQL server containing your ePO
database, and your regional domain controller.

Or simply check the following registry key on each
of the servers mentioned above, making sure the
registry value for lmcompatibilitylevel is set to
0:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa


PURPOSE

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


RESOLVED ISSUES

1.  ISSUE:
    The error: "Failed to process XML file" is
    logged in EVENTPARSER.LOG, even when the event
    is eventually processed.

    RESOLUTION:
    The log message is now changed to a more
    informational message: "Failed to process XML
    file, PKG file will be reprocessed for embedded
    XML."

2.  ISSUE:
    Client systems may try to update from the wrong
    repository branch when changing the agents back
    to the current branch from the previous or
    evaluation branch.

    RESOLUTION:
    Client systems update from the correct branch,
    as explicitly defined by the update policy.

3.  ISSUE:
    On the Updates tab of the ePolicy Orchestrator
    Agent policy configuration page, the Repository
    Branch Update Selection policy does not reset
    when reset policy inheritance is selected.

    RESOLUTION:
    Repository Branch Update Selection policy now
    resets properly when reset policy inheritance is
    selected.

4.  ISSUE:
    In the Update History Subreport, any product
    update events that result from an update task
    launched by a managed product are listed by the
    Event IDs instead of meaningful event
    descriptions.

    RESOLUTION:
    In the Update History Subreport, these types of
    product update events are now listed by
    meaningful event descriptions.

5.  ISSUE:
    For any client system with 4 GB RAM or more,
    ePolicy Orchestrator reports an incorrect amount
    of total physical memory.

    RESOLUTION:
    ePolicy Orchestrator now reports the correct
    amount of total physical memory on client
    systems.

6.  ISSUE:
    Large events forwarded from System Compliance
    Profiler are processed too slowly by Event
    Parser, causing a backlog of events waiting to
    be processed.

    RESOLUTION:
    Changes have been made to significantly improve
    the performance of System Compliance Profiler
    event processing.

7.  ISSUE:
    Properties containing localized strings might
    cause the ePolicy Orchestrator server to fail to
    process the properties, and as a result no
    policies are sent to the agent.

    RESOLUTION:
    Properties containing localized strings are now
    processed properly.

8.  ISSUE:
    When two or more replications are run
    concurrently, one or more of the replications
    may fail with the following error in the
    EPOAPSVR.LOG: "Failed to save sitelist file
    C:\WINNT\TEMP\SiteList.xml, hr = 0x80070020."

    RESOLUTION:
    Separate temporary folders are now used for each
    replication task, which prevents a race
    condition from occurring, effectively resolving
    this issue.

9.  ISSUE:
    When upgrading from ePolicy Orchestrator 3.5,
    the pull now and scheduled pull tasks use the
    NAIFtp site by default.

    RESOLUTION:
    The pull now and scheduled pull tasks now use
    the NAIHttp site by default.

10. ISSUE:
    If the Common Management Agent requests policy
    from the ePolicy Orchestrator (ePO) server and
    fails to download the policy, the ePO server may
    not send a future policy for missed items until
    they have been modified on the server.  This
    results in a policy compilation error on the
    client system.

    RESOLUTION:
    When requesting policy, Common Management Agent
    now sends its current policy list to the ePO
    server.  This allows the server to send any
    missing policy.

       NOTE:
       This fix requires Common Management Agent
       3.5.5, which is due to be released in Q1
       2006.

11. ISSUE:
    Event Parser leaks memory when it processes
    server events.

    RESOLUTION:
    Server events no longer cause a memory leak when
    processed by the Event Parser.

12. ISSUE:
    Tomcat leaks memory when running server tasks
    that require web actions, such as pull tasks.

    RESOLUTION:
    Identified memory leaks have been fixed so that
    Tomcat no longer leaks memory when it runs
    server tasks.

13. ISSUE:
    The name of a Registered Executable in the
    External Commands option for Rogue System
    Detection and Notifications cannot be edited.

    RESOLUTION:
    The name of a Registered Executable in the
    External Commands option can now be edited.

14. ISSUE:
    When new content updates for System Compliance
    Profiler are checked into the repository, the
    latest Microsoft patches do not appear in the
    rules configuration screen.

    RESOLUTION:
    The latest Microsoft patches now appear in the
    rules configuration screen after new System
    Compliance Profiler content is checked into the
    repository.

15. ISSUE:
    When a response is set up in Rogue System
    Detection to push the ePO agent with a custom
    installation path, once the response is saved,
    the path reverts back to the default
    installation path for the agent.

    RESOLUTION:
    When the installation path for the ePO agent
    push from the Rogue System Detection interface
    is changed from the default, the path is now
    saved properly.

16. ISSUE:
    When configuring proxy settings, both the
    repository wizard and the edit proxy dialog box
    in the Repository interface do not allow special
    characters, such as the "@" symbol or a period.

    RESOLUTION:
    The HTTP and FTP proxy authentication dialog
    boxes now accept special characters such as the
    "@" symbol and the period.

17. ISSUE:
    From a remote console, if you try to copy a
    package to the current branch from the
    evaluation branch, the progress bar indicates
    that the package was copied successfully, but
    the package is not actually copied to the
    current branch.

    RESOLUTION:
    A remote console can now properly copy a package
    from the evaluation branch to the current
    branch.

18. ISSUE:
    Common Management Agent (CMA) compiles policy
    after each agent-to-server communication due to
    the ePolicy Orchestrator server sending
    unchanged agent meta policy.

    RESOLUTION:
    ePolicy Orchestrator server no longer sends
    unnecessary policy data during every
    agent-to-server communication, preventing the
    need for CMA to compile policy for every
    agent-to-server communication.

19. ISSUE:
    The 3DES algorithm implemented in NAISIGN, which
    is used by SPIPE4 to encrypt and decrypt, has
    poor performance.

    RESOLUTION:
    The code has been revised and encryption and
    decryption performance is substantially
    improved.

20. ISSUE:
    Users are unable to schedule a task for any
    interval less than one hour.

    RESOLUTION:
    Users are now able to enter decimal values, thus
    allowing tasks to be scheduled for intervals
    smaller than one hour.

21. ISSUE:
    Policy settings that contain foreign characters
    are not properly saved in the ePolicy
    Orchestrator database.

    RESOLUTION:
    Policy settings that contain foreign characters
    are now saved properly in the database.

22. ISSUE:
    When non-English characters are entered in
    password fields within ePolicy Ochestrator, the
    passwords may become corrupted during the
    encryption/decryption process.

    RESOLUTION:
    ePolicy Orchestrator now has better support for
    special characters in passwords.

23. ISSUE:
    Property files are not saved to disk in ePolicy
    Orchestrator 3.6, making it difficult to
    troubleshoot failures in processing properties.

    RESOLUTION:
    Debug functionality has been added to
    NAIMSERV.DLL for additional logging and for
    saving defective properties files to the
    DB\Debug directory.

    To enable the additional debug functionality of
    saving malformed agent properties to a debug
    folder, follow these steps:

    1. Open regedit on the ePolicy Orchestrator
    server.

    2. Browse to HKEY_LOCAL_MACHINE\SOFTWARE\Network
    Associates\ePolicy Orchestrator.

    3. Create a new DWORD value called
    SaveAgentProps and set that DWORD value to 1.

    4. Restart the McAfee ePolicy Orchestrator 3.6.0
    Server (Apache) service.

    The malformed properties files will be saved to
    the ePO\3.6.0\DB\Debug directory in the
    following format:
    <Computer_Name>_<Timestamp>_Props.xml.

       NOTE:
       Only enable this debug functionality for
       troubleshooting purposes because this
       directory will grow without limit. When not
       troubleshooting, set the DWORD value for
       SaveAgentProps to O and restart the McAfee
       ePolicy Orchestrator 3.6.0 Server (Apache)
       service.


ADDITIONAL CHANGES INCLUDED FOR MCAFEE HOST
INTRUSION PREVENTION 6.0

    NOTE:
    At the time these Release Notes were written,
    McAfee Host Intrusion Prevention was in Beta
    II.

1.  Implementation of notification categories for
    McAfee Host Intrusion Prevention 6.0.

2.  The ability to remove an assignment of policy
    from the first slot while there is more than one
    policy assigned to the node.

3.  Clicking cancel at the assignment dialog of
    multiple policy objects no longer results in
    policy assignment.

4.  A security dialog no longer appears on the user
    creation screen when you have the McAfee Host
    Intrusion Prevention 6.0 NAP checked in on a
    Microsoft Windows 2003 server running ePolicy
    Orchestrator.

5.  Clicking the "Export all policies" button for
    McAfee Host Intrusion Prevention now properly
    exports the policies, including customized
    policy settings.

6.  Deleted client properties no longer appear in
    the ePolicy Orchestrator Properties tab after
    the next agent-to-server communication.  This
    feature requires Common Management Agent version
    3.5.5, which is due to be released in Q1 2006.

7.  The message "Please click 'Apply' to save your
    changes" only appears on McAfee Host Intrusion
    Prevention policy windows when appropriate.


__________________________________________________________
INSTALLATION

INSTALLATION REQUIREMENTS

To use this release, you must have ePolicy
Orchestrator 3.6 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 EPO3601.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 databases" in the
    ePolicy Orchestrator 3.6 Installation Guide.

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

5.  Close all ePolicy Orchestrator consoles.

6.  On the taskbar, click the "Start" button, then
    select "Run." 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.6 Patch 1 Setup" wizard
    appears.

8.  Click "Next" to begin the installation.

9.  Click "Finish" to complete the installation.

10. For all remote consoles, repeat Steps 4  9.


REMOVING THIS RELEASE

To remove this Patch from your computer, uninstall,
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.


__________________________________________________________
PARTICIPATING IN THE MCAFEE BETA PROGRAM

To download new beta software or to read about the
latest beta information, visit the McAfee beta web
site located at:
       http://www.mcafeesecurity.com/us/downloads/beta/mcafeebetahome.htm

To submit beta feedback on any McAfee product, send
e-mail to:
       mcafee_beta@mcafee.com

McAfee is devoted to providing solutions based on
your input.


__________________________________________________________
CONTACT INFORMATION

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

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

    AVERT WebImmune & Submit a Virus Sample (Logon
    credentials required)
       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/

    Anti-Virus DAT File and Engine Updates
       http://www.mcafeesecurity.com/us/downloads/updates/

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

    Anti-Spam Rules File and Engine Updates
       ftp://ftp.mcafee.com/spamdefs/1.x/

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

       Valid grant number required (contact Customer
       Service)

    HotFix and Patch Releases
   -   For Security Vulnerabilities (Available to
       the public)
       http://www.mcafeesecurity.com/us/downloads/updates/hotfixes.asp
   -   For Products (ServicePortal account and
       McAfee Technical Support grant number
       required)
       https://mysupport.nai.com/products/products.asp

    Product End-of-Life Support
       http://www.mcafeesecurity.com/us/products/mcafee/end_of_life.htm


SOFTWARE AND HARDWARE TECHNICAL SUPPORT
    Home Page
       http://www.mcafeesecurity.com/us/support/technical_support

    KnowledgeBase Search
       http://knowledgemap.nai.com/

    McAfee Technical Support ServicePortal (Logon
    credentials required)
       https://mysupport.mcafeesecurity.com

    McAfee Security Alerting Service (MSAS)
       http://mysupport.nai.com/supportinfo/pvans_info.asp


CUSTOMER SERVICE
    US, Canada, and Latin America toll-free:
   Phone:     +1-888-VIRUS NO or +1-888-847-8766
              Monday-Friday, 8am-8pm, Central Time

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

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


MCAFEE BETA PROGRAM
    Download Site:
       http://www.mcafeesecurity.com/us/downloads/beta/mcafeebetahome.htm

    E-mail to Submit Beta Feedback:
       mcafee_beta@mcafee.com


TRAINING: MCAFEE UNIVERSITY
       http://www.mcafeesecurity.com/us/services/education/mcafee/university.htm


WORLDWIDE OFFICES
    For addresses and phone numbers of worldwide
    offices:

       http://www.mcafeesecurity.com/us/contact/home.htm


_____________________________________________________
COPYRIGHT & TRADEMARK ATTRIBUTIONS

Copyright (C) 2005 McAfee, 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
McAfee, Inc., or its suppliers or affiliate
companies.


TRADEMARKS

ACTIVE FIREWALL, ACTIVE SECURITY, ACTIVESECURITY
(AND IN KATAKANA), ACTIVESHIELD, CLEAN-UP, DESIGN
(STYLIZED E), DESIGN (STYLIZED N), ENTERCEPT,
EPOLICY ORCHESTRATOR, FIRST AID, FOUNDSTONE,
GROUPSHIELD, GROUPSHIELD (AND IN KATAKANA),
INTRUSHIELD, INTRUSION PREVENTION THROUGH
INNOVATION, MCAFEE, MCAFEE (AND IN KATAKANA), MCAFEE
AND DESIGN, MCAFEE.COM, MCAFEE VIRUSSCAN, NET TOOLS,
NET TOOLS (AND IN KATAKANA), NETSCAN, NETSHIELD,
NUTS & BOLTS, OIL CHANGE, PRIMESUPPORT, SPAMKILLER,
THREATSCAN, TOTAL VIRUS DEFENSE, VIREX, VIRUS FORUM,
VIRUSCAN, VIRUSSCAN, VIRUSSCAN (AND IN KATAKANA),
WEBSCAN, WEBSHIELD, WEBSHIELD (AND IN KATAKANA) are
registered trademarks or trademarks of McAfee, Inc.
and/or its affiliates in the US and/or other
countries. The color red in connection with security
is distinctive of McAfee 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 McAfee 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) 1996, 1989, 1998-2000.
*Software copyrighted by Gunnar Ritter. *Software
copyrighted by Sun Microsystems, Inc., 4150 Network
Circle, Santa Clara, California 95054, U.S.A., (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. *Software copyrighted by
Carnegie Mellon University (C) 1989, 1991, 1992.
*Software copyrighted by Cambridge Broadband Ltd.,
(C) 2001-2003. *Software copyrighted by Sparta,
Inc., (C) 2003-2004. *Software copyrighted by
Cisco, Inc and Information Network Center of Beijing
University of Posts and Telecommunications, (C)
2004. *Software copyrighted by Simon Josefsson, (C)
2003. *Software copyrighted by Thomas Jacob, (C)
2003-2004. *Software copyrighted by Advanced
Software Engineering Limited, (C) 2004. *Software
copyrighted by Todd C. Miller, (C) 1998. *Software
copyrighted by The Regents of the University of
California, (C) 1990, 1993, with code derived from
software contributed to Berkeley by Chris Torek.


PATENTS

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



V3.1.3
