VisualAge C++ Beta Debugger
             ---------------------------

Disclaimer of liability
------------------------
This debugger program is provided 'AS IS'.  There is no warranty
or service implied with respect to the program.

The availability of this debugger does not imply that this or a
similar debugger will be included in future IBM product offerings.


Features of this debugger
-------------------------
The debugger (B_IDBUG.EXE) has a similar interface to the VisualAge
for C++ for OS/2 Version 3.0 debugger.
Remote debugging support has been added which allows you to remotely
debug a program running on another computer.  This is useful for
debugging GUI programs as the debugger GUI does not interfere with
the GUI of the program being debugged.
See the online help for information on how to do remote debugging.
(Help -> Help index -> remote debugging)
You will need to run B_RMTDBG.EXE instead of the IRMTDBG.EXE that the help
says to use.

The "Message Queue" and "Window Analysis" monitors have been removed from
the debugger.  There is a stand-alone utility (B_MQWA.EXE) that replaces
the message queue monitor.


Build level
-----------
HV3980212


Installation instructions
-------------------------
1. Create a new directory for the debugger (e.g. C:\DEBUGGER)
2. Unzip the beta debugger zip file, preserving directory structure
3. Add the following to config.sys variables
    - C:\DEBUGGER\BIN  to PATH
    - C:\DEBUGGER\HELP to HELP
    - C:\DEBUGGER\HELP to DPATH
    - C:\DEBUGGER\DLL  to LIBPATH


Prerequisites
-------------
  - You must be running OS/2 V3 or later.
  - You must have VisualAge C++ for OS/2 V3.0 installed in order to use
    this debugger.
  - You need TCP/IP installed in order to use the remote debugging feature
    of the debugger.


Support
-------
Support is provided on a best-effort basis.  Newer versions of this
debugger with bug fixes may be made available at a future time.
Please report all problems, questions, suggestions, and so on to
VisualAge C++ Support.  They will be forwarded to the appropriate
personnel for consideration for future versions of the program.
Please indicate that you are using the beta debugger and give the
build number (see above) in your report.

Please include a complete description of the problem as well as a small
(up to 100 lines if possible) testcase that demonstrates the problem.


Enjoy,

Your IBM Debugger Development Team