VAC++ V4.0 -  Win2000 TempFix
-----------------------------

This package consists of a temp fix to enable applications generated
with VisualAge C++ Version 4.0 for Windows, to execute on Windows 2000.
There were certain cases where a behaviour change in the operating system
caused a problem when manipulating menus.  This problem has been corrected
in this tempfix.

The code included in this package has undergone only minimal testing.
IBM advises users to install this package only if they have experienced
a Win2000 problem.


There are 2 zip files that you could have chosen from:

1.  tus1opt.zip
    -   Optimized dll's and libs used for everyday development and
        distribution.
        space required: 25.4 meg

2.  tus1deb.zip
    -   Debug dll's and libs used only when you want to debug open class
        source code.  NOTE:  These files take over 5 times more space than
        the optimized versions.  You should only use these dll's if you
        installed the source and plan to debug the open class classes.
        space required: 138.5 meg


FILES CONTAINED IN tus1opt.zip
---------------------------------

   readme.txt           - this file
   lib/cppobi40.lib
   lib/cppobs40.lib
   lib/cppoui40.lib
   lib/cppous40.lib
   runtime/cppobi40.dll
   runtime/cppoui40.dll



FILES CONTAINED IN tus1deb.zip
---------------------------------

   readme.txt           - this file
   lib/cppobi40.lib
   lib/cppobs40.lib
   lib/cppoui40.lib
   lib/cppous40.lib
   runtime/cppobi40.dll
   runtime/cppoui40.dll



INSTALLING THIS FixPack
-----------------------

1. Stop running all programs that use the VAC++ dll's.  If not sure
   then stop running all applications.

2. Download tus1opt.zip into a temporary directory. (normal debugging case)
   -OR-
   Download tus1deb.zip into a temporary directory. (special debugging case)
   (only use the debug dll's if you are planning to debug into
    open class source).

3. IMPORTANT: backup the files listed above.  This temp fix is a
   replacemnt fix.  If you encounter problems, you will need to
   restore the previous files.

4. Unzip the files into one of the following areas:

    a.  if using opt dll's from ppk1opt.zip then unzip into the
        base directory of where VAC++ was installed.

        For example, if VAC++ was installed in D:\ibmcppw, use a command
        similar to the following:

        unzip -u tus1opt.zip -d D:\ibmcppw

    -OR-

    b.  if using debug dll's from ppk1deb.zip then unzip into the
        source directory of where VAC++ source was installed.

        For example, if VAC++ source was installed in D:\ibmcppw\iocsrc, use
        a command similar to the following:

        unzip -u tus1deb.zip -d D:\ibmcppw\iocsrc

5. You may need to reboot to cause the changes to take effect.


KNOWN ISSUES
------------

1. If you are using the VAC++ V3.6 debugger to debug your exe within
   the V4.0 environment within Win2000 then you may encounter a
   debugger termination or other behaviour.
   IBM is aware of the problem and is investigating.


IF YOU ENCOUNTER PROBLEMS
-------------------------

If you have a service contract with IBM, you may create a problem report
using your regular channels.  These PMRs will be treated as sev 3 problems
and may or may not be fixed within another temp fix.  Otherwise, you can
reach IBM by posting a comment at
news://news.software.ibm.com/ibm.software.vacpp.openclass.