home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 29 Fixes_o
/
29-Fixes_o.zip
/
ctw308.zip
/
read.me
< prev
next >
Wrap
Text File
|
1997-07-29
|
12KB
|
268 lines
------------------------------------------------------------------------
This Fixpak is provided as a set of files. To install this Fixapk perform the
following steps :
(1) Unzip this Fixpak to an empty directory (i.e. f:\ibmcsd). If you are using
PKUNZIP*, use -d, to have the files unzipped into directories. Do not unzip
into a directory with a blank in its name.
(2) Change the current directory to the directory containing service.exe.
(3) ENSURE THAT YOU HAVE AT LEAST 5 MB OF FREE SWAPPER SPACE, BEFORE
PROCEEDING.
(4) Issue the following command :
SERVICE
This Fixpak may be installed to any disk accessible to your system,
including LAN drives. The service program itself must run within an
OS/2 2.11 or later session.
(5) If you performed a basic install, you will be asked if you want to
backup the previous version. You may choose to do this or not, but
you SHOULD NOT ATTEMPT TO RESTORE THE PREVIOUS LEVEL, using the
Installation Utility - Restore Action. If problems occur, you should
delete and re-install the component.
(6) YOU ARE REQUIRED TO REBOOT YOUR MACHINE AFTER INSTALLING THIS FIXPAK.
This Fixpak updates SMARTS projects. You can verify the update went successfully,
by viewing the CPPINST.LOG in the directory you installed the product into.
If you apply this Fixpak, you will also need to apply the Visual Builder
Fixpak, CTV304.ZIP. If you do not, the Project Smarts "Visual Builder
application" will not work correctly.
------------------------------------------------------------------------
The following conditions must exist for Fixpak installation to be successful:
(1) You must have already installed the IBM VisualAge C++ for OS/2 product
via a basic install from CD-ROM, diskette or from a server to which the
CD-ROM/diskettes were copied to. You can also install this FIxpak to a
server to which the CD-ROM install image was copied to.
Users who have performed a shared install will have to delete and re-install
this product from their workstation, once this Fixapk has been applied to
the server.
(2) No IBM VisualAge C++ for OS/2 tools can be open in any session when you
install the Fixpak. If the copy of the product being serviced resides
on a LAN drive, you must ensure that no other LAN user has any of these
files open.
(3) Make sure that the directory for this Fixapk contains only the files from
this Fixpak. If other files are present, it may cause the installation to
fail. It would best to unpack the Fixpak ZIP file into an empty directory.
------------------------------------------------------------------------
This Fixpak applies fixes to the WorkFrame/2 component of the
IBM VisualAge C++ for OS/2 product.
A list of the fixes contained in this Fixpak can be found in the file
CTW308.LST. The fixes are cumulative, meaning that this Fixpak contains
all fixes described in CTW304.LST.
The complete list of files in this Fixpak can be found in the file
SERVICE.LST.
======================================================
Read me for FixPak Level 8 (FixPak 8) of WorkFrame/2 V3.0
======================================================
Install instructions:
=====================
Since CTW302, NMAKE version 3.000.013 has been included in the FixPak
package, but not installed. It is now installed by the SERVICE program
over the original version in the BIN directory. If you have replaced
the original version of NMAKE and do not want version 3.000.013 for
reasons such as those mentioned in the CTW302 section below, then
you must make a backup copy of your version and use it to replace
version 3.000.013 after applying SERVICE. If you are running NMAKE
from a different directory, then follow the instructions for CTW302
below.
======================================================
Read me for CTW304 of WorkFrame/2 V3.0
======================================================
Install instructions:
=====================
In order to activate the fix for the problem where MakeMake generates an
incomplete make file when many dependencies are present, you must add the
following statement to your CONFIG.SYS file:
SET _IWF.MMDEPBUFSIZE=n
where n is the number of bytes the dependency buffer should be. How big
this number should be depends on the number of dependencies you have, and
if you are using long names for those dependencies. If this variable is not
specified or the number is less than 2,000, the buffer size will default to
2,000 bytes (which is the current size of the dependency buffer). Based on
this, you can calculate how big this buffer should be by counting how many
dependencies are processed by MakeMake today, and dividing that result by
the number of actual dependencies, and multiplying by 2,000.
For example, you calculate that you need a dependency buffer of 10,000
bytes. The statement in the CONFIG.SYS file would look like this:
SET _IWF.MMDEPBUFSIZE=10000
After installing this CSD, you must reboot your machine for the changes
in this CSD to take affect.
Prequisites
===========
None, other than those listed below.
------------------------------------------------------------------------
Read me for CSD Level 3 of WorkFrame/2 V3.0
===========================================
Install instructions:
=====================
After installing this CSD, you must reboot your machine for the changes
in this CSD to take affect.
If you currently have VisualAge for COBOL installed on your machine, there
are special instructions you may need to follow, depending on how these
products were installed on you machine:
A. If you installed VisualAge for COBOL AFTER installing VisualAge for C++,
then you need to modify your CONFIG.SYS file in the following way for the
WorkFrame CSD to take affect in VisualAge for C++:
1. Modify your LIBPATH, PATH, DPATH, HELP, and BOOKSHELF variables so that
any directory name containing "IBMCPP" is moved ahead of any directory
name containing "IBMCOBOL".
2. Reboot you machine so that the changes can take affect
B. If you installed VisualAge for COBOL BEFORE installing VisualAge for C++,
then you do not need to do perform any additional tasks for the changes
to take affect.
C. In either case you will need to modify the "COBOL GUI Designer Master
Project":
1. Open (double click on) the VisualAge COBOL icon
2. Open (double click on) the Works folder
3. Open (double click on) the COBOL GUI Designer Master Project
4. Click on the 'View' pulldown menu
5. Click on the 'Tools Setup' menu item
6. Expand (click on the '+') the EDIT action class
7. Right mouse click on the 'Edit' action
8. Select the 'Change...' menu item from the pop-up menu
9. Select the 'Support' tab at the bottom of the notebook
10. In the Action Support DLL group box change the
'Entrypoint' from DEFAULT to EDIT (by selecting EDIT
in the drop-down list box).
11. Press OK
12. If needed expand (click on the '+') the EDIT action class again
13. Double click on the 'Edit' action
14. Insure that the parameters field contains:
/CM WF INIT %d %f %p
15. Press OK and you're all done
Prequisites
===========
CSD CTW303 requires that CSD CTO304 or later must be installed. This CSD
contains part of the fix for the Project Smarts window size problem.
OS/2 Warp FixPak 22 must be also be installed. This FixPak contains
part of the fix for the problems concerning failures invoking LPEX by
double clicking on errors in the monitor window.
================================================================================
The following is from the read me file for CSD CTW302, and must
followed by all VisualAge for C++ users who have not previously
applied CTW302.
CSD CTW302 requires NMAKE version 3.000.013 or later in order for Builds
to function correctly in projects which have multiple source directories.
This version of NMAKE is available in this CSD package, but not installed
as part of the SERVICE exec. You may use this copy or get a copy from
another source, such as the OS/2 Developer Connection 10 CDs.
Before using this copy of NMAKE, you must first determine the current
level of your existing NMAKE. Run NMAKE without any makefile or options
specified from the command line. Check the version line that is output
by NMAKE.
If the Version line starts with "Version 2.0..." then you are using NMAKE
that came with the OS/2 2.1 Toolkit. Do NOT replace this version of NMAKE
with version 3.000.013. NMAKE version 3.000.013 is NOT compatible with the
OS/2 2.1 Toolkit, and the error we describe above does not occur with NMAKE
version 2.
If the Version line indicates that the NMAKE version is included in the
range of 3.000.000 to 3.000.012, then you must replace NMAKE.EXE with the
one provided here or the one in DevCon 10. NMAKE.EXE will be in one of
two places on your machine:
1. In the TOOLKT30\BIN directory - this means you installed NMAKE as part
of the Warp Toolkit, which you obtained separately from VisualAge C++.
2. In the IBMCPP\BIN directory - this means you installed NMAKE as part of
VisualAge C++.
In either case, replace NMAKE.EXE in this directory with the one we provide
or with the one found on the DevCon 10 CDs.
If the Version line indicates that the NMAKE version you are currently using
is 3.000.013 or greater, then you do not have to do anything; the NMAKE version
you are already using is correct.
================================================================================
The following is from the read me file for CSD CTW301, and must
followed by all VisualAge for C++ users who have not previously
applied CTW301.
After applying CTW302 and rebooting, please make the following
change:
MakeMake has been changed in CTW301 so that it will now generate a
make file which will cause all intermediate and target files
generated by the make (like object files, for example) to be
placed in the project's working directory. Before CTW301,
all intermediate and target files were (wrongly) being output
into the source directory. In spite of this change, however,
there is still a problem with the Resource Compiler action.
The default options for the Resource Compiler action puts the target
.RES file in the same directory as the source .RC file, regardless of
the working directory set for the project. If the working directory
is not the same as the source directory containing the .RC file, then
the make file generated by MakeMake will fail as it looks for the .RES
file in the working directory.
To fix this problem, you will need to change the options
for the Resource Compiler action. Change the Resource Compiler
options in the default VACPP project (in \IBMCPP\MAINPRJ) so
that it will apply to all your projects that inherit from it.
The default Resource Compiler options are currently set to
"%q%n.RES". You need to changed this to ".\%n.RES" so that the
correct make file will be generated by MakeMake. Follow these
steps to accomplish this:
1) Through the Drives folders, find your VACPP project in
the \MAINPRJ\VACPP subdirectory. Open the project.
2) Go to the Tools Setup window of the default project.
2) Expand the Compile action.
3) Right mouse click on the Resource Compiler icon.
and select the "File Options->Change" menu selection
5) In the Parameters field, change "%q" to ".\"