Rational Suite Release Notes
Version 2001.03.00
Updated December 4, 2000 9:07 am
Copyright 2000 Rational Software and its subsidiaries. All rights reserved.
Thank you for choosing a Rational Suite product!
Please read this document to learn about known product issues, important tips, and other Suite product information. Release Notes for each individual product are located on the Rational Solutions for Windows CD in the \Program Files\Rational\doc folder and are installed by default in C:\Program Files\Rational\doc\ when you install the product.
The release notes for all products in Rational Suite are available in
<Install Path>\rs-release-notes.htm . Note that this link (and all links contained in these Release Notes) is designed to work with the default install path of the release note file. If you customized this path during installation, this link will not work.
These release notes provide information critical to installing and using Rational products, including supported platforms and known issues with this release.
These release notes are for the following Rational Suite products:
- Rational Suite Enterprise
- Rational Suite AnalystStudio
- Rational Suite DevelopmentStudio
- Rational Suite TestStudio
- Rational Suite DevelopmentStudio-RealTime Edition
- Rational Team Unifying Platform
All Rational Suite documentation is available on the Rational Solutions for Windows Online Documentation CD.
Additional support information is available at the Rational Suite web site: http://www.rational.com/products/rs/ .
This release contains new functionality for the products in Rational Suite. The release notes for the products in each Rational Suite edition describe the new features for each product. See
<Install Path>\rs-release-notes.htm
for a link to each Rational Suite product's release notes. Note that if you customized your documentation installation for your Rational Suite product, this link will not work, but the file is available by clicking on Start > Programs > Rational Suite > Readme for all products.
Supported Hardware and Software Platforms
This section outlines the supported platforms and installation requirements for this version of Rational Suite. Each component product in the Suite lists specific requirements in its own release notes.
|
|
|
|
|
- Windows NT 4.0 SP 6
- Windows 2000
- Windows 98
- Windows 95
- Windows ME
|
|
|
- 133 MHz or higher Pentium-compatible computer
- 200 MB free disk space (minimum installation)
- 200 MB free disk space (includes all sample applications)
- 64 MB RAM is the recommended minimum;
more memory generally improves responsiveness.
- 2GB hard disk
|
|
|
- Windows NT 4.0 SP4 or higher
- Windows 2000 Server
|
Hosted Development Systems (remote sessions)
|
RequisitePro, Rose, SoDA, ClearCase support hosted development on these platforms:
- Citrix
- Windows Terminal Server (NT 4),
- Windows 2000 Server
|
|
|
|
|
|
VB 6.0 SP3 or higher, VB 5.0
|
|
|
|
|
|
- Internet Explorer 4.01 SP1
Certain Rational products require components from Internet Explorer 4.01 SP1 or higher to run properly. If you do not have Internet Explorer, you can download it from Microsoft's Web site: http://www.microsoft.com/windows/ie. If the Rational installer does not detect that Internet Explorer 4.01 SP1 is already installed on your system, it will not allow the install to proceed.
|
|
|
- RequisitePro IIS 5, 4, Apache
- ClearQuest - IIS 5, 4
- TestStudio - 5, 4
- ProjectStudio IIS 5, Apache
- ClearCase IIS 5, 4, Apache, Netscape
|
Web Servers on Non-Windows Platforms
|
RequisitePro, ProjectStudio, ClearCase, Rose Web Publisher, Rational Unified Process - Apache on
|
Web Clients on Non-Windows Platforms
|
ClearQuest, RequisitePro, ProjectStudio, ClearCase, Rose Web Publisher, Rational Unified Process
Solaris 2.7, HP11, RedHat Linux
|
|
|
- MS JVM Build 3193 (until further notice)
- Sun 1.2.2 JDK
- Sun 1.3 JDK
- JVM in Visual Age for Java
- IBM JDK (Hursley)
|
|
|
- Windows 2000
- NT 4.0 SP 6
- Windows 98 2nd Edition
- Windows 95 SR2
- Windows Millennium (beta)
- "Whistler" Beta (new version of NT)
|
|
|
Requirements Management-Servlet Exec (for IIS)
|
Network Server Requirements
|
If you use Sybase SQL Anywhere software, make sure that your database server meets the following minimum hardware and software requirements:
- Operating system: Windows NT 4.0 Server or Workstation 4.0
- Processor: Pentium
- Memory: 64 MB
- Disk space: 1.3 gigabytes (minimum)
- Network protocol: TCP/IP
Note: Novell NetWare is no longer supported for network servers.
|
|
|
-
ClearQuest:
-
MDAC 2.5 or higher
-
SQL Server 7.0, 6.5 SP2
-
SQL Anywhere 5.5.05
-
Oracle 7.3.4, 8.0.5, and 8.1.6 (8i)
-
RequisitePro:
-
MDAC 2.5
-
Microsoft SQL Server 7.0 SP1, 2000
-
Oracle 7.3.4, 8i
-
TestStudio:
-
MDAC 2.5
-
Microsoft SQL Server 7.0
-
SQL Anywhere 5.5.05
-
Rose Data Modeler:
-
DB2 Universal Database 5.x, 6.x & 7.x
-
DB2 OS390 5.x & 6.x
-
Microsoft SQL Server 6.x & 7.x
-
Oracle 7.x & 8.x
-
Sybase System 12
|
Migration and Conversion Information
If you are working with a Rational Suite product, you must convert your data in a synchronized manner from any prior release to the current release. Do this in the following order:
- Back up your data.
Never omit this step. It is possible that you will inadvertently lose your data during the upgrade. If you have backed it up, you can start over; if you have not backed it up, you cannot start over.
- Upgrade and apply schema packages in existing Rational ClearQuest databases after product installation
- Upgrade Rational RequisitePro projects that are outside of the Rational Administrator Repo project. For information about upgrading the ClearQuest/RequisitePro integration, please refer to the Rational RequisitePro release notes.
- Run the Rational Administrator Convert Repo utility
For more information on conversion and migration issues, see the Migration and Conversion chapter in the manual Configuring Rational Suite.
Upgrading Rational Suite Products
For information about upgrading, refer to the manual, Installing Rational Suite.
You may encounter upgrade issues if you upgrade from Rational Suite 1.0, 1.1 or 1.5 to Rational Suite version 2001, skipping over version 2000. To avoid these issues, you must completely uninstall your old Rational Suite product (this includes cleaning out your registry settings for product and licensing); then install the new version. If the upgrade is the only thing you have done when you encounter an error, the uninstall/reinstall should avoid any issues. However, if you have done other things to your system as well (such as decide at the same time as you are upgrading that you should move repositories etc. around), then you need to address those issues before you uninstall and reinstall.
You must upgrade all of your machines simultaneously; errors will occur when version 2001 products are mixed with products of earlier release and attempt to access the same repositories.
Installation of any Rational Suite product containing a Rational testing component cannot be done without uninstalling the old Suite product first. This is caused by the major redesign, renaming, and relocation of the Rational Testing product components.
Currently, the list of old products that must be uninstalled before installing the new product includes:
- Rational Suite TestStudio
- Rational Suite Enterprise
- Rational Suite PerformanceStudio
- Rational Robot
- Rational TeamTest
- Rational LoadTest
The list of new products that won't work unless you do the uninstall includes all Suite and point products that include TestManager, which is now in the team-unifying platform.
The following new and updated features are included in this release.
- Rational Suite now incorporates ClearCase LT in the Suite product line.
- Rational Suite Extended Help is significantly enhanced. It now:
- Can register and unregister databases and translation strings from the Extended Help executable.
- Is capable of keeping track of the context when viewing Extended Help from multiple tools
- Rational Suite licensing now supports checking for a license without checking out a product license.
- Licensing may now be configured as user-based as well as machine-based.
- Licensing is supported on 64-bit Windows systems
- Rational License Key Administrator can now import temporary license keys
- Unified Change Management projects are supported
- Artifacts may be displayed and edited via XML
- The Synchronizer uses RDSI as its interface method to other Rational Software products
- The License Key Administrator allows you to add a registry entry to display license requesting menus
The Rational Suite Tutorial is not included with the current release of the various Suite products. The tutorial and related documentation will be provided as downloadable items from the Rational web site. Please stay tuned to http://www.rational.com/support/documentation/index.jsp for news announcing the tutorial's availability.
Internationalization and Localization
- Rational Suite and its component products now run in English on Traditional Chinese, Dutch, Korean, and Hebrew operating systems.
- Rational Suite and its component products now run in English and support non-English data on German, French, Italian, Swedish, Japanese, and Simplified Chinese operating systems.
Rational Team Unifying Platform
- The Rational Team Unifying Platform is a new product, consisting of six tools:
- Rational Unified Process
- Rational RequisitePro
- Rational ClearQuest
- Rational SoDA
- Rational TestManager
- Rational ClearCase LT
- Software configuration management solution designed for project workgroups.
- Included as part of all Rational Suite solutions on Windows, ClearCase LT offers Unified Change Management (UCM), the out-of-the-box process that is based on Rational "best practices". This process enables project teams to manage change at the activity level and to control workflow. ClearCase LT includes ClearCase Explorer, an integrated, easy-to-use interface for developers, and a Server Setup Wizard that facilitates getting started with UCM and importing data from PVCS or other change management products.
- Rational ClearCase LT is integrated with all Rational Suite products and is available to work with Rational Suite. Rational ClearCase is also available to the Suite products, however ClearCase is designed for larger teams that require distributed servers, server replication, transparency, or advanced build management. ClearCase LT users can upgrade to ClearCase without changing their process, data, or their work style.
- We recommend that project teams that share data across projects use either ClearCase LT or ClearCase for all members of a team. You cannot mix ClearCase and ClearCase LT installations for the same set of users sharing the same data; when you install your Rational Suite product, if you have ClearCase installed, ClearCase LT is automatically omitted from the install process. For more information on ClearCase LT, see the manual, Introducing ClearCase LT.
Rational QualityArchitect
Rational QualityArchitect is a powerful collection of integrated tools for testing middleware components built with technologies such as Enterprise JavaBeans and COM.
Rational QualityArchitect, in conjunction with Rational Rose, generates test scripts for components and interactions in your Rose model. Once generated, the test scripts can be edited and run right from your development environment or from Rational TestManager.
Rational QualityArchitect is part of Rational Rose Enterprise and is automatically installed in any Rational Suite install of Rational Rose.
The functionality provided by the existing Rational PerformanceArchitect product has been incorporated into Rational QualityArchitect, which is available as part of Rational Suite Enterprise, Rational Suite, DevelopmentStudio, and Rational Rose Enterprise.
- The test planning process is more fully integrated into performance testing.
- Unified Change Management has been incorporated into Automated Testing components.
- Automated testing components support baselining.
- Testing options have been improved. Suites (formerly called schedules) can be nested, shared, and executed based on user-defined preconditions.
- Support for:
- SQL Server 2000
- EJB Playback
- DB-LIB API for SQL Server
- Java and Visual Basic scripting languages
- C APIs for extending TestScript Services to other languages
- Command line test scripts
- Built-in TestScript execution adapters for Java and VB test scripts
- Discontinued features:
- HP-UX 10 UNIX agents are no longer supported
- AIX 4.1 UNIX agents are no longer supported
- Rational LoadTest users will automatically get an upgrade to Rational TeamTest and will be able to run the same number of tests and use the same protocols as they did with Rational LoadTest
- Rational Suite PerformanceStudio users will automatically get upgraded to Rational Suite Enterprise with the same playback capabilities.
Rational Suite TestStudio
- Implements the functionality from the former Rational Suite PerformanceStudio, which is no longer offered
- Displays ClearQuest datastore properties; integrated property sheet
- Custom installations are not currently supported
- Integrated wizards:
- Project configuration:
- ClearQuest
- RequisitePro
- Rational TeamTest
- Displays ClearQuest datastore properties; integrate property sheet
- Project configuration:
- Integration with Rational Purify, Quantify and PureCoverage
- All executables (exe, dll, lib, and ocx) are renamed for the test products. For the most part, components that have a prefix of "sqa7" have been renamed to "rt". (prefix of "rtx" for libraries that load in a global process space).
- Support Unified Change Management in Automated Testing components
- Support for Delphi Versions 3.0, 4.0, and 5.0.
- Support for Oracle Forms 6.0
- New Netscape recording capability and enhanced Netscape playback
Developer Tools (Rational Purify, Rational Quantify, Rational PureCoverage)
- Rational Purify now supports Java. Use Purify to analyze memory allocation and consumption patterns in Java to help you eliminate memory leaks.
- Rational Purify is now available with either a Nodelocked or Named-user license.
- Rational Quantify now collects source-line-level performance data for Java 2 JDK 1.2.2 compliant JVMs and above.
- Rational Quantify is now available with either a Nodelocked or Named-user license.
- Rational PureCoverage now collects source-line-level coverage data for Java 2 JDK 1.2.2 compliant JVMs and above.
- Rational PureCoverage is now available with either a Nodelocked or Named-user license.
Rational Suite PerformanceStudio
- Rational Suite PerformanceStudio has been incorporated into Rational Suite TestStudio. Rational Suite PerformanceStudio users will automatically get an upgrade to Rational Suite Enterprise and will be able to run the same number of tests and use the same protocols as they did with Rational Suite PerformanceStudio.
- Enhanced diagram layout capabilities (Core Rose) provides more flexibility and capabilities for arranging elements on model diagrams.
- Association role names redesigned (Core Rose)
- Script Editor allows font choice (Core Rose Extensibility)
- Specifications for Domain, domain package, and stored procedure elements in models (Data Modeler add-in)
- Custom trigger enhancements for Oracle and DB2 models (Data Modeler add-in)
- Compare/Sync (Data Modeler add-in)
- Support for Sybase Adaptive Server 12.x (Data Modeler add-in)
- UI Updates (Data Modeler add-in)
- Microsoft Windows Web Solution Platform (formerly the Microsoft Windows DNA patterns for Data Modeling platform) (a Visual Basic add-in. Note that the online help for this add-in has not been integrated with the Rose online help. You can access the help directly from the following location in Windows Explorer: <Install Path>\Rational\Rose\vb\templates\ADB\help\adb.hlp ). Note that if you use a customized install path, the above link will not work.
- Enterprise Java Beans 1.1 support (Rose J)
- Java Servlets support (Rose J)
- Enhanced Javadoc support (Rose J)
- Modeless Editor (Rose J, CORBA, XML, and ANSI C++ add-ins)
- CORBA 2.3 support (CORBA add-in)
- VSS Bug fixes
- Parser fidelity fixes / PLF (VC++ add-in)
- New ANSI C++ Add-In, supporting roundtrip engineering, model conversion for Classic C++ models, model check, and class customization capabilities
- Unified Change Management Support (ClearCase Add-in)
- Model Integrator Patch
Rational Rose RealTime Edition
- Code synchronization
- UCM support for activities
- Support for Rational ClearCase snapshot views
- Support for Rational ClearCase LT
- Embedded target - LYNX 3.1
- Model integrator merge granularity improvements
- Runs in English, supports non-English data on German, French, Italian, Swedish, and Japanese operating systems.
Rational ClearQuest and Rational ClearQuest Web
- Support for
- IBM DB2
- Seagate Software Crystal Reports 8
- Oracle 8 client
- Oracle 8i server and client
- Datastore Creation Wizard and Property Sheet
- Many usability improvements (ability to distinguish between test and production databases to prevent users from accidentally using their production databases as test databases, etc.)
- Support for Secure Sockets Layer (SSL)
- Includes a new query authoring tool that lets you create and edit complex queries; this is similar to the functionality available on the Windows interface
- Ability to create reports on the Web
- Many usability improvements have been added, including: View child records from a list view control, Find stateless record types from the Find a Record feature, view the custom help text for fields, etc.
- Recursive REPEATs
- Template Search Path
- Improved Template View
Rational RequisitePro and Rational RequisiteWeb
- Project administrators may now baseline their requirement assets with the rest of their development artifacts, putting all project artifacts under version control with Rational Unified Change Management (UCM) and Rational ClearCase. Baselines allow you to save a snapshot of your project and with this functionality users can make baselines of their projects and create new projects from those baselines using UCM.
- Rational RequisitePro now ships with three project templates that provide pre-configured documents types, requirement types, and attributes based on different usage models: a use-case template, a traditional template, and a composite (mixed use-case and declarative requirement) template. Using the Project Template Wizard, users can also create custom templates based upon their existing projects. These custom templates can include data and security in addition to the project structure.
- The integration with Rational ClearQuest has been enhanced with the ability to create new ClearQuest records from within RequisitePro. With the addition of this feature, the integration is equally powerful from either tool: users are able to create and associate to change request records in ClearQuest from the RequisitePro environment while they can also create and associate to requirements in RequisitePro from the ClearQuest environment. For information about upgrading the ClearQuest/RequisitePro integration, please refer to the Rational RequisitePro release notes.
- Rational RequisiteWeb was completely re-written using JSP technology. Performance improvements are found throughout RequisiteWeb. Additionally, RequisiteWeb may now be hosted on an Apache Web Server running on Unix or Linux in addition to Microsoft IIS.
- Requirement names allow you to assign a name to any requirement. The name may be up to 128 bytes long and include text, numbers or punctuation. Requirement names are displayed along with the requirement tag in views and dialog boxes, but not in documents. For existing users who have been maintaining an attribute to serve as a requirement name, Rational RequisitePro provides a conversion wizard that allows you to populate the requirement name with the value of an existing attribute.
- A new URL attribute type has been created that allows users to store a URL as a requirement attribute, and navigate to that URL from within a RequisitePro Attribute Matrix, or the Requirement Property dialog.
- Rational RequisiteWeb has been enhanced with a Requirement Browser dialog, making it easier to select particular requirements quickly.
- RequisitePro is now capable of installation and use on Hebrew, Korean, Traditional Chinese, and Dutch operating systems, and it has been tested to assure conformance. Users must enter all input data (such as path names) using U.S. English.
- Guidelines for the use of Microsoft Windows DNA technology have been added to the Development Component Solutions roadmap.
- A new small project roadmap has been added
- A new workflow detail, Perform Architectural Synthesis, has been added to Analysis and Design to help with technology selection and to show that the envisioned system is feasible
- Several new tool mentors have been added, including tool mentors for using the Rational Process Workbench
- Tailoring guidance is provided for all artifacts
- There are updated requirements management templates, activities, and guidelines
- Updated examples
- The term "Worker" has been changed to "Role" for clearer understanding of the different roles a team member might perform
- Details have been added to the Visual Modeling best practice
- Staffing sections have been added to roles which previously had none
- Version 2001 software will run with Version 2000 license keys. If you are an existing customer and are using version 2000 of a Rational product, you do not need to obtain new license keys in order to run Version 2001 of the same product.
- You can use your floating licenses under certain conditions while disconnected from your network.
- AccountLink, Rational's online license management tool, is now the way to get and return license keys automatically from Rational. The Rational License Key Administrator does not have an interface for requesting or returning license keys from Rational. You can find AccountLink at http://www.rational.com/accountlink.
- Customers without internet access can request license keys by fax by filling out the license key request form and faxing it to their local Rational Licensing Support office. The form is available at <Install Path>\common\licensing_request_form.htm. The form is also available in German and in French at Rational Fax Form - German.htm and Rational Fax Form - French.htm respectively.
- The enhanced License Usage Mapper allows you to install multiple Rational Suite products on a single machine.
- The enhanced License Usage Mapper allows you to have a Rational Suite product that you installed use the license key for another Suite product that you did not install. For example, you could install Rational Suite Enterprise and have ClearQuest ask the FLEXlm license server for a license of Rational Suite Enterprise, then ask the server for a license of Rational Suite AnalystStudio if the Enterprise key was already in use.
- Rational Solutions for Windows Version 2001 use FLEXlm 7.0. If you upgrade the FLEXlm license server software on a machine with Rational products installed on it, you need to upgrade the Rational products also.
- If you do not have Administrator privileges, you can still use some functions of the License Key Administrator (LKAD). Refer to the Adminstering Licenses for Rational Software manual for more details.
- Rational ClearCase LT is licensed using FLEXlm-based Rational Common Licensing. ClearCase LT is be sold as a floating point-product (not offered as a node-locked point-product) and is also added to all node-locked and floating Rational Suite products. ClearCase LT works with existing Rational Suite license keys. For example, if you have a floating license of Rational Suite Development Studio Version 2000, you can install and use ClearCase LT with that same license key.
- Rational Purify for Windows, Rational Quantify for Windows, and PureCoverage for Windows Version 2001 is now offered as node-locked and named-user floating licenses. Customers who already have node-locked Purify, Quantify and PureCoverage licenses will not be upgraded to named-user floating licenses.
- Rational has merged Rational Suite PerformanceStudio with Rational Suite TestStudio and enhanced TestStudio to offer functional and performance testing capabilities. Existing Rational Suite PerformanceStudio customers will be upgraded to Rational Suite Enterprise Version 2001 with all the appropriate Virtual Testers, Protocols and Agents. Rational has sent these customers a letter that informs them of the upgrade path and how to get their license keys for Rational Suite Enterprise. You must uninstall Rational Suite PerformanceStudio before you can install any Version 2001 Rational product.
- Rational LoadTest Virtual User licenses and Rational LoatTest Protocol licenses have been renamed Rational Test Virtual Tester and Rational Test Protocol licenses respectively.
- Rational TestManager has been enhanced to support LoadTest Virtual Tester and LoadTest Protocol licenses. Therefore, existing Rational Suite PerformanceStudio customers that currently have Virtual User and Protocol licenses can continue using these licenses with Rational TestManager and any product that includes TestManager.
- New Project functionality replaces repositories: the Rational Administrator no longer creates repositories
- You can upgrade repositories to projects from Rational Suite 1.0, 1.5, and 2000, and from test products labeled 7.x
- Unified Change Management implemented
- You must configure your own project to associate Rational Test datastores, RequisitePro projects, ClearQuest databases, and Rose models with the project and optionally bring them under configuration management
- You can create a test datastore based on the established baseline of an existing test datastore and include the data from that baseline. If you have a Rational Test datastore that is baselined, you can use that baseline to create a new Test datastore.
- You can create a Rational RequisitePro project and a Rational Test datastore, both of which you can associate with a Rational Administrator project. Rational RequisitePro project administrators can create baselines of Rational RequisitePro projects by performing tasks in Rational Administrator and Rational ClearCase, implementing the Unified Change Management model.
- You can create a Rational RequisitePro project based on the established baseline of an existing project and include the data from that baseline. If you have a Rational RequisitePro project that is baselined, you can use that baseline to create a new project in Rational RequisitePro.
- Project configuration is enhanced in:
- Rational Rose
- Rational Test
- Rational RequisitePro
- ClearQuest (integrated wizard)
- Project registration is improved
- Projects can now be deleted
- Configuration management:
- Add/remove Test datastore
- You can display ClearCase project properties and integrate a property sheet
- Datastore properties are displayed for:
- Rational RequisitePro
- Rational TeamTest
- Rational ClearQuest
- Property sheets are integrated in:
- Rational RequisitePro
- Rational TeamTest
- Rational ClearQuest
- Wizards integrated for:
- Rational ClearQuest
- Rational RequisitePro
- Rational Test user/group support
- The Rational Installer supports the SQL Anywhere 5.5.05 server
- The user can use the Rational Administrator to start individual Rational tools
- The Rational Administrator now supports baselining in the Rational Administrator, Rational Robot, and Rational TestManager
- The Rational Administrator offers a "Convert - RepoProject" option. Given a RepoProject, the Rational Administrator conversion tool:
- informs the user what Rational ClearQuest packages must be upgraded and points the user to the appropriate documentation
- attempts to determine that the proper packages have been installed in the associated Rational ClearQuest database prior to proceeding with the upgrade.
- runs the Rational RequisitePro project upgrade tool
- converts each RepoProject / subproject pair into a new Rational Administrator project. It will convert the associated team test datastore, and maintain the links that existed for the TeamTest datastore, Rational ClearQuest database, Rational RequisitePro project, and Rose models.
Rational produces synchronized releases of all its products. This is necessary because there are tight integrations between products. If you have installed other Rational products from a previous Rational Solutions for Windows CD, you must uninstall all previous versions of the Rational product you are installing now.
Note: At this point, the Rational ClearQuest Web server cannot coexist with Windows Terminal Server. When installing ClearQuest Web on a Windows 2000 machine, if the machine is also a host for Windows Terminal Server (regardless of whether ClearQuest is being used under Terminal Server), then the Rational ClearQuest Web interface fails to check out a license and the user interface always comes up in "Restricted" mode. The workaround is to use a machine which is not a Windows Terminal Server host as the Rational ClearQuest web server.
Caution-Before You Install
Warning: If you are installing a Rational Suite over an older Rational Suite product, you must back up your data before you proceed with your installation. You must then uninstall the older Rational Suite product before installing the current version.
On occasion, the Rational installation program will display information regarding possible conflicts between files that are being installed and existing files on the system that have the same name. Messages referencing files that exist within a Rational directory are generally benign. However, if any file in question resides in the Windows system directory, we recommend that you investigate that file. One version of the file may be more compatible with existing software on the system than the other. Contact Rational Technical Support for additional information.
If you have additional, older, Rational products installed on your system, you need to remove those older products. Use the Add/Remove Software function in your Control Panel to remove your older version.
If You Are Setting Up a Silent Install
If you have older Rational products installed on your system, you will see a warning page during your installation. If you are setting up a silent install, please pay particular attention to this message and take steps to ensure that users upgrade all Rational products. Users who install silently will not see an error message. A message will appear in the user's error log file, but the user may not remember to look at the log file after completing the install.
If you run the response.ini file for a silent install, the licensing options specified in the response.ini file will not override any licensing options already installed on your system. If your system has no licensing installed, the response.ini file will install the licensing options specified in it.
Before installing any Rational product, make sure that no other applications, including Internet Explorer, are running.
If you are installing a Rational product from a network location, make sure the install image directory has read-only permissions.
Installation and licensing information is available in the License Key Administrator online Help and in the Rational Suite Installation Guide, included on the Rational Solutions for Windows Online Documentation CD.
During installation of Rational Suite, you may receive an error message after rebooting your system, which indicates your Registry memory is low. To complete the installation, increase the maximum Registry size. Log on as a member of the administrators group to change the Registry size limit. In the System Properties control panel, on the Performance tab, in the Virtual Memory area, click Change. In the Virtual Memory dialog box, increase the Maximum Registry Size value. This enables you to specify the maximum size for the Registry. Setting the Registry size doesn't guarantee that the space will be available for the Registry. It only sets the maximum size that can be used when it is needed.
When you set a Registry size limit, it limits both the page pool size and the amount of disk space that can be used by the Registry.
Installing a Rational product under Windows NT 4.0 or Windows 2000 may require rebooting the system. You must log in after reboot using the same USERNAME as the one you used when the install was originally started.
A common scenario for Rational ClearCase installers is that the admin performs the install and the end user subsequently logs on and completes the install. If you install Rational Suite and include Rational ClearCase LT, you may not log on as another user to complete the install. A lot of Rational ClearCase install work occurs after the reboot, so a failure to complete the install as the same user can cause severe problems.
For Windows 9x, double-byte characters are not supported in the install pathname. To work around this, install into a non-double byte character set directory name.
While the installer does not support editing of the installation path in the response.ini file, the situation could arise where a pre-existing response.ini file specifies a path different from a pre-existing Rational product installation on a local machine. This would cause two Rational products to be installed in different locations, and could lead to instability or unusability. The system administrator and the user should be careful to ensure that the installation path specified in the response.ini file and any pre-existing installation path on the local machine are the same.
Rational Software Setup Help reports that Internet Explorer 4.x or higher must be installed on your system to run Rational Software products. See the software requirements section of these release notes for the required version of Internet Explorer. Users who are testing or developing on older platforms and using Internet Explorer 4.0 or earlier, or users who do not have Internet Explorer installed on their system, will have to install Internet Explorer 4.01 SP1 or higher. Otherwise, the latest release of Rational products may not work properly on their system.
When you select a Network installation option, use a UNC pathname, such as \\server\share\directory, rather than a mapped drive letter. This ensures that the network location remains constant, even if drive letter mappings change.
It is possible to inadvertently install a Rational product in more than one location through the Silent Install if the response.ini file is directing the install to a different location from where you presently have a Rational product. This can happen if you directly edit the response.ini file. Rational Software does not support directly editing the response.ini file. However, you can run into this problem if the administrator issues a new response.ini file for your company and you are instructed to use that new file for future company installations. In other words, you don't have to edit the Rational file to cause this problem to occur. Not only does this corrupt your existing and new installation, but it corrupts Rational's un-install from occurring correctly.
Before removing any Rational product through the Windows Control Panel add/remove feature, make sure that you:
- Close all running Rational applications.
- Return any permanent licenses for the products you are removing (if you plan to reinstall on another system/location).
Four DLLs required for Rational Robot Virtual User Script Generation are missing in the typical Enterprise installation.
The workaround to this problem is:
- Bring up a DOS prompt and change directores to your Rational Test directory (in a default installation, that directory is file:///C:\Program Files\Rational\Rational Test):
cd c:\Program Files\Rational\Rational Test
- Run rtfxdlx.exe .
The Minimal Install functionality of Rational products is not supported in this release. You must choose the Typical or Custom/Full options to install your Rational product(s). For information on how to install your Rational product, see your product's Installation manual.
Note that the installation manuals may include information on minimal installations. That information is no longer valid.
If you are using floating licenses, it is recommended that the license server machine be up and running before launching the Rational License Key Administrator. Otherwise, the License Key Administrator will return an error if it is directed to get a license from the server machine.
If you have questions regarding the licensing of your Rational Software products, please contact Rational Licensing Support in your area: http://www.rational.com/support/contact. World-wide Rational Licensing Support contact information can also be found in the Rational installation and licensing guides, and in the on-line help of the License Key Administrator on Windows systems.
Visit http://www.rational.com/support/ for more details about interactions between specific products. Click Upgrades and Patches, then select a product to upgrade, then click Compatability Matrix.
The following sections outline known compatibility issues with software products produced by Rational and other companies. See also the
Compatible Products section.
Important Installation Notice Regarding PowerBuilder Incompatibility with Microsoft MDAC 2.1
If you are a PowerBuilder 5, 6, or 6.5 developer or user, and if your applications use ODBC to connect to Microsoft data sources, such as SQL Server 7 or Microsoft Access, please read the following caveat carefully before installing Rational Suite:
There is a known incompatibility between the Microsoft Data Access Controls (MDAC) v2.1, which are part of the Suite installation, and PowerBuilder's ODBC connectivity to Microsoft data sources. After MDAC 2.1 is installed on a system, any PowerBuilder 5.0, 6.0, or 6.5 applications on that system that use ODBC to connect to a Microsoft Access or Microsoft SQL Server database will be unable to retrieve data from those databases. The reported error is "[Microsoft][ODBC Driver Manager] Program Type Out of Range".
Sybase is aware of this incompatibility and has resolved this problem in the 6.5.1 maintenance release of PowerBuilder. Please contact Sybase technical support for this maintenance release, or for further information on the incompatibility. For more information, visit http://support.sybase.com.
Installing Rational Software in Windows Terminal Server Environment
You can install and run Rational software on a Windows Terminal Server console system as you would on any other supported Windows NT Server system.
Only Rational Rose 2000e, Rational RequisitePro, and Rational SoDA for Windows will run on a Windows Terminal Server client system. To use these products on a Terminal Server client, your console system must be configured to use floating licenses.
Rational ClearQuest Field Name Change May Affect Reporting
The field name RepoProject in Rational ClearQuest has changed to RAProject. You should go through your reporting software to be sure this change is reflected in your report fields or your reports may not include the field or may otherwise malfunction. Refer to the Rational ClearQuest release notes for more information.
Rational ClearQuest Uses Microsoft Access ODBC Driver, Which Reports Incorrect Column Length
The Microsoft Access ODBC driver reports an incorrect column length when calling SQLDescribeCol on a calculated textual field. SQLDescribeCol always returns 2147483598 as the length of calculated column and not the expected 255 (standard length of text column reported by the MDAC 2.5 Access ODBC driver). This problem applies to any version of Rational ClearQuest as it is run on Windows 2000 SP1. To work with Windows 2000 SP1 (or any other product that releases MDAC 2.5.1 or higher), you must be running Rational ClearQuest 2001.03.00 (the current release). For more information, see the Rational ClearQuest Release Notes. Microsoft's description of the problem is on their website: http://support.microsoft.com/support/kb/articles/Q272/9/51.ASP?LN=EN-US&SD=gn&FR=0
Conflict Between Certain Rational Products and Certain Anti-Virus Software
When some software is installed or launched, some virus scanners check each file, including .dll and .ini files, being read and loaded, as part of their normal process. However, this functionality can significantly increase the amount of time it takes for some software to load. This is a result of the interaction between the loading software's dynamic extensibility functionality and the virus checking mechanism used by the anti-virus software.
This functionality of certain anti-virus software could affect the performance of Rational Rose and of the Rational Installer.
Until another solution is found, we suggest you turn off your anti-virus software when loading Rational Rose or installing Rational software. You should, when the software is loaded and running, restart your anti-virus software.
Netscape 6 has not been fully tested for Rational's web products or online documention. Rational has not identified any specific issues associated with Netscape 6. Neither has Rational confirmed that Netscape 6.0 performs properly with all of Rational's products or documentation.
Performance Issues for Medium- to Large-Size Project Source Control Operations
(The performance of adding test and requirements assets to source control and subsequent checkin-all operations can be very slow for medium- to large-sized requirements and test projects.)
Rational Suite 2001 supports the ability to place requirements and test assets under version control in a ClearCase VOB. The support for this is done using two operations from the Rational Administrator: Add to CM and Checkin-All. Add to CM adds the assets to source control and Checkin-All captures a snapshot of the assets at a point in time. In both cases, if there is a large number of existing requirements or test assets, the time it takes for both of these operations may be very long and could make these features unusable in this release, depending on how often you plan to perform these operations.
The time it takes to perform these operations directly depends on the number of files needed to store the requirements and test assets. For requirement assets, the number of files needed depends on the number of saved views, requirement types, and documents. The number of files is not dependent on the number of requirements. For test assets, the number of files needed largely depends on the number of scripts and the number of verification points in each script being managed.
The following information will allow you to estimate the time it will take for the Add to CM and Checkin-All operations for existing requirements and test projects. Performance testing has shown there is a strong relationship between the performance of these operations and the number of file elements placed under source control. Therefore, to estimate the time these operations will take, you need to determine the number of file elements that will be involved in the operation.
The number of files involved in a RequisitePro project that is added to source control or checkpointed can be estimated using the following formula:
Number of Files = 10 + 3 * (Number of Documents) + (Number of Saved Views) + (Number of Requirement Types)
Estimated Operation Time In Minutes:
(10 * Number of Files) / 60 seconds
Here is an example:
Number of Documents = 165
Number of Requirement Types = 12
Number of Saved Views = 37
Number of Files = 10 + 3*165 + 37 + 12 = 554
Minutes = 92.3
Actual performance may vary based on the hardware and database you are using. Using the above example (554 files) took:
83 minutes using Access as the database on a 667 Mhz 256 MB RAM server
90 minutes using Oracle or SQL Server on a 333 Mhz 128 MB RAM server
The number of files involved in a Test project that is added to source control or checkpointed can be estimated using the following formula:
Number of GUI Script Files = (Number of GUI Scripts) * (2 + OP + (2 * OD))
Where:
OP = Average Number of Object Property Verification Points + Average Number of Low Level Scripts + Average Number of Alpha Numeric Verification Points
OD = Average Number of Object Data Verification Points
In short, the number of files is 2 per GUI Script + 1 for each verification point or low level script + 2 for each data verification point.
Number of Files = 200 + Number of GUI Script Files + Number of Manual Scripts
Number of Minutes = (10*Number of Files) / 60 seconds
Here is an example:
Number of GUI Scripts = 200
Number of Maunal Scripts = 100
Estimated 3 Object or AlphaNumeric verification point and/or low level scripts
Estimated 1 Data verification point
Number of GUI Script Files = 200 * (2 + 3 + (2*1)) = 1400
Number of Files = 200 + 1400 + 100 = 1700
Minutes = 283
The 10x factor in computing the time is based on an estimated 5 seconds for two ClearCase operations that must be performed on each file in this implementation. You may be able to further improve the time it takes for these operations by having a high powered and properly configured ClearCase server. Please be sure to allocate enough time if you chose to use this feature.
Late Changes to Documentation
Warning: Always back up your data before attempting to migrate it from a prior Rational Suite release.
To back up your TeamTest data, simply copy the repository to a new location in your Windows Explorer.
Database backup is beyond the scope of this documentation set. To back up your database, you must consult your database vendor's documentation.
Rational RequisitePro Synchronization
If you are upgrading from a prior edition of a Rational Suite product, you must manually edit the SynchLinks attribute of Requirements when it appears for each requirement, changing the name of the attribute from SynchLink to SynchronizerSynchLinks. If you attempt your synchronization without making this change, the Rational Synchronizer crashes and will then no longer recognize previously generated synchlinks.
Discussions of email notification using MAPI are no longer supported by Rational RequisitePro. For more information, see Using Rational RequisitePro and the Rational RequisitePro online help (Start > Programs > Rational Suite > Readme for all products, click on the link to the RequisitePro release notes).
The Rational Suite Tutorial is not included with the current release of the various Suite products. The tutorial and related documentation will be provided as downloadable items from the Rational web site. Please stay tuned to http://www.rational.com/support/documentation/index.jsp for news announcing the tutorial's availability.
Known Defects and Change Requests
The following table identifies known bugs and limitations in this release. In addition, review the release notes for the products included in your Rational Suite edition. See the release note entitled Readme for All Products. This link is designed to be used if you have followed the default install path for your release notes files; if you have customized that path, this link will not work..
Table 1 Known Defects -- 2001.03.00
|
|
|
|
|
|
|
If you resize the ExtendedHelp window, the page displayed in the browser pane may have some information that is not accessible. If this happens, redisplay the page by double-clicking on the appropriate item in the tree view.
|
|
|
|
If no Extended Help databases are active, or there are no target nodes in the target tree, the root appears as a web page but cannot be opened by double clicking. When there are leaf nodes, the root reverts to its proper rendering as a folder.
|
|
|
|
On Japanese systems, an exception occurs when you close the Extended Help window. This is benign and causes no loss of data or data corruption.
|
|
|
|
When using the EHelpUpdate program, if you enter the same file name for the input and output, the input file is overwritten, incorrectly.
|
|
|
|
This note applies both to online Help for Extended Help and to the chapter about Extended Help in Configuring Rational Suite. In the list of valid values for Rose, the subtool "State Diagram" should read "Statechart Diagram".
|
|
|
|
Extended Help requires a display monitor that supports at least 256 colors.
|
|
|
|
- During an installation one should not be concerned by the imformational success message that appears regarding winsock2
- During a silent installation, the installation will pause asking the user to confirm.
|
|
|
|
Before you install the current Rational testing product(s), be sure to uninstall earlier versions of the following products:
- Rational Suite TestStudio
- Rational Suite Enterprise
- Rational Suite PerformanceStudio
- Rational Robot
- Rational TeamTest
- Rational LoadTest
|
|
|
|
Because Rational Purify, Quantify, and PureCoverage are not installed on Windows 95 or 98 systems, the Release Notes for those products are not installed on those platforms. As a result, the links are invalid in rs-release-notes.htm to the Release Notes for those products.
|
|
|
|
Evaluation artifacts are not included as a part of this installation procedure. As a result, when you select the Evaluator option on the Software Use page of the Rational Software Setup program, the samples are not installed.
|
|
|
|
If you plan to access test assets (for example, use a project that has an associated test datastore) with your AnalystStudio or Rational Suite Team Unifying Platform installation, please select the Typical or Custom/Full installation option in the Rational Software Setup program. The Compact install option does not install files required to access test assets.
|
|
|
|
Rational has identified an issue with the FLEXlm redundant license server on Windows platform. The issue is as follows:
If the master redundant server goes down, the other two license servers WILL continue to serve licenses. However, when the master machine comes back up, license requests to the redundant servers fail.
The workaround is to restart all three redundant license servers when the master comes back up.
|
|
|
|
The License Key Administrator crashes in redundant server
mode when any two servers are listed under the same name.
If
two redundant server names are the same, LKAD will crash after the user
presses OK in the Service Configuration Dialog.
LKAD will not restart, and no product license will be able to be
acquired.
Workaround:
Part1:
Registry update
-
Use
Regedit.exe to open the windows registry
-
Navigate
to HKEY_LOCAL_MACHINE\Software\Rational Software\Licensing\1.0\
-
Update
the values associated with these fields to be your 3 redundant
servers.
PrimaryRedundantServer
SecondaryRedundantServer
TertiaryRedundantServe
e.g.
the original values looked like this:
PrimaryRedundantServer
license_server1
SecondaryRedundantServer
license_server2
TertiaryRedundantServer
license_server2
the edited values look like this:
PrimaryRedundantServer
license_server1
SecondaryRedundantServer
license_server2
TertiaryRedundantServer
license_server3
Part2:
File update
-
Open
the file <Install Directory>\common\rational_redirect.dat in
Windows Notepad.
-
Change
the server names to the proper three unique names.
-
Save
the file
e.g.
the original file looked like this:
SERVER
license_server1 ANY 27000
SERVER license_server2 ANY 27000
SERVER license_server2 ANY 27000
USE_SERVER
the
edited file looks like this
SERVER
license_server1 ANY 27000
SERVER license_server2 ANY 27000
SERVER license_server3 ANY 27000
USE_SERVER
|
|
|
|
On occasion, the Rational Administrator may freeze after configuring a project. Operation should resume normally after a few seconds.
|
|
|
|
Use of the Rational Administrator under Windows NT and Windows 2000 systems requires Administrator privileges. If you attempt to connect to a project without write access privileges to the registry, the Rational Administrator may crash.
|
|
|
|
The performance of adding test and requirements assets to source control and subsequent checkin-all operations can be very slow for medium to large sized requirements and test projects.
Rational Suite 2001 supports the ability to place requirements and test assets under version control in a ClearCase VOB. The support for this is done using two operations from the Rational Administrator: "Add to CM" and "Checkin-All". "Add to CM" adds the assets to source control and "Checkin-All" captures a snapshot of the assets at a point in time. In both cases, if there are a large number of existing requirements or test assets, the time it takes for both of these operations may be very long.
The time it takes to perform these operations directly depends on the number of files needed to store the requirements and test assets. For requirement assets, the number of files needed depends on the number of saved views, requirement types, and documents. The number of files is not dependent on the number of requirements. Medium to large sized requirements projects can expect the initial add to CM to take over an hour. For test assets, the number of files needed largely depends on the number of scripts and the number of verification points in each script being managed. Test projects with more than 1000 scripts can expect the initial add to CM to take over 24 hours to complete.
More detailed information on how to estimate the time it will take for your project and advice for configuring your environment for optimal performance can be found at: http://www.rational.com/documentation/
|
|
|
|
If you are upgrading from a prior release of Rational Suite, you must manually edit the Synchlinks attribute of Requirements in RequisitePro when it appears for each requirement, changing the name of the attribute from "SynchLink" to "SynchronizerSynchLinks".
If you attempt your synchronization without making this change, the Synchronizer crashes and will no longer recognize previously generated synchlinks.
|
|
|
|
SoDA will not return any information on Artifacts contained within TestManager Projects due to a known defect with the COM server.
|
Rational QualityArchitect
|
|
If you manually handcoded a RQA VB script or RQA Java script (i.e. Scripts that uses RQA testservices calls in the code), you must manually create the script directory hierachy for the script in the directory you specified.
|
Rational QualityArchitect
|
|
Because your COM Programmatic ID string must be 39 characters or less, you may get the following error from having a .cls filename that, when combined with the VB project name, produces a filename of more than 39 characters.
Programmatic ID string too long '<VB project name>.<RQA cls name>'.
The Programmatic ID must be 39 characters or less
To avoid this error, reduce the length of your Programmatic ID string.
|
|
|
|
If you try to perform an Object Data VP (ODVP) on the first tab of the Start Test form after populating the grid, Rational Robot may send the message Unable to capture data from Selected Object.
As a workaround, select the other tabs, populate them and then go back to the first tab to perform the ODVP. This will allow Rational Robot to capture all your data.
|
|
|
|
When you do a Custom Install of TestStudio selecting Robot as the only product, and go to Rational Test > Java Enabler, the next button is grayed out, but does work if you press it.
Tab functionality does not work for the Next button. Mnemonics do not work for the Next button.
|
|
|
|
On Windows 2000, when opening a Rose model from Windows Explorer, you may be prompted to save changes to the model. After you respond to the prompt, the model closes, sometimes issuing a Rose Synchronizer error. Also on Windows 2000, when opening a model from within the Rose application, a Rose Synchronizer error may appear, but the model opens correctly.
To fix both of these behaviors, please install Windows 2000 SP1
|
|
|
|
At this time, Rational Suites products do NOT support the importation of data from an existing database using double-byte characters for column names. To import the data, change the column names to have ASCII values.
|
|
|
|
The Readme for All Products (rs-release-notes.htm) file may contain inactive links. If you have not installed a product or feature, the release notes for that product or feature will not be accessible.
|
|
|
|
Rational RequisitePro projects with security enabled cannot be synchronized. We suggest you disable security while you synchronize your project. When you have finished, you may re-enable your security if you wish.
|
|
|
|
After converting an older Requisite Pro database to the current version, Requisite Pro items that have never previously been Synchronized may cause crashes when initially synchronized in the converted database. If the user encounters a problem, try using the 'Link To' command to manually set a synchronization target.
|
When installing AnalystStudio, Let's Go AnalystStudio appears at the end of the installation process if the View Release Notes check box is selected. If this installation is an upgrade of an existing AnalystStudio installation, some links in Let's Go AnalystStudio may not function properly. To refresh the links, close Let's Go AnalystStudio and reopen it by clicking Start > Programs > Rational Suite AnalystStudio > Let's Go AnalystStudio.
The Rational Rose 2001 Release Note states that the VC++ add-in requires Visual Studio 6.0.
It should state that both the VB and the VC++ add-ins require Visual Studio 6.0.
If your TestStudio schema is in a resolved state, you must define it as a UCM Completed StateDef type. If you do not do so, you cannot use the default UCM Policies to complete your work.
If you have questions about installing, using, or maintaining this product, contact Rational Technical Support as follows:
|
|
|
|
|
|
|
(800) 433-5444 (toll free)
(408) 863-4000 Cupertino, CA
|
(781) 676-2460 Lexington, MA
|
|
Europe, Middle East, Africa
|
+31 (0) 20-4546-200 Netherlands
|
+31 (0) 20-4545-201 Netherlands
|
support@europe.rational.com
|
|
|
|
|
support@apac.rational.com
|
Note: When you contact Rational Technical Support, please be prepared to supply the following information:
- Your name, telephone number, and company name
- Your computer's make and model
- Your operating system and version number
- Product release number and serial number
- Your case ID number (if you are following up on a previously-reported problem)
Please visit the Rational Web site for latest Release Notes, patches, and information: http://www.rational.com/.
Notice of Proprietary Rights
This computer program and documentation are confidential trade secrets and the property of Rational Software Corporation and its subsidiaries. Use, examination, reproduction, copying, disassembly, decompilation, transfer, and/or disclosure to others, in whole or in part, are strictly prohibited except with the express prior written consent of Rational Software Corporation and its subsidiaries.
Shared Microsoft Components Updated During The Rational Software Setup Procedure
The table below lists shared Microsoft components that are updated during the Rational Software setup procedure.
Table 2 Shared Microsoft Components Updated During the Rational Software Setup Procedure
|
|
|
|
|
|
Microsoft Data Access Objects 3.5
|
|
|
|
|
|
|
dao2535 .tlb
|
{COMMONFILESDIR}\Microsoft Shared\DAO
|
|
|
|
|
dao350 .dll
|
{COMMONFILESDIR}\Microsoft Shared\DAO
|
3.51.1608.0
|
xml:lang= en
|
Microsoft Data Access Objects 3.6
|
|
|
|
|
|
|
dao360 .dll
|
{COMMONFILESDIR}\Microsoft Shared\DAO
|
3.60.2521.8
|
|
Microsoft Data Access Components 2.1.2
|
|
|
|
|
|
|
mdac_typ . exe
|
{CDDIR}\patches
|
21.2.4202.3
|
lang= en
|
|
|
mdac_typ . exe
|
{CDDIR}\patches\0404
|
21.2.4202.3
|
lang=zh-TW
|
|
|
mdac_typ . exe
|
{CDDIR}\patches\ 0407
|
21.2.4202.3
|
lang= de
|
|
|
mdac_typ . exe
|
{CDDIR}\patches\040c
|
21.2.4202.3
|
lang= fr
|
|
|
mdac_typ . exe
|
{CDDIR}\patches\0410
|
21.2.4202.3
|
lang= it
|
|
|
mdac_typ . exe
|
{CDDIR}\patches\0411
|
21.2.4202.3
|
lang= ja
|
|
|
mdac_typ . exe
|
{CDDIR}\patches\0413
|
21.2.4202.3
|
lang=nl
|
|
|
mdac_typ . exe
|
{CDDIR}\patches\041d
|
21.2.4202.3
|
lang=sv
|
|
|
mdac_typ . exe
|
{CDDIR}\patches\0804
|
21.2.4202.3
|
lang=zh-CN
|
Microsoft ActiveX Components
|
|
|
|
|
|
|
axdist .exe
|
{CDDIR}\patches
|
4.71.30.1
|
lang=en
|
|
|
axdist .exe
|
{CDDIR}\patches\0404
|
4.71.30.1
|
lang=en
|
|
|
axdist .exe
|
{CDDIR}\patches\0407
|
4.71.30.1
|
lang=en
|
|
|
axdist .exe
|
{CDDIR}\patches\0411
|
4.71.30.1
|
lang=en
|
Microsoft Visual Basic 5 Service Pack 3
|
|
|
|
|
|
|
msvbvm50 .dll
|
{WINSYSDIR}
|
5.1.43.19
|
lang=en
|
Microsoft Visual C++ 5
|
|
|
|
|
|
|
msvcp50 .dll
|
{WINSYSDIR}
|
5.0.0.7022
|
lang=en
|
Microsoft Visual C++ 6 Service Pack 3
|
|
|
|
|
|
|
atl .dll os=win95
|
{WINSYSDIR}
|
3.0.8449.0
|
lang=en
|
|
|
atl .dll os=winnt
|
{WINSYSDIR}
|
3.0.8449.0
|
lang=en
|
|
|
mfc42 .dll
|
{WINSYSDIR}
|
6.0.8447.0
|
lang=en
|
|
|
mfc42loc .dll
|
{WINSYSDIR}
|
6.0.8267.0
|
xml:lang=de
|
|
|
mfc42loc .dll
|
{WINSYSDIR}
|
6.0.8168.0
|
xml:lang=en
|
|
|
mfc42loc .dll
|
{WINSYSDIR}
|
6.0.8267.0
|
xml:lang=fr
|
|
|
mfc42loc .dll
|
{WINSYSDIR}
|
6.0.8267.0
|
xml:lang=it
|
|
|
mfc42loc .dll
|
{WINSYSDIR}
|
6.0.8168.0
|
xml:lang=ja
|
|
|
mfc42loc .dll
|
{WINSYSDIR}
|
6.0.8267.0
|
xml:lang=nl
|
|
|
mfc42loc .dll
|
{WINSYSDIR}
|
6.0.8267.0
|
xml:lang=sv
|
|
|
mfc42loc .dll
|
{WINSYSDIR}
|
6.0.8168.0
|
xml:lang=zh-TW
|
|
|
mfc42loc .dll
|
{WINSYSDIR}
|
6.0.8168.0
|
xml:lang=zh-CN
|
|
|
msvcirt .dll
|
{WINSYSDIR}
|
6.0.8168.0
|
lang=en
|
|
|
msvcp60 .dll
|
{WINSYSDIR}
|
6.0.8168.0
|
lang=en
|
|
|
msvcrt .dll
|
{WINSYSDIR}
|
6.0.8397.0
|
lang=en
|
|
|
oleaut32 .dll
|
{WINSYSDIR}
|
2.40.4275.1
|
lang=en
|
|
|
stdole2 .tlb
|
{WINSYSDIR}
|
2.40.4275.1
|
lang=en
|
|
|
|
|
|
|
Microsoft Internet Explorer 4.0
|
|
|
|
|
|
|
comcat .dll
|
{WINSYSDIR}
|
4.71.1460.1
|
lang=en
|
|
|
msvcrt40 .dll os=win95
|
{WINSYSDIR}
|
4.10.0.6038
|
lang=en
|
|
|
msvcrt40 .dll os=winnt
|
{WINSYSDIR}
|
4.2000.0. 6172
|
lang=en
|
Microsoft Windows 98/Windows NT 4.0 Service Pack 4
|
|
|
|
|
|
|
msvcrt20 .dll
|
{WINSYSDIR}
|
|
lang=en
|
Microsoft Transaction Server
|
|
|
|
|
|
|
adme .dll
|
{WINSYSDIR}
|
1997.1.8. 205
|
lang=en
|
|
|
dtccm .dll
|
{WINSYSDIR}
|
1997.1.8. 205
|
lang=en
|
|
|
dtctrace .dll
|
{WINSYSDIR}
|
1.0.0.2
|
lang=en
|
|
|
dtcutil .dll
|
{WINSYSDIR}
|
1997.1.8. 205
|
lang=en
|
|
|
msdtcprx .dll
|
{WINSYSDIR}
|
1997.1.8. 205
|
lang=en
|
|
|
xolehlp .dll
|
{WINSYSDIR}
|
1997.1.8. 205
|
lang=en
|
Microsoft Windows Script 5.1
|
|
|
|
|
|
|
ste51 .exe
|
{CDDIR}\patches
|
4.72.2106.1
|
lang=en
|
|
|
ste51 .exe
|
{CDDIR}\patches\0404
|
4.71.1712.0
|
lang=zh-TW
|
|
|
ste51 .exe
|
{CDDIR}\patches\0407
|
4.72.2106.1
|
lang=de
|
|
|
ste51 .exe
|
{CDDIR}\patches\040c
|
4.71.1015.0
|
lang=fr
|
|
|
ste51 .exe
|
{CDDIR}\patches\0410
|
4.71.1015.0
|
lang=it
|
|
|
ste51 .exe
|
{CDDIR}\patches\0411
|
4.72.2106.1
|
lang=ja
|
|
|
ste51 .exe
|
{CDDIR}\patches\0413
|
4.71.1015.0
|
lang=nl
|
|
|
ste51 .exe
|
{CDDIR}\patches\041d
|
4.71.1015.0
|
lang=sv
|
|
|
ste51 .exe
|
{CDDIR}\patches\0804
|
4.71.1015.0
|
lang=zh-CN
|
Microsoft Visual Basic 5 Service Pack 3
|
|
|
|
|
|
|
implode .dll
|
{WINSYSDIR} shared=yes
|
1.0.0.1
|
lang=en
|
|
|
tlbinf32 .dll
|
{WINSYSDIR} shared=yes
|
1.1.81.69
|
lang=en
|
|
|
vb5db .dll
|
{WINSYSDIR} shared=core
|
6.0.81.69
|
lang=en
|
|
|
cmct2chs .dll
|
{WINSYSDIR}
|
6.0.80.22
|
lang=zh-CN
|
|
|
cmct2cht .dll
|
{WINSYSDIR}
|
6.0.80.22
|
lang=zh-TW
|
|
|
cmct2de .dll
|
{WINSYSDIR}
|
6.0.80.22
|
lang=de
|
|
|
cmct2fr .dll
|
{WINSYSDIR}
|
6.0.80.22
|
lang=fr
|
|
|
cmct2it .dll
|
{WINSYSDIR}
|
6.0.80.22
|
lang=it
|
|
|
cmct2jp .dll
|
{WINSYSDIR}
|
6.0.80.22
|
lang=ja
|
|
|
cmctlchs .dll
|
{WINSYSDIR}
|
6.0.80.22
|
lang=zh-CN
|
|
|
cmctlcht .dll
|
{WINSYSDIR}
|
6.0.80.22
|
lang=zh-TW
|
|
|
cmctlde .dll
|
{WINSYSDIR}
|
6.0.80.22
|
lang=de
|
|
|
cmctlfr .dll
|
{WINSYSDIR}
|
6.0.80.22
|
lang=fr
|
|
|
cmctlit .dll
|
{WINSYSDIR}
|
6.0.80.22
|
lang=it
|
|
|
cmctljp .dll
|
{WINSYSDIR}
|
6.0.80.22
|
lang=ja
|
|
|
cmdlgchs .dll
|
{WINSYSDIR}
|
6.0.81.63
|
lang=zh-CN
|
|
|
cmdlgcht .dll
|
{WINSYSDIR}
|
6.0.81.63
|
lang=zh-TW
|
|
|
cmdlgde .dll
|
{WINSYSDIR}
|
6.0.81.63
|
lang=de
|
|
|
cmdlgfr .dll
|
{WINSYSDIR}
|
6.0.81.63
|
lang=fr
|
|
|
cmdlgit .dll
|
{WINSYSDIR}
|
6.0.81.63
|
lang=it
|
|
|
cmdlgjp .dll
|
{WINSYSDIR}
|
6.0.81.63
|
lang=ja
|
|
|
comct232 .ocx
|
{WINSYSDIR}
|
6.0.80.22
|
lang=en
|
|
|
comctl32 .ocx
|
{WINSYSDIR}
|
6.0.80.22
|
lang=en
|
|
|
comdlg32 .ocx
|
{WINSYSDIR}
|
6.0.84.18
|
lang=en
|
|
|
dbgrdchs .dll
|
{WINSYSDIR}
|
1.0.0.126
|
lang=zh-CN
|
|
|
dbgrdcht .dll
|
{WINSYSDIR}
|
1.0.0.126
|
lang=zh-TW
|
|
|
dbgrdde .dll
|
{WINSYSDIR}
|
1.0.0.126
|
lang=de
|
|
|
dbgrdfr .dll
|
{WINSYSDIR}
|
1.0.0.126
|
lang=fr
|
|
|
dbgrdit .dll
|
{WINSYSDIR}
|
1.0.0.126
|
lang=it
|
|
|
dbgrdjp .dll
|
{WINSYSDIR}
|
1.0.0.126
|
lang=ja
|
|
|
dbgrid32 .ocx
|
{WINSYSDIR}
|
5.1.81.4
|
lang=en
|
|
|
dblist32 .ocx
|
{WINSYSDIR}
|
6.0.81.69
|
lang=en
|
|
|
dblstchs .dll
|
{WINSYSDIR}
|
6.0.81.63
|
lang=zh-CN
|
|
|
dblstcht .dll
|
{WINSYSDIR}
|
6.0.81.63
|
lang=zh-TW
|
|
|
dblstde .dll
|
{WINSYSDIR}
|
6.0.81.63
|
lang=de
|
|
|
dblstfr .dll
|
{WINSYSDIR}
|
6.0.81.63
|
lang=fr
|
|
|
dblstit .dll
|
{WINSYSDIR}
|
6.0.81.63
|
lang=it
|
|
|
dblstjp .dll
|
{WINSYSDIR}
|
6.0.81.63
|
lang=ja
|
|
|
mscc2chs .dll
|
{WINSYSDIR}
|
6.0.81.63
|
lang=zh-CN
|
|
|
mscc2cht .dll
|
{WINSYSDIR}
|
6.0.81.63
|
lang=zh-TW
|
|
|
mscc2de .dll
|
{WINSYSDIR}
|
6.0.81.63
|
lang=de
|
|
|
mscc2fr .dll
|
{WINSYSDIR}
|
6.0.81.63
|
lang=fr
|
|
|
mscc2it .dll
|
{WINSYSDIR}
|
6.0.81.63
|
lang=it
|
|
|
mscc2jp .dll
|
{WINSYSDIR}
|
6.0.81.63
|
lang=ja
|
|
|
mscmcchs .dll
|
{WINSYSDIR}
|
6.0.81.63
|
lang=zh-CN
|
|
|
mscmccht .dll
|
{WINSYSDIR}
|
6.0.81.63
|
lang=zh-TW
|
|
|
mscmcde .dll
|
{WINSYSDIR}
|
6.0.81.63
|
lang=de
|
|
|
mscmcfr .dll
|
{WINSYSDIR}
|
6.0.81.63
|
lang=fr
|
|
|
mscmcit .dll
|
{WINSYSDIR}
|
6.0.81.63
|
lang=it
|
|
|
mscmcjp .dll
|
{WINSYSDIR}
|
6.0.81.63
|
lang=ja
|
|
|
mscomct2 .ocx
|
{WINSYSDIR}
|
6.0.84.18
|
lang=en
|
|
|
mscomctl .ocx
|
{WINSYSDIR}
|
6.0.84.98
|
lang=en
|
|
|
mshfgchs .dll
|
{WINSYSDIR}
|
6.0.30.5
|
lang=zh-CN
|
|
|
mshfgcht .dll
|
{WINSYSDIR}
|
6.0.30.5
|
lang=zh-TW
|
|
|
mshfgde .dll
|
{WINSYSDIR}
|
6.0.30.5
|
lang=de
|
|
|
mshfgfr .dll
|
{WINSYSDIR}
|
6.0.30.5
|
lang=fr
|
|
|
mshfgit .dll
|
{WINSYSDIR}
|
6.0.30.5
|
lang=it
|
|
|
mshfgjpn .dll
|
{WINSYSDIR}
|
6.0.30.5
|
lang=ja
|
|
|
mshflxgd .ocx
|
{WINSYSDIR}
|
6.0.84.18
|
lang=en
|
|
|
msscrde .dll
|
{WINSYSDIR}
|
1.0.0.2521
|
lang=de
|
|
|
msscrfr .dll
|
{WINSYSDIR}
|
1.0.0.2521
|
lang=fr
|
|
|
msscript .ocx
|
{WINSYSDIR}
|
1.0.0.3715
|
lang=en
|
|
|
msscrit .dll
|
{WINSYSDIR}
|
1.0.0.2521
|
lang=it
|
|
|
msscrjp .dll
|
{WINSYSDIR}
|
1.0.0.2521
|
lang=ja
|
|
|
msstdfmt .dll
|
{WINSYSDIR}
|
6.0.84.50
|
lang=en
|
|
|
msvbvm60 .dll
|
{WINSYSDIR}
|
6.0.84.95
|
lang=en
|
|
|
mswcrchs .dll
|
{WINSYSDIR}
|
6.0.81.63
|
lang=zh-CN
|
|
|
mswcrcht .dll
|
{WINSYSDIR}
|
6.0.81.63
|
lang=zh-TW
|
|
|
mswcrde .dll
|
{WINSYSDIR}
|
6.0.81.63
|
lang=de
|
|
|
mswcrfr .dll
|
{WINSYSDIR}
|
6.0.81.63
|
lang=fr
|
|
|
mswcrit .dll
|
{WINSYSDIR}
|
6.0.81.63
|
lang=it
|
|
|
mswcrjp .dll
|
{WINSYSDIR}
|
6.0.81.63
|
lang=ja
|
|
|
mswcrun .dll
|
{WINSYSDIR}
|
6.0.84.50
|
lang=en
|
|
|
rchtxchs .dll
|
{WINSYSDIR}
|
6.0.80.37
|
lang=zh-CN
|
|
|
rchtxcht .dll
|
{WINSYSDIR}
|
6.0.81.63
|
lang=zh-TW
|
|
|
rchtxde .dll
|
{WINSYSDIR}
|
6.0.81.63
|
lang=de
|
|
|
rchtxfr .dll
|
{WINSYSDIR}
|
6.0.81.63
|
lang=fr
|
|
|
rchtxit .dll
|
{WINSYSDIR}
|
6.0.81.63
|
lang=it
|
|
|
rchtxjp .dll
|
{WINSYSDIR}
|
6.0.81.63
|
lang=ja
|
|
|
riched32 .dll xml:lang=en
|
{WINSYSDIR}
|
4.0.993.4
|
lang=en
|
|
|
riched32 .dll xml:lang=ja
|
{WINSYSDIR}
|
4.0.993.4
|
lang=ja
|
|
|
riched32 .dll xml:lang=zh-TW
|
{WINSYSDIR}
|
4.0.994.24
|
lang=zh-TW
|
|
|
riched32 .dll xml:lang=zh-CN
|
{WINSYSDIR}
|
4.0.994.24
|
lang=zh-CN
|
|
|
richtx32 .ocx
|
{WINSYSDIR}
|
6.0.84.18
|
lang=en
|
|
|
stdftchs .dll
|
{WINSYSDIR}
|
6.0.81.63
|
lang=zh-CN
|
|
|
stdftcht .dll
|
{WINSYSDIR}
|
6.0.81.63
|
lang=zh-TW
|
|
|
stdftde .dll
|
{WINSYSDIR}
|
6.0.81.63
|
lang=de
|
|
|
stdftfr .dll
|
{WINSYSDIR}
|
6.0.81.63
|
lang=fr
|
|
|
stdftit .dll
|
{WINSYSDIR}
|
6.0.81.63
|
lang=it
|
|
|
stdftjp .dll
|
{WINSYSDIR}
|
6.0.81.63
|
lang=ja
|
|
|
tabctchs .dll
|
{WINSYSDIR}
|
6.0.81.63
|
lang=zh-CN
|
|
|
tabctcht .dll
|
{WINSYSDIR}
|
6.0.81.63
|
lang=zh-TW
|
|
|
tabctde .dll
|
{WINSYSDIR}
|
6.0.81.63
|
lang=de
|
|
|
tabctfr .dll
|
{WINSYSDIR}
|
6.0.81.63
|
lang=fr
|
|
|
tabctit .dll
|
{WINSYSDIR}
|
6.0.81.63
|
lang=it
|
|
|
tabctjp .dll
|
{WINSYSDIR}
|
6.0.81.63
|
lang=ja
|
|
|
tabctl32 .ocx
|
{WINSYSDIR}
|
6.0.84.18
|
lang=en
|
|
|
vb6chs .dll
|
{WINSYSDIR}
|
5.0.81.69
|
lang=zh-CN
|
|
|
vb6cht .dll
|
{WINSYSDIR}
|
5.0.81.69
|
lang=zh-TW
|
|
|
vb6de .dll
|
{WINSYSDIR}
|
5.0.81.69
|
lang=de
|
|
|
vb6fr .dll
|
{WINSYSDIR}
|
5.0.81.69
|
lang=fr
|
|
|
vb6it .dll
|
{WINSYSDIR}
|
5.0.81.69
|
lang=it
|
|
|
vb6jp .dll
|
{WINSYSDIR}
|
5.0.81.69
|
lang=ja
|
|
|
asycfilt .dll
|
{WINSYSDIR}
|
2.40.4275.1
|
lang=en
|
|
|
ctl3d32 .dll os=win95
|
{WINSYSDIR}
|
2.31.0.0
|
lang=en
|
|
|
ctl3d32 .dll os=winnt
|
{WINSYSDIR}
|
2.31.0.0
|
lang=en
|
|
|
imagehlp .dll
|
{WINSYSDIR}
|
4.0.1381.4
|
lang=en
|
|
|
olepro32 .dll register=1
|
{WINSYSDIR}
|
5.0.4275.1
|
lang=en
|
|
|
psapi .dll
|
{WINSYSDIR}
|
4.0.1371.1
|
lang=en
|
Microsoft Java Virtual Machine 5.0.3234.0
|
|
|
|
|
|
|
msjavx86 .exe
|
{CDDIR}\patches
|
5.0.3234.0
|
lang=en
|
Microsoft Windows Sockets Library 2.0
|
|
|
|
|
|
|
ws2setup .exe
|
{CDDIR}\patches
|
4.71.30.1
|
lang=en
|
