Information regarding TDWIN.DLL and Windows 3.1 Compatibility
=============================================================

Borland will support Windows 3.1 for its full line of Windows
language products: Borland C++ & Application Frameworks, Borland C++,
Turbo C++ for Windows, and Turbo Pascal for Windows.  Windows 3.1
compatibility kits will be available for these products in Q292.
The compatibility kits will include all the files you need
to create and target Windows 3.0 and Windows 3.1 applications,
including the lib's, dll's, .h and .tpu files for multimedia, pen,
true type and OLE support.  The kits will also include online help
for the 3.1 API and example files.

We are working very aggressively on creating these compatibility
kits.  Because they require final shipment of the Windows SDK from
Microsoft, we are unable to supply these files at this time.  As you
are well aware, software often changes at the last moment, and thus
we need to make sure that our compatibility kits work with the retail
and SDK versions that Microsoft will ship.

You may run into some difficulties with Turbo Debugger for Windows
when used in conjunction with the Windows 3.1.  These issues will be
addressed in the compatibility kit.  Most of the problems you experience
are solved by simply using a Borland provided DLL called TDWIN.DLL in place
of WINDEBUG.DLL as a temporary solution.  That file is included in this
archive.  It has been released by Borland AS IS and should be considered a
temporary solution to the issue of using Turbo Debugger for Windows under
Windows 3.1.  Borland's "true" solution to Windows 3.1 compatibility issues
is the compatibility kit described above.  Until that solution becomes
available, you may use TDWIN.DLL without guarantee.

Using TDWIN.DLL will resolve the majority of problems experienced when
running TDW 3.0 or TDW 2.5 under Windows 3.1.  It will NOT work with
the Windows 3.1 debugging kernel.  You may experience other problems while
using this temporary solution.

To use TDWIN.DLL:
        - make a backup copy of your WINDEBUG.DLL onto a floppy
        - make sure that there are no copies of WINDEBUG.DLL on your path,
          in the WINDOWS directory, or in the WINDOWS/SYSTEM directory.
        - rename TDWIN.DLL to WINDEBUG.DLL and place it
          into the BIN directory of your Borland product.
        - you now should be able to run Turbo Debugger for Windows under
          Windows 3.1 (not 100% compatible)

We thank you for your commitment to Borland products.
We will update you as soon as more information on the Windows 3.1
compatibility kits is available.