IBM VisualAge C++ Professional for Windows NT, Version 4.0 - Fixpak 1 -------------------------------------------------------------------- IBM VisualAge(R) C++ Professional for Windows NT(R), Version 4.0 (C) Copyright IBM Corporation 1991, 1998 - All Rights Reserved. (C) Copyright IBM Corp and another 1991, 1998 - All Rights Reserved. (C) Copyright Microsoft Corp. 1985, 1996 - All Rights Reserved. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. ------------------------------------------------------------------------ To install this Fixpak perform the following steps : (1) Unzip the Fixpak into a temporary directory. The unzipped Fixpak occupies just less than 33M bytes. (2) Make sure you are currently in the directory into which the fixpak was unzipped. (3) Issue the following command : SETUP (4) If you are installing this Fixpak in Silent mode do the following: (a) If you are applying it to an XCOPYed LAN image, edit the file "setup.iss" by changing the 15th line from "szDir=h:\vacppCD" to "szDir=drive:\dir" where 'drive' is the drive letter and 'dir' is the directory where the LAN image is to be found. (b) Issue the command "SETUP -S" If you have the Technology Preview components installed you will also need to download and install the TechPreview fixes : (1) Down the file fp1-tp.zip (2) Unzip the file into the ibmcppw40\bin directory ----------------------------------------------------------------------- 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 Fixpak level must be equal to or greater than the previously installed level (if any). Note that Fixpaks are cumulative. (3) If you had XCOPYed the CD image to a LAN drive, you can apply this Fixpak to the LAN drive. (4) 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. ------------------------------------------------------------------------ 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. ------------------------------------------------------------------------