SEARCH INSTRUCTIONS:  To go directly to a specific
section, use your editor's search utility and search on
"SECTION -#-" replacing the # with the appropriate section
number.


                        TABLE OF CONTENTS

SECTION 1     System Requirements
              A)   Minimum Installation
              B)   Full Installation

SECTION 2     Installing BC++ 4.0
              A)   Pre-Installation Notes
                   1)   Backup Disks
                   2)   Disk Compressions
                   3)   Upgrading
              B)   Installation Instructions
              C)   After Installation

SECTION 3     Minimum and Selected Installation Options
              A)   16-bit Command Line Minimum Install
              B)   32-bit Command Line Minimum Install
              C)   16-bit IDE Minimum Install
              D)   32-bit IDE Minimum Install
              E)   DOS Only Minimum Install 

SECTION 4     Win32 Install Issues
              A)   Explanation of Win32s
              B)   Adding Win32s To Your System
              C)   Removing Win32s From Your System

SECTION 5     Troubleshooting - Install Issues
              A)   Data Integrity or Bad Section Errors
              B)   Disk Full or Insufficient Disk Space 
                   Errors
              C)   GP Fault or Unhandled Exception Errors
             
SECTION 6     Troubleshooting - Run Time Problems
              A)   Out of Memory Errors
              B)   GP Fault or Unhandled Exception Errors
              C)   Turbo Debugger for Windows
         
SECTION 7     Modifications the Install Program Makes to 
              Your System
              A)   Standard Installation
              B)   Win 32s Setup Program

SECTION 8     Icons in the BC++ Group Window
              A)   Creating a Program Group Window for BC++
              B)   List of Executable Files that each Icon 
                   Calls
              C)   Brief Description of What Each Icon Does

SECTION 9     LAN Windows Configuration

SECTION 10    How to Get A Technical Information Document
              A)   From DLBBS
              B)   From TechFax

SECTION 11    On-line Documents
              A)   Documents in BC4\BIN Directory
              B)   Documents in BC4\DOC Directory

SECTION 12    Boot Clean




SECTION -1-  SYSTEM REQUIREMENTS
    
Before installing BC++ 4.0 please review the minimum 
system requirements listed below:

A) Minimum Installation

4 MB Extended Memory
Intel 386 or higher
DOS 4.01 or later
Windows 3.1 or later
approx 20 MB hard disk space
3.5" High Density Disk Drive or CD ROM Drive

IF YOUR SYSTEM DOES NOT MEET THESE MINIMUM REQUIREMENTS, 
THEN YOU WILL NOT BE ABLE TO INSTALL AND RUN BC++ 4.0 FOR 
WINDOWS.

B) Full Installation (16-bit/32-bit capability):

8 MB system memory
Intel 386 or higher
DOS 4.01 or later
Windows 3.1 or later
Win32s (included in BC++ 4.0)
approx 80 MB hard disk space
3.5" High Density Disk Drive or CD ROM Drive
 
NOTE: On a compresed hard disk the installation process may 
need additional hard disk space.  If you are using a disk 
compression utility, refer to Section 2, part A.


SECTION -2-  INSTALLING BC++ 4.0

A) Pre-Installation Notes

1) Backup Disks:

Before installing BC++ 4.0 make backup copies of your 
original disks using the DOS DISKCOPY command. You must 
use the same disk size and media (density) when you make 
your backup set of disks.  Attempting to copy from 3.5" 
to 5.25" will cause the install program to fail. If you 
have a bad disk contact Borland's Disk Replacement line at 
(800) 621-3132. 

2) Disk Compression:

If you are using a disk compression utility (such as
Stacker[tm], DoubleSpace[tm], XtraDrive[tm], SuperStor[tm],
etc.) the estimated available hard disk space reported may 
not be sufficient to install the product.  During 
installation, BC++ 4.0 copies compressed files onto your 
hard disk.  Disk compression utilities report available 
hard disk space assuming that the files copied onto the 
disk can be compressed. Since the files that are copied by 
the installation program are already compressed, the disk 
compression utility cannot compress them any further.  To 
address this issue, you may need to free up additional hard 
disk space for the installation.  

3) Upgrading:

It is recommended that you remove all previous versions of
Borland C++, including files and directories, from your 
hard drive before installing BC++ 4.0.  If you must keep a 
previous version of Borland C++ on your system, please 
consult Technical Information Document number 1736.  For 
information on how to receive this document, refer to 
Section 10.   
        
B) Installation Instructions:

1. Boot Clean

It is highly recommended that you boot clean before 
installing BC++ 4.0.  Booting your system with a clean 
configuration will eliminate any potential software 
conflicts that may arise during installation.  Refer to 
Section 12 for instructions on how to boot clean.

2. Insert the BC++ 4.0 installation disk into drive A or B.

3. If you are at the DOS prompt type WIN A:INSTALL (or WIN
B:INSTALL) and press ENTER.  If you are in Windows choose
File|Run from Program Manager and type:

A:INSTALL (or B:INSTALL).

4. Select installation options from the install menu for
Destination and Working directories.  

The "Borland C++ Destination Directory" is the directory in 
which BC++ 4.0 will be installed.  

The "Borland C++ Working Directory" is the working 
directory where temporary files are expanded during 
installation. 

The "Windows Directory" is the directory where Windows is 
located.  This path cannot be edited.
        
The "Install WIN32s" option will install WIN32s.  Refer to 
Section 3 for more information.

The "Create Borland C++ Group" option will create a program 
group in Windows for you with all the BC++ 4.0 icons.  
Refer to Section 8 for more information.

The "LAN Windows Configuration" option is useful when you 
are installing BC++ 4.0 onto a network. This option will 
place support files, which would normally be installed into 
the local Windows directory, into the network BC4\BIN 
directory.  Refer to Section 9 for more information.

The "Customize Installation" button allows you to
customize the installation of BC++ 4.0.

The "Installation requires" section is the amount of KB 
required to install the options you have chosen.

The "Available" section is the amount of KB you currently 
have available on the drive specified as the Destination 
Directory.

5. Choose INSTALL to begin installation. If problems arise 
during installation, note any error messages and refer to 
Section 5.

C) After Installation:

1. After the install has completed, the README file will 
appear.  The README file contains important information 
about configuring and using BC++ 4.0, including late 
changes which may have occurred after the manuals were 
printed.

2. The option to install Win32s extensions to Windows 3.1 
is provided by Microsoft for 32-bit applications.  Refer to
Section 4 for more information. 
          
3. Exit Windows and modify your CONFIG.SYS so that files 
and buffers are set to at least 40.  Example:

FILES=40
BUFFERS=40          

BC++ 4.0 will automatically modify your AUTOEXEC.BAT file 
by adding to your path statement the BC++ 4.0 bin 
directory.  Example:

PATH C:\BC4\BIN;C:\;C:\DOS;C:\WINDOWS 

4. To launch the Integrated Development Environment (IDE),
double click on the BCW icon in the Borland C++ program
group window.  If the IDE does not appear, note the error
message(s) and refer to Section 6.


SECTION -3-  MINIMUM AND SELECTIVE INSTALLATION OPTIONS

This section outlines the minimum and selective install 
options available for BC++ 4.0.
     
A) 16-bit Command Line Minimum Install (9 MB Hard Disk)

Borland C++ Tools:

16-bit Target Command Line Tools        4800 KB 

Borland C++ Libraries:

16 & 32-bit RTL Header Files            2120 KB

Borland C++ Libraries - Windows RTL Options:

16-bit Small Library                    1408 KB
16-bit DLLs                              208 KB

B) 32-bit Command Line Minimum Install (13 MB Hard Disk)

Borland C++ Tools:

32-bit Target Command Line Tools        5064 KB

Borland C++ Libraries:

16 & 32-bit RTL Header Files            2120 KB
32-bit Specific RTL Header Files         744 KB

Borland C++ Libraries - Windows RTL Options:

32-bit Library                          4568 KB
32-bit DLLs                              392 KB

C) 16-bit IDE Minimum Install (26 MB Hard Disk)

Borland C++ Tools:

IDE                                    22104 KB

Borland C++ Libraries:

16 & 32-bit RTL Header Files            2120 KB
32-bit Specific RTL Header Files         744 KB

Borland C++ Libraries - Windows RTL Options:

16-bit Large Library                    1432 KB
16-bit DLLs                              208 KB
    
D) 32-bit IDE Minimum Install (30 MB Hard Disk)

Borland C++ Tools:

IDE                                    22104 KB

Borland C++ Libraries:

16 & 32-bit RTL Header Files            2120 KB
32-bit Specific RTL Header Files         744 KB

Borland C++ Libraries -  Windows RTL Options:

32-bit Library                          4568 KB
32-bit DLLs                              392 KB

E) DOS Only Minimum Install (8 MB Hard Disk)

Borland C++ Tools:

16-bit Target Command Line Tools        4800 KB 

Borland C++ Libraries:

16 & 32-bit RTL Header Files            2120 KB

Borland C++ Libraries - DOS RTL Options:

DOS Large Library                        488 KB


SECTION -4-  WIN32s INSTALL ISSUES
  
A) An Explanation of Win32s

Win32s is a subset of Windows NT.  It allows 32-bit 
programs to run under Windows 3.1 (16-bit) by simulating a 
32-bit operating system.  If you are using Windows 3.1, 
these extensions (provided by Microsoft) are required to 
run 32-bit applications created with BCW.  Please note that
you will need a minimum of 8 MB of memory to run Win32s. If 
you plan to create 32-bit applications, you must install 
these extensions. If you are unsure, and you have 8 MB of 
memory, install Win32s. The Win32s extensions will not 
affect the normal operation of Windows 3.1.

B) Adding Win32s to your system

If you haven't installed BC++ 4.0 yet, make sure you check 
the "Install WIN32s" option on the install program.  

If you have already installed BC++ 4.0, without Win32s on 
your system, insert disk 1 in your A: drive.  Run Windows 
and then choose File/Run/a:setup.      

C) Removing Win32s from your system

1. Exit Windows.  Change to the Windows directory on your 
   hard drive.  

2. Edit the SYSTEM.INI file and remove the line in the 
   [386Enh] section that reads:

   device=C:\WINDOWS\SYSTEM\WIN32S\W32S.386

   (The actual path in the above line may be different to 
    reflect your specific configuration.)

3. Change to the WINDOWS\SYSTEM directory. 
  
4. Remove the following files:

     WIN32S.INI
     W32SYS.DLL
     WIN32S16.DLL

5. Change to the WINDOWS\SYSTEM\WIN32S directory. 

6. Delete all the files in the WINDOWS\SYSTEM\WIN32S 
   directory.

7. Change back to the WINDOWS\SYSTEM directory and remove 
   the WIN32S subdirectory.

Win32s has now been removed from your system.
                                             

SECTION -5-  TROUBLESHOOTING - INSTALL PROBLEMS

This section explains common errors encountered during
installation.  System configuration and software conflicts 
may cause the installation process to fail.  If the 
installation fails, boot your system clean to eliminate any 
possible software conflicts.  Refer to Section 12 for 
instructions on how to boot clean.  If booting clean does 
not solve the problem, or you encounter a problem not 
mentioned here, contact Borland Technical Support.

A) Data Integrity or Bad Sector on Disk Errors

If you receive either one of these error messages, then you 
need to get a replacement disk set.  Contact Borland's Disk 
Replacement Line at (800-621-3132). 

B) Disk Full or Insufficient Disk Space Errors

You could get either one of these errors if there is 
insufficient hard disk space available to install BC++ 4.0.
Here are some suggestions:

1.  Boot your system with a clean configuration.  Refer to 
Section 12 for instructions on how to boot clean.

2.  Make sure your system meets the minimum installation 
requirements.  Refer to Section 1 for a list of the minimum
installation requirements.

3.  Run Windows in standard mode (win /s).  During a
Windows-hosted installation process, a swap file is used to
simulate extra memory while running Windows.  This only 
happens if you are running Windows in 386 Enhanced Mode and 
have virtual memory (under control panel) turned on. While 
Windows is running, the temporary swap file can grow 
dynamically thereby using up hard disk space.  Starting 
Windows in standard mode (win /s) before installing will 
prevent this from happening.
                                 
C) GP Fault/Unhandled Exception 

GP Fault or Unhandled Exception errors can occur for a 
variety of reasons.  Possible reasons for these errors are 
explained in Technical Information Document number 649.  
Refer to Section 10 for instructions on how to obtain this 
document.  Here are a few suggestions for solving these 
errors:

1. Use the original installation diskettes.
																									 
2. Make sure your system meets the minimum requirements. 
Refer to Section 1 for a list of the minimum installation
requirements.

3. Boot your system with a clean configuration.  Refer to 
Section 12 for instructions on how to boot clean.

4. Run Windows in standard mode (win /s) to eliminate swap 
file usage.

5. Turn off Disk Caching and Video/Shadow RAM in CMOS.  
Refer to the documentation for your computer.


SECTION -6-  TROUBLESHOOTING - RUN TIME PROBLEMS

This section describes common errors encountered when 
trying to use BC++ 4.0.  System configuration and software 
conflicts may cause BC++ 4.0 to fail.  If BC++ 4.0 fails, 
you should boot your system clean to eliminate any possible 
software conflicts.  Refer to Section 12 for instructions 
on how to boot clean.  If booting clean does not solve the 
problem or you encounter a problem not mentioned here, 
contact Borland Technical Support.
  
What is DPMI and how is it important?

DPMI stands for DOS Protected Mode Interface and it 
provides reliable extended memory allocation when the 
processor is in protected mode. Many of the tools provided 
in BC++ 4.0 require the use of a 32-bit DPMI server in 
order to run. Because of this, a DPMI server must be 
installed on your system, or sufficient extended memory 
must be available at runtime so BC++ 4.0 can load an 
internal DPMI server.  

DPMI services are provided by many popular memory managers 
such as QEMM386 and 386MAX. These programs can be 
configured to install DPMI services when the memory manager 
is installed. When running a DPMI-hosted program like 
BC++ 4.0, be sure to use a version 0.9 or better server 
that supports virtual memeory. 

If you do not have a memory manager that provides DPMI 
services, then BC++ 4.0 will load its own internal server. 
However, in order to do this, you must have enough extended 
memory (not expanded) to allow the server to load. 4MB RAM 
is usually enough to allow the server to load. If you are 
getting "Out of Memory" errors, then some other program is 
using your extended memory. Read the "Out of Memory" 
section below for details on how to address this issue.

A)   Out of Memory

If you are getting "Out of Memory" errors, it is quite 
possible that you have exhausted your extended (or XMS) 
memory pool. This is especially true if you only have 2MB 
available extended RAM and do not have a memory manager 
that provides virtual memory.   

BC++ 4.0 comes with a utility called MAKESWAP.EXE. This 
utility will provide virtual memory for the DPMI server. 
You will need to allocate space on your hard disk that is 
proportional to the amount of virtual memory you desire.  
For example if you want to add 8MB of virtual memory, then 
you will need to set aside 8MB of space on your hard disk. 

To use MAKESWAP, type:

MAKESWAP x

where x is the number of kilobytes you want to allocate. 
For example, MAKESWAP 8000 will create an 8MB swap file in 
the current directory called EDPMI.SWP for use by 
Borland C++ command line tools.  To enable the swap file, 
use the DPMIMEM environment variable by issuing the 
following command at the DOS prompt:

  set DPMIMEM=SWAPFILE <location of swap file>\EDPMI.SWP

For example, if you typed MAKESWAP 8000 in the C:\BC4\BIN\
directory, then you would type the following:

set DPMIMEM=SWAPFILE C:\BC4\BIN\EDPMI.SWP

You may want to add this line to your AUTOEXEC.BAT file if 
you use it often.  You MUST use this utility if you only 
have 2MB of available RAM with no memory manager that 
provides virtual memory.  Note that you must clear this 
environment variable by issuing the command:

set DPMIMEM=

before running other 16-bit DPMI-hosted executables.

B) GP Fault/Unhandled Exception/System Hang 

GP Fault or Unhandled Exception errors can occur for a 
variety of reasons including:  not enough memory available, 
not enough hard disk space available, conflicts with 
optimizations set in the CMOS, and software conflicts.  
Technical Information Document numbers 649 and 1328 address 
these issues.  Refer to Section 10 for information on how 
to obtain this document.

C) Turbo Debugger for Windows 

Should you experience any strange behavior from the Turbo 
Debugger, such as a garbled screen or a system hang upon
execution or exit, it is possible that your video card or 
mode is not supported by the video DLL that is being 
loaded.  Changing the video DLL should eliminate the 
problem.  

Double clicking on the icon "TD Video Configuration" 
(hereafter referred to as TDWINI) will bring up the utility 
for changing the video DLL.  You can also test the 
effectiveness of the current video DLL with this utility.  
If you follow the instructions here and in the help 
document for TDWINI but are still experiencing a problem 
with the video test, another video DLL should be used.  If 
the video test appears to be working, the problems you are 
experiencing with the Debugger may not be related to the 
video mode.  At this point you may wish to contact Borland 
Technical Support.  

For instructions on using TD Video Configuration refer to 
the TDWINI help.  To access the help utility, click on the 
help button from inside the TD Video Configuration.

SECTION -7-  MODIFICATIONS THE INSTALL PROGRAM MAKES TO 
             YOUR SYSTEM

This section describes the files that are added by the 
install program to your Windows directory and modifications 
that are made to the Windows configuration files.

A) Standard Installation

Files changed in the Windows directory:

WIN.INI modifications:
          [Extensions]
added:    IDE=BCW.EXE^.IDE
          
PROGMAN.INI modifications:
          [Settings]
changed:  Order= 1 6 7 2 3 4 5
          [Groups]
added:    Group6=C:\WINDOWS\BCW40.GRP
          Group7=C:\WINDOWS\WIN32APP.GRP

SYSTEM.INI modifications:
changed:  drivers=mmsystem.dll winmm16.dll
          [386Enh]
          device=C:\WINDOWS\SYSTEM\WIN32S\WIN32S.386
          device=C:\BC4\BIN\WINDPMI.386
          device=C:\BC4\BIN\TDDEBUG.386


Files added to WINDOWS directory:
HELP.ICO 
BORHELP.INI 
WINHELP.INI 
TDW.INI 
SYSTEM.OLD 
BCW.INI 
BCW40.GRP 
WIN32APP.GRP
MAIN.GRP 
ACCESSOR.GRP 
GAMES.GRP 
STARTUP.GRP 
APPLICAT.GRP 

Files added to the WINDOWS\SYSTEM directory:
OLECLI.W31
OWL.INI
CTL3D.DLL
CTL3D32.DLL
BW320007.DLL
BW320009.DLL
BW32000C.DLL
BWCC32.DLL 
BWCC.DLL
BWCC0007.DLL 
BWCC0009.DLL
BWCC000C.DLL
WIN32S.INI
WIN32S16.DLL
OLECLI.DLL
W32SYS.DLL
WINMM16.DLL

Files added to the WINDOWS\SYSTEM\WIN32S directory (with
installation of Win32s)
ADVAPI32.DLL
COMDLG32.DLL
GDI32.DLL
KERNEL32.DLL
LZ32.DLL
MPR.DLL
NTDLL.DLL
CRTDLL.DLL
OLECLI32.DLL
OLESVR32.DLL 
SHELL32.DLL
USER32.DLL
VERSION.DLL
W32S.386
W32SKRNL.DLL
WIN32S.EXE
WINSPOOL.DRV
NETAPI32.DLL
WSOCK32.DLL
SCK16THK.DLL
WINMM.DLL
C_1252.NLS
C_850.NLS
C_437.NLS
UNICODE.NLS 

           
SECTION -8-  ICONS IN THE BC++ GROUP WINDOW

A) Creating a Program Group Window for BC++ 4.0. 

If the Borland C++ Program Group Window did not appear
after installation you can create one by choosing one of
the following options:

1. Generating icons by downloading the BC4GRPS.ZIP file

 a. If you need help on downloading refer to Section 10 of
    this document.

 b. Now at the DOS prompt type in: PKUNZIP BC4GRPS.ZIP

 c. It will then uncompress the files, and there will be a
    readme.txt file that was expanded. Inside the readme 
    file are intructions on using the BC4GRPS.EXE program 
    to get the icon groups to appear.

2. Manually creating the icons:

 a. Load Windows

 b. Choose File|New|Program Group and click on OK.

 c. Type the name you want for the program group window in 
    the	"Description:" text box, such as Borland C++.

 d. You may leave "Group File" line blank and Windows will 
    create one for you. So, click on the OK button and a 
    new Window should appear.

 e. Choose File|New|Program Item to create icons for the 
    Windows programs and click on OK.

 f. Select one of the Windows executable programs to create 
    an icon for, such as BCW.EXE. Type in the name of that 
    executable program in the Description text box.

 g. Type the full pathname to this executable in the 
    Command Line text box.  Entering a pathname for the 
    working directory is optional.  The default is the 
    WINDOWS directory.  Click OK.  The icon will appear in 
    the active program group window.

 h. Repeat steps e-g for every single executable program 
    for which you wish to make an icon.

B) List of executable files that each icon calls:

Borland C++:                 \BC4\BIN\BCW.EXE
Turbo Debugger for Win32:    \BC4\BIN\TD32.EXE
TD32 Configuration:          \BC4\BIN\TD32INST.EXE
TD Video Configuration:      \BC4\BIN\TDWINI.EXE
Turbo Debugger for Windows:  \BC4\BIN\TDW.EXE
TDW Configuration:           \BC4\BIN\TDWINST.EXE
Remote Debugging:            \BC4\BIN\WREMOTE.EXE
Remote Setup:                \BC4\BIN\WRSETUP.EXE
Turbo Debugger for DOS:      \BC4\BIN\TD.EXE
TD Configuration:            \BC4\BIN\TDINST.EXE
WinSpector:                  \BC4\BIN\WINSPCTR.EXE
WinSight:                    \BC4\BIN\WINSIGHT.EXE
FConvert:                    \BC4\BIN\FCONVERT.EXE
Workshop:                    \BC4\BIN\WORKSHOP.EXE
Hot-Spot Editor:             \BC4\BIN\SHED.EXE
Win32s Reference:            \BC4\BIN\WIN32S.HLP
Multimedia Reference:        \BC4\BIN\WIN31MWH.HLP
MCI Reference:               \BC4\BIN\MCISTRWH.HLP
Hot-Spot Reference:          \BC4\BIN\SHED.HLP
Windows Socket Reference:    \BC4\BIN\WINSOCK.HLP
BCW and Library Reference:   \BC4\BIN\BCW.HLP
ObjectWindows Reference:     \BC4\BIN\OWL.HLP
Windows API Reference:       \BC4\BIN\BWINAPI.HLP
Resource Workshop Reference: \BC4\BIN\WORKHELP.HLP
Winsight Reference:          \BC4\BIN\WINSIGHT.HLP
Winspector Reference:        \BC4\BIN\WINSPCTR.HLP
Creating Help:               \BC4\BIN\CWH.HLP
Master Index:                \BC4\BIN\MINDEX.HLP


C) Brief Description of what each icon does

1. Borland C++ 

This icon launches Borland's Integrated Development
Environment (IDE).  From within the IDE, you can edit,
compile, and run C or C++ programs.

2. Turbo Debugger for Win32

This icon launches the 32-bit debugger.

3. TD32 Configuration

This icon launches the configuration utility for Turbo
Debugger for Win32.

4. TD Video Configuration

This icon launches the configuration utility that allows
you to configure the Debugger to run with your video card.

5. Turbo Debugger for Windows

This icon launches the Turbo Debugger for Windows
(16-bit).

6. TDW Configuration

This icon launches the configuration utility for Turbo
Debugger for Windows.

7. Remote Debugging

This icon launches the Remote Debugger.

8. Remote Setup

This icon launches the configuration utility that allows
you to configure your system to do remote debugging.

9. Turbo Debugger for DOS

This icon launches the DOS Turbo Debugger.

10. TD Configuration

This icon launches the configuration utility for Turbo
Debugger for DOS.

11. WinSpector

This icon launches WinSpector.  WinSpector will assist you
in performing a post-mortem examination of  Unrecoverable
Application Errors (UAE) or General Protection Errors.

12. WinSight

This icon launches the program that gives you debugging
info about Windows classes, windows, and messages.  Using
WinSight, you can study how any application creates
classes and windows, and monitor how Windows sends and
receives messages.  WinSight is a passive observer:  it
intercepts and displays info about messages, but does not
prevent messages from getting to applications.

13. FConvert

This icon launches the utility to convert text files from
OEM to ANSI format or vice versa.

14. Workshop

This icon launches Resource Workshop.  Resource Workshop is
a sophisticated tool that integrates the entire process of
designing, editing, and compiling resources for
applications. Resources are data that define the visible
portions of your Windows program (i.e. icons, bitmaps,
dialog boxes, etc.).

15. Hot-Spot Editor

This icon launches the Hot-Spot Editor.  The Hot-Spot
Editor is used to create and edit a bitmap that includes
one or more hotspots.  A hotspot can link to Help topics
or run Help macros when clicked on.  Using Hot-Spot
Editor, you can assign hotspots to a bitmap and assign
attributes to each hotspot.  These bitmap files generally
have a .SHG filename extension.

16. Win32s Reference

This icon launches the on-line reference for Microsoft's
Win32 Application Programming Interface (API).    

17. Multimedia Reference

This icon launches the on-line reference for the
Multimedia Application Programming Interface (API) of
Windows 3.1.  The Multimedia API includes the functions,
messages, and data structures you can use to create
multimedia applications for Windows.

18. MCI Reference

This icon launches the on-line reference for the Media
Control Interface (MCI).  MCI is a high-level command
interface to multimedia devices and resource files.

19. Hot-Spot Reference

This icon launches the on-line reference for the Hot-Spot
Editor.

20. Windows Socket Reference

This icon launches the on-line reference for Open Interface
for Network Programming under Microsoft Windows.  Windows
Sockets is an independent specification which defines a
network programming interface for MS Windows. 

21. BCW and Library Reference

This icon launches the on-line reference for Borland C++
for Windows.

22. ObjectWindows Reference

This icon launches the on-line reference for
ObjectWindows.

23. Windows API Reference

This icon launches the on-line reference for Windows API.

24. Resource Workshop Reference

This icon launches the on-line reference for Resource
Workshop.

25. Winsight Reference

This icon launches the on-line reference for WinSight.

26. Winspector Reference

This icon launches the on-line reference for WinSpector.

27. Creating Help

This icon launches the on-line reference documents that
tell you how to create an on-line Help system using the
Microsoft Windows 3.1 Help compiler and application called
"WinHelp".

28. Master Index

This icon launches the master index to all of the printed
manuals that come with BC++ 4.0.


SECTION -9-  LAN WINDOWS CONFIGURATION

BC++ 4.0 provides a LAN Windows Configuration option
during installation. This option is very useful when you
plan to install BC++ 4.0 to a network. Because BC++ 4.0
requires access to several support files at run time, the
LAN Windows Configuration will centralize the location of
these files to a location on the network rather than
requiring multiple copies of these files to be on each
machine that may run BC++ 4.0.

Specifically this option will place the following files:
BWCC.DLL, TDDEBUG.386, TDW.INI, CTL3D.DLL, CTL3D32.DLL in
the BC4\BIN subdirectory instead of the WINDOWS directory
on the installing machine.

Because of this change, you MUST make sure that the
BC4\BIN subdirectory appears in each path on each machine
that will run BC++ 4.0. For example, if you installed BC++
4.0 to the network drive W:, then each machine that will
run BC++ 4.0 should have W:\BC4\BIN in its path. 

Please note that simply selecting the LAN Windows
Configuration option WILL NOT automatically setup BC++ 4.0
to work on a network. Additional configuration adjustments
will also have to be made to your system. To find out more
about network installations, obtain Technical Information
Document number 806.  Refer to Section 10 on how to obtain
this document.


SECTION -10-  HOW TO GET A TECHNICAL INFORMATION DOCUMENT

Technical Information Documents provide valuable
information that can be used as reference materials. There
are two ways to obtain a Technical Information Document.

A)  Download the document from Borland's DLBBS 
(408) 431-5096, CompuServe, Genie, or BIX through a modem 
to your computer. Below are steps to download a Technical
Information Document from the Borland DLBBS.

The communication settings of your modem are automatically
detected, so no special setup is required.  However, if
you encounter any difficulties connecting to the service,
set your modem to 8 data bits, no parity, and 1 stop bit
(8-N-1).  The Download BBS supports modem speeds up to
14,400 bps.

For proper display, your communication software should
provide ANSI terminal support.  Most packages provide
VT-100 terminal emulation, which is fine for the DLBBS. If
you are using a Windows based package, select a screen
font (such as:  Terminal) that includes extended ASCII
characters.

Once connected, you will be prompted to enter your first
and last names and a password.  If you have not used the
service before, you will be asked to verify your name and
then answer a few questions.  Then the menu-driven system
will guide you through the various product and file
areas.  You will always receive a list of options when you
are prompted to make any choice.

Maneuvering the Main Menu

The Main menu shows the product whose files you can
currently access.  At the Main menu, enter "F" to move to
the Files menu.

Downloading Files

Once you know the name of the file you want to download,
enter "D" for download at the File menu.  When prompted,
enter the full name of the file or files.  All Technical
Information Documents have the form "TI#.ZIP".  Replace
the # with the appropriate document number.   For example,
to download Technical Information Document number 649, the
full name of the file would be TI649.ZIP.

When you have listed all of the files to download, press
<Enter> on a blank line.  You have the option to
automatically disconnect after the last downloaded file. 
Next, select the transfer protocol appropriate to your
communication software. (You will not be prompted if you
have selected a default protocol.)  The DLBBS is now ready
to send the file.  Initiate the download routine for your
communication software to start the file transfer.  If you
do not know the protocol or download keys to press, refer
to your telecommunications manual.

Working with Downloaded Files

Most of the files on the Download BBS are stored and
transferred in an archived (compressed) format and will
need to be unarchived before they can be used.  If you do
have the unarchiving utility PKUNZIP v.204G or greater,
then download PKZ204G.EXE from the DLBBS and execute it. 
You will recieve PKUNZIP and PKZIP utilities.  To
unarchive the file, enter the name of an unarchive utility
(UNPACK, UNZIP or PKUNZIP) and then the name of the
archived file.  Example:

PKUNZIP TI649.ZIP

B)  Download the document from Borland's TechFax Service. 
Call (800) 822-4269 from a touch-tone phone.  When
prompted, enter your FAX number, then enter the document
number you wish to receive.  The document will be faxed to
you shortly.

Here is a list of common Technical Information Documents:

    * 3       General Catalog of All Documents Available
    * 649     General Protection Faults
    * 1171    Problem Report Form
    * 1010    Installing and Configuring BC++
    * 806     Network Installations
    * 738     Memory Corruption
    * 1561    Clean Boot

SECTION -11-  ON-LINE DOCUMENTS

Here is a list of the on-line information and help
documents available with BC++ 4.0:

A) These files are located in the \BC4\BIN directory and
can be viewed by invoking WINDOWS and following these
steps:

1. Choose File|Run from Program Manager. 
2. Enter the pathname to the file you wish to view.  
Example: C:\BC4\BIN\BCW.HLP

BCW.HLP = BC++ 4.0 Help (help for new features as well as
          other essentials)
BWINAPI.HLP = Windows API for BC++ 4.0 (new Borland 
              function calls for Win32)
CTL3D.HLP = Adding 3-D Effects to Controls
CWH.HLP = Creating Windows Help
HELPEX.HLP = Creating Windows Help: Examples
HELPREF.HLP = Sample Main Window (Sample Topic x_topic1)
MC.HLP = Message Compiler (MC.EXE) for Windows NT
MCINSTRWH.HLP = MCI (Media Control Interface) Command 
                Strings Content 
MINDEX.HLP = Master Help Index to the BC++ 4.0 Manuals
OWL.HLP = Owl for BC++ 4.0 Help (Using Object Windows 2.0)
PENAPIWH.HLP = Pen API Reference
SHED.HLP = Using Hot Spot Editor
TDWINI.HLP = TDWINI.EXE Information (Video Configuration 
             Utility for Turbo Debugger for Windows)
WIN31MWH.HLP = Windows 3.1 Multimedia Reference
WIN32S.HLP = Win32s 1.1 Programmer's Reference
WINSIGHT.HLP = WinSight Help
WINSOCK.HLP = Windows Sockets (An Open Interface for 
              Network Programming Under Microsoft Windows)
WINSPCTR.HLP = WinSpector Help  
WORKHELP.HLP = Resource Workshop 4.0 Help

B) These files are located in the \BC4\DOC directory
and can be viewed with any text editor.

ASMDEBUG.TDW = Turbo Debugger for Windows (Assembly-level 
               debugging)
BWCCAPI.RW = Technical Description of Borland Windows 
             Custom Controls (BWCC)
BWCCSTYL.RW = Presentation of style considerations for 
              using BWCC dialog boxes
COMPAT.TXT = How to use OWL 1.0, TV 1.0x, and Paradox 
             Engine and Database Frameworks with BC++ 4.0
CUSTCNTL.RW = Creating Custom Control Classes
H2ASH.TSM = on-line Documentation for H2ASH (converter 
            utility for .ASH and .H files)
HDWDEBUG.TDW = Turbo Debugger for Windows Using the 
               Hardware Debugging Features
HELPME!.TDW = Turbo Debugger for Windows tips and hints
HELPME!.TSM = Turbo Assembler 3.1 Manual Reference and 
              Corrections
HELPME!.TXT = General information about a number of topics 
              involving programming and using Borland Tools
HINTS.TDW = Turbo Debugger for Windows Tips and Techniques
INTLDEMO.TXT = International API information and sample 
               program
MANUAL.OWL = changes to ObjectWindows 
PE.TXT = Portable executable format information
RESFMT.TXT = Win32 binary resource format information
TCREF.TSM = The source module cross-reference utility
TD_ASM.TXT = Information about Assembler-level debugging
TD_HDWBP.TXT = Using the Turbo Debugger hardware debugging 
               features
TD_HELP!.TXT = Turbo Debugger Tips and Hints
TD_RDME.TXT = Any last minute Turbo Debugger information
TD_UTILS.TXT = Turbo Debugger utilities reference
UTIL.DOC = Documentation of BC++ 4.0 standalone utilities
UTILS.TDW = Turbo Debugger Utilities Reference


SECTION -12-  BOOT CLEAN

This section describes the process of "booting clean" on
IBM PC's and compatible computers with DOS and/or windows.
This document assumes you have MS-DOS version 5.00 or
higher.

"Booting Clean" is the process of booting without loading 
device drivers and TSRs that can cause memory conflicts. 

These device drivers and TSRs are usually loaded in two
files- AUTOEXEC.BAT and CONFIG.SYS typically located on
the root directory of your hard disk (C:\).  The safest
method of booting clean is to create a "bootable" floppy
disk in drive A:. See the "Making a Boot Disk" section
below.

If you are using a program that runs under Microsoft
Windows, then you may need to make changes to some Windows
configuration files in order to ensure a "clean system
configuration" under Windows. The two files you will need
to examine are WIN.INI and SYSTEM.INI. These files are
located in the WINDOWS subdirectory on your hard disk. The
changes that you will need to make to these files (if any)
are outlined below. 

Clean Boot for DOS 6.0

Dos 6.0 allows you to change your system configuration
without editing any files by pressing the F5 key when
rebooting your computer.  First, reboot your computer, and
as soon as you see the "Starting MS-DOS. . ." message (try
to predict it), press and hold the F5 key until you get
the message "Bypassing system files. . .". You may get a
few extra @ symbols and beeps.  If this is the case,
simply release the F5 key and press ENTER. Now you have
the option of confirming each CONFIG.SYS and AUTOEXEC.BAT
command one at a time.  Following the instructions for DOS
5.0 Clean Boot you can identify which commands to keep
without having the extra steps of creating a boot disk
and/or editing your system configuration files.


Making a Boot Disk

In order to make a bootable floppy disk, follow the
instructions below:  (Do not type the double quotes)

NOTE: These instructions assume that your hard disk is C:
and your DOS and WINDOWS subdirectories appear on this
disk. (Most cases)

     1) Place a blank disk in drive A:
     2) type "C:"
     3) type "cd \dos" (go to your DOS subdirectory)
     4) type "format a: /s" (format the disk)
     5) type "BOOT DISK" for your volume label 
        (format process)
     6) Ensure that the format process completed correctly. 
        If not, obtain another disk and repeat steps 3 and 
        4.
     7) type "copy himem.sys a:"
     8) type "copy edit.com a:"
     9) type "cd \" (go to your root directory of your boot 
        disk)
    10) type "copy command.com a:"

At this point you now have a bootable floppy disk
containing an ASCII editor (EDIT.COM) and a high memory
driver (HIMEM.SYS).  Using EDIT, ensure your AUTOEXEC.BAT
and CONFIG.SYS look like one of the configuration choices
below. 

Your "clean" system configuration should be exactly like
one of the choices below except replace "<Insert REQUIRED
drivers here>" with any required drivers.  The ONLY
required drivers are, for example, disk compression and/or
hard disk access drivers.  This does not include mouse
drivers and disk caching utilities such as SmartDrive.

Clean Configuration #1: DOS 5.0 and DOS 6.0 running Windows
-----------------------------------------------------------

1) Insert your "bootable floppy" in drive A:
2) type "A:"
3) At the A> prompt type "edit CONFIG.SYS"
4) Type in the following:

          <Insert REQUIRED drivers here>
          DEVICE=HIMEM.SYS
          FILES=40
          BUFFERS=40

4) Exit the editor (Alt-F, then X, then Y)
5) Type "edit AUTOEXEC.BAT"
6) Type in the following:

          <Insert REQUIRED drivers here>
          PATH=C:\WINDOWS;C:\DOS;C:\BC4\BIN
          PROMPT $P$G

7)  Exit the editor (Alt-F, then X, then Y)
8)  type "C:"
9)  type "CD \WINDOWS"
10) type "copy WIN.INI WIN.BAK"
11) type "copy SYSTEM.INI SYSTEM.BAK"
12) type "edit WIN.INI"
13) Make sure that the "load=" and "run=" lines in your
    WIN.INI file look like the following:
          ------------
          [windows]
          spooler=yes
          load=
          run=
          Beep=yes
          ------------
12) Exit the editor (Alt-F, then X, then Y)
13) type "edit system.ini"
14) Ensure that your "shell=" line in your SYSTEM.INI file
    looks like the following:
          ------------
          [boot]
          shell=progman.exe
          ------------
15) Exit the editor (Alt-F, then X, then Y)
16) Make sure your "Bootable floppy" is in drive A: and
    reboot your computer.


Final Notes

At this point you should have a pretty good idea what is
causing the difficulty you were experiencing, or you have
completed the installation. Now you will probably want to
revert back to your original system configuration. This is
easy since you made a bootable floppy. Simply remove the
floppy from the floppy drive and restore your windows
configuration (if applicable) by following these
instructions:

1)   type "C:"
2)   type "CD \WINDOWS"
3)   type "copy windows.bak windows.ini"
4)   type "copy system.bak system.ini"

Reboot your computer. You have now restored your original
system configuration.
