                   Release Notes for
          McAfee(R) Common Management Agent(TM)
          Version 3.1, Service Pack 2a, Patch 7
                   Copyright (C) 2004
          Networks Associates Technology, Inc.
                  All Rights Reserved

__________________________________________________________


Thank you for using the McAfee(R) Common Management
Agent(TM) software. This file contains important
information regarding this release. We strongly
recommend that you read the entire document.


IMPORTANT:
McAfee Security does not support automatic
upgrading of a pre-release version of the
software (beta or release candidate). To upgrade
to a production release of the software, you
must first uninstall the existing version of the
software.

__________________________________________________________

Patch Release:    June 16, 2004

This release was developed and tested with:

   - Common Management Agent: 3.1.2
   - ePolicy Orchestrator: 3.0.2a

Make sure you have installed these versions before
using this release.

_________________________________________________________
WHAT'S IN THIS FILE

-   Important Note
-   About This Release
   -   Purpose
   -   Resolved Issues
   -   Previously Resolved Issues
   -   Files Included with This Release
-   Installation
   -   Installation Requirements
   -   Installation Steps
   -   Checking the Agent Package into the Master
       Repository
   -   Creating the New Agent Installation Package
   -   Replicating the Agent Package to Distributed
       Repositories
   -   Monitoring Agent Deployment
-   Participating in the McAfee Security beta program
-   Contacting McAfee Security and Network
    Associates
-   Copyright
-   Trademarks, License Attributions & Patent
    Information
   -   Trademarks
   -   License Agreement and Attributions
   -   Patent Information

_________________________________________________________
IMPORTANT NOTE

    We strongly recommend that you install Service
    Pack 2a for ePolicy Orchestrator software before
    you install this release. You can download the
    Service Pack from the McAfee Security web site
    at:

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


    You will need to supply your customer grant
    number or user name and password to access this
    site.

__________________________________________________________
ABOUT THIS RELEASE


PURPOSE

This patch replaces the Common Management Agent
3.1.2 to resolve the issues listed below. This is
intended for ePolicy Orchestrator 3.0.2 customers.


RESOLVED ISSUES

1.  ISSUE:
    Installation of Common Management Agent version
    3.1.2 Patch 6 would not complete on some Windows
    95 systems.

    RESOLUTION:
    This issue has been fully resolved in this
    release.

2.  ISSUE:
    Emailing a web page from some versions of
    Internet Explorer would cause Outlook to stop
    responding when the "Send" button was clicked.

    RESOLUTION:
    This issue has been fully resolved in this
    release.

3.  ISSUE:
    There was a potential security issue with URIs
    sent to the agent when they contained a dot
    character.

    RESOLUTION:
    This issue has been fully resolved in this
    release.  McAfee would like to thank Robert W.
    Baird for identifying this issue, and working
    with us to resolve it in a professional and
    timely manner.

4.  ISSUE:
    In previous releases, it was possible to deploy
    a site list that contained invalid information
    for a network, causing remote agents to be
    orphaned and unable to communicate to any
    ePolicy Orchestrator server.  This would usually
    require manual intervention to resolve.

    RESOLUTION:
    This release of the Common Management Agent
    includes a new feature that allows the agent to
    keep track of the last good known ePolicy
    Orchestrator connection in the system registry.
    If a site list is deployed to the agent that
    contains a list of sites that it cannot connect
    to, it will make an attempt to connect to this
    saved ePolicy Orchestrator site to retrieve
    another site list that may have corrected data.
    This feature aids system administrators in
    recovering from deployments of site lists that
    contain invalid information.

5.  ISSUE:
    Sitelist.xml files that contained "Type=Server"
    references would not be overwritten or modified,
    even if a new site list is downloaded from the
    ePolicy Orchestrator server.  This mainly
    affected VirusScan Enterprise 7.0 customers
    migrating from an unmanaged environment to one
    managed by ePolicy Orchestrator.

    RESOLUTION:
    This release of the Common Management Agent
    correctly modifies a sitelist.xml file if it
    contains "Type=Server" and new site list
    information has been retrieved from the ePolicy
    Orchestrator server.


PREVIOUSLY RESOLVED ISSUES

1.  ISSUE:
    Task names containing "% s" cause the framework
    service to crash and tasks do not run.

    RESOLUTION:
    Task names can now contain "% s".

    NOTE:
    Clients with task names containing "`P" will see
    this converted to "%".

2.  ISSUE:
    Scheduler crashes after a machine has been off
    for more than 1 day.

    RESOLUTION:
    Improvements have been made to the handling of
    threads in the scheduler.

3.  ISSUE:
    Upgrading a 2.5.1 agent to 3.X does not maintain
    the same GUID.

    RESOLUTION:
    The agent GUID is saved when upgrading a 2.5.1
    agent to a 3.X agent.

4.  ISSUE:
    A distributed repository whose name is a subset
    of a master repository name, becomes disabled
    when the master repository is marked disabled.

       EXAMPLE:
       Master repository name  ePOmasterrepository
       Distributed repository name  repository

    RESOLUTION:
    The distributed repository will not become
    disabled if the master repository is set to
    disabled.

5.  ISSUE:
    Installing the agent to a French Canadian
    language pack installs in English not French.

    RESOLUTION:
    Installs on a French Canadian language pack are
    now in French.

6.  ISSUE:
    Installation failure on terminal servers when
    upgrading a 2.5.1 agent.

    RESOLUTION:
    The installation of the 3.1.2 agent will now
    upgrade a 2.5.1 agent on a terminal server. The
    3.1.2 agent must be installed on the local
    terminal server through installation mode. Do
    not push the 3.1.2 agent to a terminal server.
7.  ISSUE:
    Updating from a mirrored UNC repository fails
    because an extra carriage return is added to the
    file DELTA.INI.

    RESOLUTION:
    Mirrored UNC repositories no longer add an extra
    carriage return to the file DELTA.INI.

8.  ISSUE:
    Updates from a FTP server that include a sign on
    banner that begins with more than 4 blank spaces
    will fail. The FTP login failed.

    RESOLUTION:
    The agent can now login to a FTP server with a
    sign on banner that begins with 4 blank spaces.

9.  ISSUE:
    Install VS 7.x or the ePolicy Orchestrator agent
    on an XP SP2 system will result in update
    failures. This is due to the new blank default
    security settings in DCOMCNFG.

    RESOLUTION:
    In supporting Microsoft's effort to increase
    security, NAI will now set the appropriate
    security settings at install time.

    HOW TO QUALIFY FOR THIS:
    Install VS 7.x and receive a COM error during an
    update. DCOMCNFG should have nothing listed for
    Access permissions or Launch/Activation
    permissions. Adding SYSTEM and INTERACTIVE to
    the default security will enable updating to
    work.

10. ISSUE:
    During a scheduled update, scheduled ePolicy
    Orchestrator task or a normal ePolicy
    Orchestrator communications, a stack error
    occurs in the AGENT_<computername>.log. These
    are rare situations when multiple threads
    accessing the same .XML file and will make CMA
    unstable.

    RESOULTION:
    CMA will now allow for better .XML handling.

    HOW TO QUALIFY FOR THIS:
    Look for stack errors in the
    AGENT_<computername>.log

11. ISSUE:
    Autoupdates or Replication tasks to an FTP
    server could hang or fail due to commands
    getting out of order. This was due to responses
    coming back from the FTP or Proxy that CMA was
    not expecting.

    RESOULTION:
    CMA will now no longer hang or fail if the FTP
    communications are not what we expect.

    HOW TO QUALIFY FOR THIS:
    Look for FTP communications that seem to hang
    after an Autoupdate or a Logon during an
    Autoupdate. One symptom is this happening during
    very busy Proxy or Network traffic and us
    failing WinInet and using Windows Socket
    communication.

12. ISSUE:
    CMA could appear to be in a high CPU state or
    log a crash in the Agent_<computername>.log if
    the sitelist.xml becomes corrupt.

    RESOULTION:
    CMA will now handle these situations and either
    resolve the issue by recreating the sitelist.xml
    from ePolicy Orchestrator or log an error.

    HOW TO QUALIFY FOR THIS:
    Deleting the sitelist.xml file seems to make the
    issue go away permanently.

13. ISSUE:
    Replication of 0-byte files could occur under a
    number of situations. This could cause products
    to not replicate or update errors with older
    products such as VirusScan 4.5.1 to a ePolicy
    Orchestrator 3.x repository.

    RESOULTION:
    The Framework service will now properly handle
    any transfers of 0-byte files through its
    Replication and Pull tasks.

    HOW TO QUALIFY FOR THIS:
    The Pull task will error on a file that is
    0-byte while still copying that file to the
    repository for Replication. NAI has also seen
    VirusScan product replications fail due to
    0-byte files being replicated.

14. ISSUE:
    During a scheduled update, scheduled ePolicy
    Orchestrator task or a normal ePolicy
    Orchestrator communications, a stack error
    sometimes occurred in the
    AGENT_<computername>.log.

    RESOULTION:
    CMA no longer produces stack errors during these
    operations.

15. ISSUE:
    Auto-updates or Replication tasks to an FTP
    server sometimes stopped responding, or failed,
    due to commands being in a different order than
    what the update task expected.

    RESOULTION:
    CMA will no longer stops responding or fails if
    the FTP or Proxy response is not what the update
    task is expecting.

16. ISSUE:
    Replication of 0-byte files sometimes occurred.
    This caused products to not replicate correctly,
    or caused update errors with older products such
    as VirusScan 4.5.1 to a ePolicy Orchestrator 3.x
    repository.

    RESOULTION:
    The Framework service now properly handles any
    transfers of 0-byte files through its
    Replication and Pull tasks.

17. ISSUE:
    UNC/DFS updates were unresponsive or not
    complete under some circumstances.

    RESOULTION:
    UNC/DFS now handles different network
    configurations correctly.


FILES INCLUDED WITH THIS RELEASE

This release consists of a package called
CMA3127.ZIP, which contains the following files:

    Agent.dll
    Agent.ini
    AgentPlugin.dll
    AgentRes.Dll
    Agt300Det.McS
    AppLib.dll
    Cabinet.dll
    Cleanup.exe
    ClientUI.dll
    CMAUIRes.dll
    CmdAgent.exe
    ComponentSubsystem.dll
    ComponentUserInterface.dll
    Contact.Txt
    FrameworkLog.xsl
    FrameworkManifest.xml
    FrameworkPackage.exe
    FrameworkService.exe
    FrmInst.exe
    FrmPlugin.dll
    Genevtinf.dll
    Install.pkg
    InstallMain.McS
    InternetManager.dll
    ListenServer.dll
    Logging.dll
    Logo.jpg
    Management.dll
    McScript.Exe
    Mcurial.Dll
    naCmnLib.dll
    nagshr32.dll
    NaiLog.Dll
    Nainet.dll
    naisign.dll
    naizlb32.dll
    naPolicyManager.dll
    naPrdMgr.exe
    naSPIPE.dll
    naXML.dll
    Patchw32.dll
    PcrPlug.dll
    PkgCatalog.z
    PoEvtInf.dll
    PSAPI.dll
    readme.txt
    Scheduler.dll
    ScriptSubSys.dll
    ScrptRes.Dll
    SecureFrameworkFactory.dll
    Server.xml
    SrPubKey.bin
    unicows.dll
    UpdateMain.McS
    UpdaterUI.exe
    UpdateSubSys.Dll
    UpdPlug.Dll
    UpdRes.Dll
    UserSpace.Dll
    WStub32.Exe
    XMLWrap.Dll

__________________________________________________________
INSTALLATION


INSTALLATION REQUIREMENTS

To use this release, you must have ePolicy
Orchestrator 3.1 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 EPO3127.ZIP file to the temporary
    folder that you created in Step 1.


CHECKING THE AGENT PACKAGE INTO THE MASTER
REPOSITORY

    NOTE
    You cannot check in packages while pull or
    replication tasks are executing.

1.  Log on to the desired ePolicy Orchestrator
    server using a global administrator user
    account.

2.  In the console tree under "ePolicy Orchestrator"
    | <SERVER>, select "Repository."

3.  In the details pane under "AutoUpdate Tasks,"
    click "Check in package." The "Check in package"
    wizard appears.

4.  Click "Next" to open the package type dialog
    box.

5.  Select "Products or updates," then click "Next."
    The catalog file dialog box appears.

6.  Select the package catalog (PKGCATALOG.Z) file
    from the temporary folder you created in Step 1
    of "Installation Steps." You can type the path
    to this file, or click "Browse" to select it,
    then click "Next." The summary dialog box
    appears.

7.  Click "Finish" to check in the package.

8.  Click "Close" after the package has been checked
    in.


CREATING THE NEW AGENT INSTALLATION PACKAGE

1.  Stop the "McAfee ePolicy Orchestrator 3.0
    Server" service. This procedure varies depending
    on the operating system. For instructions, see
    the operating system product documentation.

2.  Delete the FRAMEPKG.EXE and FRAMEWORK.Z files
    from this location in the installation
    directory:

       \DB\SOFTWARE\CURRENT\EPOAGENT3000\INSTALL\0409

    The default location of the installation
    directory is:

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

    If you upgraded the software from version 2.0,
    2.5, or 2.5.1, the default location is:

       C:\PROGRAM FILES\MCAFEE\EPO\2.0

       NOTE
       This step is not necessary if ePolicy
       Orchestrator 3.0 SP2a patch 3 is installed on
       the ePolicy Orchestrator server.

3.  Start the "McAfee ePolicy Orchestrator 3.0
    Server" service. This procedure varies depending
    on the operating system. For instructions, see
    the operating system product documentation.


REPLICATING THE AGENT PACKAGE TO DISTRIBUTED
REPOSITORIES

    NOTE
    Since local distributed repositories can only be
    accessed from client computers, replication
    tasks do not copy packages from the master
    repository to local distributed repositories;
    you must manually update local distributed
    repositories with the desired packages.

1.  Log on to the desired ePolicy Orchestrator
    server using a global administrator user
    account.

2.  In the console tree under "ePolicy Orchestrator"
    | <SERVER>, select "Repository."

3.  In the details pane under "AutoUpdate Tasks,"
    click "Replicate now." The "Replicate Now"
    wizard appears.

4.  Click "Next" to open the distributed
    repositories dialog box.

5.  Click "Select All" to select all global and
    SuperAgent distributed repositories, then click
    "Next." The replication type dialog box
    appears.

6.  Select "Incremental replication," then click
    "Finish" to run the task.

7.  Click "Close" after the task has completed.


DEPLOYING THE AGENT TO CLIENT COMPUTERS

Although there are numerous methods you can use to
install the agent on computers you want to manage
via ePolicy Orchestrator, we recommend using the
"Deployment" client task, see below. For a list of
other methods and instructions for each, see "Agent
deployment" in the ePolicy Orchestrator 3.0 Product
Guide.

1.  Log on to the desired ePolicy Orchestrator
    server.

2.  In the console tree under "ePolicy Orchestrator"
    | <SERVER>, right-click "Directory," <SITE>,
    <GROUP>, or <COMPUTER>. The "Policies,"
    "Properties," and "Tasks" tabs appear in the
    details pane.

3.  Click the "Tasks" tab.

4.  Right-click the "Deployment" task, then select
    "Edit Task." The "ePolicy Orchestrator
    Scheduler" dialog box appears.

5.  On the "Task" tab, click "Settings." The "Task
    Settings" dialog box appears.

6.  Deselect "Inherit."

7.  Next to "Agent 3.1.2," select "Install" in
    "Action."

8.  Next to those products that you do not want to
    deploy, select "Ignore" in "Action."

9.  To specify command-line options used when
    installing the agent, click the "..." button
    next to "Agent 3.1.2." For instructions, see
    "Agent installation command-line options" in the
    ePolicy Orchestrator 3.0 Product Guide.

10. If you want this task to also be enforced during
    the policy enforcement interval, select "Run
    this task at every policy enforcement
    interval."

11. Schedule the task. For instructions, see
    "Scheduling client tasks" in the ePolicy
    Orchestrator 3.0 Product Guide.

12. Click "OK" to save the current entries.


MONITORING AGENT DEPLOYMENT

You can use the Agent Versions or the Compliance
Issues reports to monitor the deployment of the
agent. For instructions and information, see
"Running reports," and "Agent Versions report
template" or "Compliance Issues report template" in
the ePolicy Orchestrator 3.0 Product Guide,
respectively.

The new agent version number is



__________________________________________________________
PARTICIPATING IN THE MCAFEE SECURITY BETA PROGRAM

To download new beta software or to read about the
latest beta information, visit the beta web site:

       http://www.networkassociates.com/us/downloads/beta/

To submit your feedback on any McAfee Security beta
product, send e-mail to:

       avbeta@nai.com

McAfee Security is devoted to providing solutions
based on your input.


__________________________________________________________
CONTACTING MCAFEE SECURITY & NETWORK ASSOCIATES

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

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

    PrimeSupport Service Portal
       http://mysupport.nai.com

Login credentials required.


McAfee Security Beta Program
    Beta Web Site
       http://www.networkassociates.com/us/downloads/beta/

    E-mail
       avbeta@nai.com


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

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

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

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


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

    DAT File and Engine Updates
       http://www.networkassociates.com/us/downloads/updates/

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

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

Valid grant number required.
Contact Network Associates Customer Service


Training
    McAfee Security University
       http://www.networkassociates.com/us/services/education/mcafee/university.htm



Network Associates 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:    services_corporate_division@nai.com
   Web:       http://www.nai.com/us/index.asp
              http://www.networkassociates.com/us/index.asp


For additional information on contacting Network
Associates and McAfee Security  including toll-free
numbers for other geographic areas - see the CONTACT
file that accompanied your original product
release.



_____________________________________________________
COPYRIGHT

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 Network Associates
legal department at: 5000 Headquarters Drive, Plano,
Texas 75024, or call +1-972-963-8000.


_____________________________________________________
TRADEMARKS, LICENSE ATTRIBUTIONS & PATENT
INFORMATION

TRADEMARKS

Active Firewall, Active Security, ActiveSecurity (in
Katakana), ActiveHelp, ActiveShield, AntiVirus
Anyware and design, Bomb Shelter, Certified Network
Expert, Clean-Up, CleanUp Wizard, ClickNet, CNX, CNX
Certification Certified Network Expert and design,
Covert, Design (Stylized E), Design (Stylized N),
Disk Minder, Distributed Sniffer System, Distributed
Sniffer System (in Katakana), Dr Solomons, Dr
Solomons label, Entercept, Enterprise SecureCast,
Enterprise SecureCast (in Katakana), ePolicy
Orchestrator, EZ SetUp, First Aid, ForceField, GMT,
GroupShield, GroupShield (in Katakana), Guard Dog,
HomeGuard, Hunter, IntruShield, Intrusion Prevention
Through Innovation, IntruVert Networks, LANGuru,
LANGuru (in Katakana), M and Design, McAfee, McAfee
(in Katakana), McAfee and design, McAfee.com, McAfee
VirusScan, NA Network Associates, Net Tools, Net
Tools (in Katakana), NetCrypto, NetOctopus, NetScan,
NetShield, NetStalker, Network Associates, Network
Associates Coliseum, NetXray, NotesGuard, Nuts &
Bolts, Oil Change, PC Medic, PCNotary, PrimeSupport,
Recoverkey, Recoverkey - International, Registry
Wizard, RingFence, Router PM, SecureCast,
SecureSelect, Sniffer, Sniffer (in Hangul),
SpamKiller, Stalker, TIS, TMEG, Total Network
Security, Total Network Visibility, Total Network
Visibility (in Katakana), Total Virus Defense,
Trusted Mail, UnInstaller, Virex, Virus Forum,
ViruScan, VirusScan, WebScan, WebShield, WebShield
(in Katakana), WebSniffer, WebStalker, WebWall,
Whats The State Of Your IDS?, Whos Watching Your
Network, WinGauge, Your E-Business Defender, Zip
Manager are registered trademarks or trademarks of
Network Associates, Inc. and/or its affiliates in
the US and/or other countries.  Sniffer(R) brand
products are made only by Network Associates, Inc.
All other registered and unregistered trademarks
herein are the sole property of their respective
owners.



LICENSE AGREEMENT AND ATTRIBUTIONS

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 NETWORK ASSOCIATES OR THE PLACE OF
PURCHASE FOR A FULL REFUND.


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.0



