IBM VisualAge C++ Professional for OS/2 (R), Version 4.0  Fixpak 1- README
-----------------------------------------------------------------------------------------------------------------------------------------------

IBM VisualAge(R) C++ Professional for OS/2(R), Version 4.0 Fixpak
  (C) Copyright IBM Corporation 1991, 1998 - All Rights Reserved.

  US Government Users Restricted Rights - Use, duplication or disclosure
  restricted by GSA ADP Schedule Contract with IBM Corp.

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


Trademarks

The following terms are trademarks of International Business Machines
Corporation in the United States or other countries or both:

    IBM
    Open Class
    OS/2
    VisualAge


Contents
========

This Fixpak 1 is divided into two parts.  Part 1 is mandatory which includes fixes to the 
core components.  Part 2 is optional, which includes IOC source, samples and tech preview.

To install this Fixpak perform the following steps :

(1) Unzip the Fixpak into a temporary directory. The unzipped Fixpak 
    occupies less than 90M bytes for Part 1 and less than 245M bytes for Part 2.

(2) Make sure you are currently in the directory into which the Fixpak
    was unzipped.

(3) Issue the following command :

      INSTALL

(4)  (a) If you are installing this Fixpak locally, select "Install Fixpak 1 locally" from the 
       Install Selection menu.  The Fixpak install will overwrite the installed files only if the 
       time stamp of the installed files are older.
       (b) If you are installing this Fixpak to an XCOPYed LAN image, select "Install Fixpak 1 to 
       CD image on LAN drive" from the Install Selection menu.  The install will ask you for the
       location of IBM VisualAge C++.  Both the drive and the path of the target CANNOT be empty.  
       All the files in the Fixpak will overwrite the CD image files, however, the time stamp of the fixed
       files will not be updated when IBM VisualAge C++ is installed.


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


The following conditions must exist for Fixpak installation to be
successful:

 (1) No IBM VisualAge C++ Professional tools can be open in any
     session when you install the Fixpak.

 (2) The Feature Installer Runtime must be installed on the system.  Since this is 
      a prerequisite for installing the IBM VisualAge C++ product please refer to the
      install.txt of the product for the installation notes of the Feature Installer Runtime.

 (3) The Fixpak level must be equal to or greater than the previously
     installed level (if any). Note that Fixpaks are cumulative.

 (4) If you had XCOPYed the CD image to a LAN drive, you can apply
     this Fixpak to the LAN drive.  

 (5) If you are operating from a CD/Network install, the Fixpak
     must first be applied to the LAN image, and then applied to the
     local machine.
    
 (6) IBM VisualAge C++ and the Fixpak must be in the same language.

 (7) If the installation is not completed successfully, a Feature Installer object VACFP1 
       may remain in the {BootDrive}\OS2\install directory.  Remove the object before restarting 
       the Fixpak install.


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


The following section identifies known problems or limitations for applications executing on OS/2
Warp Server 4.

IBM Open Class
The ITabControl class is not supported on OS/2 Warp Server 4.   If you are building applications for
both the OS/2 Warp 4 and OS/2 Warp Server 4 environments, you should use the INotebook class.

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

Note to Those Including Parts in their Configuration Files

You should note that the frequent segmentation violations that
occurred with the GA version of the product no longer occur.  However, 
it should be noted that two builds may be required when a part
is changed:  the first build after changing a part will generate the
source code reflecting the changes to the part but the source changes
will not be compiled as part of the first build; the second build is
required to incorporate the changed source code.  If one generates the
part source from within the Visual Builder before doing a build then
only one build will be required.

------------------------------------------------------------------------