                         INSTALL.TXT
                         ===========

SEARCH INSTRUCTIONS FOR NOTEPAD.EXE:  To go directly to a 
specific section, search for "SECTION -#-" replacing the # 
with the appropriate section number.

                       TABLE OF CONTENTS

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

SECTION 2     Installation Notes
              A)   Before Installing
              B)   After Installing

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     Win32s 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)   Install Program Terminates Prematurely
              C)   Disk Full or Insufficient Disk Space 
                   Errors
              D)   GP Fault or Unhandled Exception Errors
             
SECTION 6     Troubleshooting - Run-Time Problems
              A)   Resource Workshop Requires BWCC 2.0 and Above
              B)   Unable to Locate Required .DLLs
              C)   Fatal Error in Display
              D)   Out of Memory Errors
              E)   GP Fault or Unhandled Exception Errors
              F)   Turbo Debugger for Windows
              G)   Borland Example Fails
         
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 for each Icon 
                   and a description of what it does

SECTION 9     LAN Windows Configuration

SECTION 10    How to Get A Technical Information Document
              A)   From TechFax
              B)   From Bulletin Boards
              
SECTION 11    Boot Clean


SECTION -1-  SYSTEM REQUIREMENTS

Before installing BC++ 4.02 please review the minimum 
system requirements listed below:

A) Minimum Installation (no IDE)

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

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.02)
        approximately 80 MB hard disk space
        3.5" High Density Disk Drive

NOTE: On a compressed hard disk the installation process
might need additional hard disk space. If you are using
a disk compression utility, refer to Section 2, Part A4.


SECTION -2-  INSTALLING BC++ 4.02

A) Before Installing

IMPORTANT!
Do not install Borland C++ 4.02 files over previously installed 
Borland C++ directories. The files in this distribution will 
not work with previously shipped tools and libraries.  This 
is particularly true for configuration files from previous 
shipping releases, like TDCONFIG.TDW and BCCONFIG.BCW.

Also, be especially careful when using object files and libraries
from Borland C++ 3.1 with binaries created with this release. 
There are several potential problems when linking with old 
objects or libraries.  Exceptions won't work correctly 
(destructors won't get called) when a pre-BC4 stack frame is 
unwound due to an exception. See the "New Compiler and Linker 
Switches" and "NOEHxx Libraries" sections for more information.

Do not use long file names when installing under Windows NT.

For a faster install, you may wish to turn off screen savers.

1. Installing Borland C++ 4.02 on your hard disk:
   a. Select File|Run from Windows 3.1, Windows for Workgroups 3.1x,
      or Windows NT.
   b. Enter A:INSTALL (or B:INSTALL) on the input line.
   c. You have the option of not installing Win32s, which should be
      turned off if you are installing under Windows NT.
   d. Fill in directories as appropriate, and INSTALL will create
      appropriate Windows groups, install Win32s, and install the
      new Borland C++ 4.02 software.

   To use the built-in transfer tools and Help, make sure their 
   location is in your path (the \BIN directory for Borland C++ 
   4.02).

2. Boot Clean:

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

3. Backup Disks:

   If you wish to make backup copies of your original disks 
   use 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. 

4. 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 might not be sufficient to install the
   product. During installation, BC++ 4.02 copies compressed
   files onto your hard disk. 

5. Upgrading:

   If you will be using OWL 1 or Turbo Vision 1, you must keep
   the source code for ClassLib, TV, and OWL 1 on your computer
   so that you can rebuild them with BC++ 4.02.  The following
   Technical Information documents may be helpful (see Section 11
   for information on how to acquire a TI):
       
       OWL 1:  1750, 1751, 1754
       TV 1:   1752,1753
       
   Remove the previous version of BC++ from your PATH statement
   in your AUTOEXEC.BAT.  For other upgrading issues (especially
   with regard to the Paradox Engine), please see the file
   BC4\DOC\COMPAT.TXT.

6. Network Installation:

   If you are installing BC++ 4.02 on a network, you may wish
   to consult Technical Information Document number 1738.  For
   information on how to receive this document, refer to 
   Section 10.

7. Norton Desktop For Windows (NDW):

   If you have Norton Desktop running on your system and
   have the Auto Arrange Icons option turned off,
   the BC++ 4.02 program icons may appear to be on top
   of each other once the installation process is
   complete.

8. Hard drive Installation:

   If you have about 35 megabytes of hard drive space in 
   addition to what is required for the installation of
   BC++ 4.02, you may want to install the product from your
   hard drive.  The primary advantage of a hard drive installation
   is speed:  expect to halve the time it takes to install
   as compared to an installation from floppy disks.  To
   install from hard drive, make a temporary directory and then
   XCOPY each disk into that directory.  Then, run the INSTALL.EXE
   from the temporary directory rather than from the installation
   disk.

9. Installing Under Windows NT or OS/2:

   The install will fail if you enter any paths that use long 
   file names (such that the names would be illegal in the DOS
   FAT file system).

B) After Installing:

1. The README file contains important information about
   configuring and using BC++ 4.02, including late changes
   which might have occurred after the manuals were printed.

2. Borland provides the Microsoft setup program to install 
   Win32s.  These libraries are used to run 32-bit Windows 
   applications on Windows 3.1.  Refer to Section 4 for more 
   information.

3. Exit Windows and verify your CONFIG.SYS so that the 
   FILES setting is set to at least 40. This should have
   been done by the installation process.  Example:

          FILES=40

   BC++ 4.02 automatically modifies your AUTOEXEC.BAT file
   by adding to your path statement the BC++ 4.02 bin 
   directory. Example:

          PATH C:\BC4\BIN;%PATH%

   Your original AUTOEXEC.BAT file is saved as AUTOEXEC.BOR. 

4. To launch the Integrated Development Environment (IDE),
   double click 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.02.

When choosing a selective installation, the first thing
to decide is what platform(s) you want to install support
for; after choosing from among "DOS," "16-bit Windows,"
or "32-bit Windows," you will then be able to choose which
specific tools you want installed.  For example, after 
selecting "DOS" and "16-bit Windows," if you choose to
install the Turbo Debugger, both TD.EXE and TDW.EXE will
be installed, but not TD32.EXE.

Note that the actual disk space required for an
installation will vary depending upon the size of the
target disk partition.  For example, on a 255 MB partition,
a full installation requires 80468 kilobytes, while on a 1 GB
partition, the required space is 102000 kilobytes.  Please be
sure to check the "space required" at the final dialog box in
the install program.  This will properly account the for varying
partition sizes.

A) 16-bit Command-line Minimum Install (10 MB Hard Disk Space)

   Configuration:          Custom
   Targets:                16-bit Windows, DOS
   Borland C++ Tools:      Command-line Tools, Run-time Libraries
   Borland C++ Run-time Libraries:
                           Header files, Static Libraries,
                           Dynamic Libraries, Large

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

   Configuration:          Custom
   Targets:                32-bit Windows
   Borland C++ Tools:      Command-line Tools, Run-time Libraries
   Borland C++ Run-time Libraries:
                           Header Files, Static Libraries,
                           Dynamic Libraries, Large

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

   Configuration:          Custom
   Targets:                16-bit Windows, DOS
   Borland C++ Tools:      Visual Tools, Run-time Libraries
   Borland C++ Visual Tools:
                           Integrated Development Environment (IDE)
   Borland C++ Run-time Libraries:
                           Header Files, Static Libraries,
                           Dynamic Libraries, Large
   
D) 32-bit IDE Minimum Install (24 MB Hard Disk)

   Configuration:          Custom
   Targets:                32-bit Windows
   Borland C++ Tools:      Visual Tools, Run-time Libraries
   Borland C++ Visual Tools:
                           Integrated Development Environment (IDE)
   Borland C++ Run-time Libraries:
                           Header Files, Static Libraries,
                           Dynamic Libraries, Large

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

   Configuration:          Custom
   Targets:                DOS
   Borland C++ Tools:      Command-line Tools, Run-time Libraries
   Borland C++ Run-time Libraries:
                           Header files, Static Libraries,
                           Dynamic Libraries, Large

*** NOTE ***

   If you wish to install the appropriate Turbo Debugger
   to complement one of the minimum configurations listed
   above, you will need about 1500 KB additional disk space
   for each target you selected.

SECTION -4-  WIN32s INSTALLATION ISSUES

A) An Explanation of Win32s

   Win32s provides a subset of the functionality provided by 
   Windows NT. It lets 32-bit programs 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. Note that you 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
   don't affect the normal operation of Windows 3.1.

B) Adding Win32s to your system

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

   If you already installed BC++ 4.02 without Win32s on
   your system, insert the second to last install disk in 
   your A: drive. Run Windows, choose File|Run, then enter
   a:\setup.exe.


C) Win32s and minimum swap file size

   Borland recommends that you have a minimum of 12 MB of memory 
   available to develop Win32s applications.  For example, if your 
   machine has 8 MB of memory available to Windows, you should 
   configure your "Virtual Memory" (swapfile) to at least 4 MB.
   This will reduce the risk of out-of-memory errors occurring 
   when using Win32s.

D) Outdated versions of Win32s

   Win32s version 1.15 is included with this release. We recommend 
   that you replace your current version with version 1.15.

   If you are running an outdated version of Win32s, the INSTALL 
   program will instruct you to remove it before installation. To
   remove an old version of Win32s perform the following steps:

   1. Change directory to the WINDOWS directory on your hard drive.  
      This is most likely C:\WINDOWS.

   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 configuration.)

   3. Change directory to the SYSTEM subdirectory.

   4. Remove the following files:

        W32SYS.DLL
        WIN32S.INI
        WIN32S16.DLL

   5. Change directory to the WIN32S subdirectory.

   6. Remove all files here.

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

   You will now be ready to run the INSTALL program.  Be sure to 
   select <Install Win32s> in the INSTALL program so that the 
   newer version of Win32s will be installed.



SECTION -5-  TROUBLESHOOTING - INSTALL PROBLEMS

This section explains common errors encountered during
installation. System configuration and software conflicts
might cause the installation process to fail. If the
installation fails, follow the instructions in Section 11
on how to boot clean.  This will eliminate most possible
software conflicts.  If booting clean doesn't 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, you
   may need to get a replacement disk set. If running a disk
   checking utility (such as "chkdsk" or "scandisk") 
   reports a bad sector or data integrity problem contact
   Borland's Disk Replacement Line at (800-621-3132). 
   Otherwise, see Section 11 on booting clean, and if 
   the problem persists, contact Borland Technical Support
   (408-461-9133) for further assistance.

B) Install Program Terminates Prematurely 

   If the install program stops for no apparent reason without 
   error messages, it is possible that certain support files
   are write protected. To check this, do the following:
          1) Go to your WINDOWS directory
          2) Type  attrib *.*
          3) Check for the "r" attribute. If any file has this
             flag set, then you must clear it by typing:
                     attrib -r <filename>
          4) Repeat steps 2-3 for the WINDOWS\SYSTEM directory.

C) "Bad Table in Pak File" 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.02. Here are some suggestions:

   - Check that you have enough disk space for the options
     you chose to install.

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

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

   - If you are using disk compression read Section 2,
     Part A4) on reported available disk space when using
     disk compression.

   - Make sure that at least 3 MB of disk space is available
     on the drive where you have Windows installed, regardless
     of which drive you are installing Borland C++ to.

E) 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:

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

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

   - 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.02. System configuration and software
conflicts might cause BC++ 4.02 to fail. If BC++ 4.02 fails,
you should boot your system clean to eliminate any possible
software conflicts. Refer to Section 11 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) "Resource Workshop requires BWCC 2.0 and above"

   Windows is finding an older version of BWCC.DLL
   on your system.  Be sure that the only copy of
   this file is in your WINDOWS\SYSTEM directory and
   is dated 10-21-93 or later.  If you still get this
   error, please see Technical Information Document 1768.
   For information on how to receive this document,
   refer to Section 10.

B) Unable to Locate Required .DLLs

   If the BC++ 4.02 IDE fails to load because one or more
   DLLs cannot be loaded, verify that your BC4\BIN directory
   is in the PATH statement in AUTOEXEC.BAT.  If it is,
   restart your machine.

C) "Fatal Error in Display"

   Try using a different Windows video driver (different
   color and/or resolution); also try the SVGA and VGA
   drivers that ship with Windows.  For a long term solution,
   please contact the supplier of your video drivers for an
   update.

D) Out of Memory

   If you are using command-line tools and are getting 
   "Out of Memory" errors you might have exhausted your 
   extended (or XMS) memory pool. If you are experiencing
   this, please consult Technical Information Document 1737.
   For information on how to receive this document, refer
   to Section 10.

E) 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 Documents
   649 and 1328 address these issues. Refer to
   Section 10 for information on how to obtain these files.

F) Turbo Debugger for Windows

   If you experience any strange behavior from the Turbo
   Debugger, such as a garbled screen or a system hang upon
   execution or exit:

   1)  Make sure that you have the latest Windows drivers 
       for your video card.
   2)  Run TDWINI (icon name "TD Video Configuration") and
       test a different DLL to resolve a possible compatibility
       problem with your specific card.
   3)  Check TD-HELP!.TXT, TD_RDME.TXT, and README.TXT for
       additional information. 
   4)  If you are still experiencing difficulties your
       problem might not be related to the video mode. At 
       this point contact Borland Technical Support via 
       phone or online help.  Refer to Section 11 for more 
       information about online options and procedures. 
   
G) Borland Example Program Fails

   Be sure that you are opening up the project (Project|Open)
   for the example, rather than trying to open and compile one
   of the .C or .CPP files.  Using the project file will ensure
   that all files necessary for compilation are included, and
   also properly set the compiler options.

SECTION -7-  MODIFICATIONS INSTALL MAKES TO YOUR SYSTEM

This section describes the files that are added by the
install program to your Windows directory and the
modifications that are made to the Windows configuration
files.  Please note that these are example modifications
based on a default installation.  

Files changed in the Windows directory:

   WIN.INI modifications:
             [Extensions]
     added:  IDE=BCW.EXE ^.IDE
             [BCW4.0 INSTALL]
             Reserved1=C:\BC4

   PROGMAN.INI modifications:
               [Groups]
     added:    Group6=C:\WINDOWS\BCW402.GRP
             
   SYSTEM.INI modifications:
               [386Enh]
     added:    device=C:\BC4\BIN\WINDPMI.386
               device=C:\BC4\BIN\TDDEBUG.386


   CONFIG.NT modifications, if you are running Windows NT:
     added:    ntcmdprompt

   Files added to WINDOWS directory:
     BCW.INI            BCW402.GRP 
     BORHELP.INI        HELP.ICO 
     SYSTEM.OLD         OWL.INI 
     WINHELP.INI        TDW.INI 

   Files added to the WINDOWS\SYSTEM directory:
     BW32000C.DLL       BW320007.DLL
     BW320009.DLL       BWCC.DLL
     BWCC000C.DLL       BWCC0007.DLL 
     BWCC0009.DLL       BWCC32.DLL 
     CTL3DV2.DLL        CTL3D32.DLL
     BIVBX102.DLL


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

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

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

   - Generate icons by downloading the BC4GRPS.ZIP file.
     (If you need help on downloading refer to Section 10 of
     this document.) At the DOS prompt type: PKUNZIP
     BC4GRPS.ZIP. This uncompresses the files, including a
     readme.txt file containing instructions on using the
     BC4GRPS.EXE program.

   - Manually creating the icons.  If you are unfamiliar
     with creating program items manually, see your
     Windows documentation.  See below for the files
     that correspond with each icon normally installed.

B) List of executable files that each icon calls:

   Borland C++:                 \BC4\BIN\BCW.EXE
   Borland C++ launches Borland's Integrated Development
   Environment (IDE).

   Resource Workshop:           \BC4\BIN\WORKSHOP.EXE
   This icon launches Resource Workshop, a tool that
   integrates the entire process of designing, editing,
   and compiling resources for applications.

   WinSight:                    \BC4\BIN\WINSIGHT.EXE
   This icon launches WinSight--a program that lists
   debugging information about Windows classes, windows,
   and messages. 

   WinSpector:                  \BC4\BIN\WINSPCTR.EXE
   This icon launches WinSpector, which helps you perform
   a post-mortem examination of Unrecoverable Application
   Errors (UAE) or General Protection Faults.

   Turbo Debugger for Win32:    \BC4\BIN\TD32.EXE
   This icon launches the 32-bit Windows debugger.

   TD32 Configuration:          \BC4\BIN\TD32INST.EXE
   This icon launches the configuration utility for Turbo
   Debugger for Win32.

   Just In Time Debugging:      \BC4\BIN\JITIME.EXE
   This icon launches the configuration utility to enable 
   Just In Time Debugging.

   TD Video Configuration:      \BC4\BIN\TDWINI.EXE
   This icon launches the configuration utility that lets
   you configure the Debugger to run with your video card.

   Turbo Debugger for Windows:  \BC4\BIN\TDW.EXE
   This icon launches the 16-bit Turbo Debugger for Windows.

   TDW Configuration:           \BC4\BIN\TDWINST.EXE
   This icon launches the configuration utility for Turbo
   Debugger for Windows.

   Remote Debugging:            \BC4\BIN\WREMOTE.EXE
   This icon launches the Remote Debugger.

   Remote Setup:                \BC4\BIN\WRSETUP.EXE
   This icon launches the configuration utility that lets
   you configure your system to do remote debugging.

   Turbo Debugger for DOS:      \BC4\BIN\TD.EXE
   This icon launches the DOS Turbo Debugger.

   TD Configuration:            \BC4\BIN\TDINST.EXE
   This icon launches the configuration utility for Turbo
   Debugger for DOS.

   FConvert:                    \BC4\BIN\FCONVERT.EXE
   This icon launches the utility to convert text files from
   OEM to ANSI format or vice versa.

   Hot-Spot Editor:             \BC4\BIN\SHED.EXE
   This icon launches the Hot-Spot Editor, which creates
   and edits a bitmap that includes one or more hotspots.

   BCW and Library Reference:   \BC4\BIN\BCW.HLP
   This icon launches the on-line reference for Borland C++
   for Windows.

   BC DOS and Library Reference: \BC4\BIN\BCDOS.HLP
   This icon launched the on-line reference for Borland C++
   DOS functions.

   ObjectWindows Reference:     \BC4\BIN\OWL.HLP
   This icon launches the on-line reference for
   ObjectWindows.

   Windows API Reference:       \BC4\BIN\BWINAPI.HLP
   This icon launches the on-line reference for Windows API.

   Win32s Reference:            \BC4\BIN\WIN32S.HLP
   This icon launches the on-line reference for Microsoft's
   Win32 Application Programming Interface (API).   

   Resource Workshop Reference: \BC4\BIN\WORKHELP.HLP
   This icon launches the on-line reference for Resource
   Workshop.

   Winsight Reference:          \BC4\BIN\WINSIGHT.HLP
   This icon launches the on-line reference for WinSight.

   Winspector Reference:        \BC4\BIN\WINSPCTR.HLP
   This icon launches the on-line reference for WinSpector.

   Hot-Spot Reference:          \BC4\BIN\SHED.HLP
   This icon launches the on-line reference for the Hot-Spot
   Editor.

   Windows Socket Reference:    \BC4\BIN\WINSOCK.HLP
   This icon launches the on-line reference for Open
   Interface for Network Programming under Microsoft
   Windows.

   MCI Reference:               \BC4\BIN\MCISTRWH.HLP
   This icon launches the on-line reference for the Media
   Control Interface (MCI).

   Multimedia Reference:        \BC4\BIN\WIN31MWH.HLP
   This icon launches the on-line reference for the
   Multimedia Application Programming Interface (API) of
   Windows 3.1. 

   Creating Help:               \BC4\BIN\CWH.HLP
   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".

   Master Index:                \BC4\BIN\MINDEX.HLP
   This icon launches the master index to all of the printed
   manuals that come with BC++ 4.0.


SECTION -9-  WINDOWS LAN CONFIGURATION

BC++ 4.02 provides a Windows LAN Configuration option during
installation. This option must be used when you run Windows
from a network.

If you run Windows from a network, this option is required
because access to the WINDOWS directory is usually
read-only. If you plan to install BC++ 4.02 to a network,
the LAN Windows Configuration option centralizes the
location of these files to a location on your hard disk that
can be read from and written to.

The Windows LAN Configuration option places the following files
normally installed to the WINDOWS directory in the BC4\BIN 
subdirectory.   

BW32000C.DLL       BW320007.DLL  
BW320009.DLL       BWCC.DLL      
BWCC000C.DLL       BWCC0007.DLL  
BWCC0009.DLL       BWCC32.DLL     
CTL3DV2.DLL        CTL3D32.DLL   
BIVBX102.DLL

You will want to ask your Network Administrator to move the
files above to the WINDOWS directory to maintain standard
file locations.  Furthermore, CTL3DV2.DLL must be installed in
your WINDOWS directory (or its network equivalent).  If
it is located anywhere else, then you may get the error "CTL3DV2
incorrectly installed."

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


SECTION -10-  HOW TO GET A TECHNICAL INFORMATION DOCUMENT

Technical Information Documents contain tips, techniques, 
and enhanced information on using Borland development tools,
and information on commonly asked programming questions.  
Such documents often include programming examples.  These
documents can be accessed via modem or fax.      Technical
files which contain binary modules, such as patches for 
released Borland products, are normally available only from 
those services that can be accessed by modem.  Documents can 
be accessed from the following sources:
 
A) Fax 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 want to receive. The document will be faxed to
   you shortly.

   Here is a list of common Technical Information Documents:
      * 3       General Catalog of All C/C++ Documents Available
      * 649     General Protection Faults
      * 1171    Problem Report Form
      * 1010    Installing and Configuring BC++
      * 806     Network Installations
      * 738     Memory Corruption
      * 1561    Clean Boot
      * 1768    Resource Workshop requires BWCC.DLL 2.0 and later
      * 1773    How to Build DOS Applications in Borland C++ 4.0

B) Download the document from:

   -The Borland Download Bulletin Board Service (DLBBS)
    	(408) 431-5096, protocol 8N1

   -The Borland Automated Online Service (OAS)
    	(408) 431-5250, protocol 8N1

   -The Borland-supported FTP site on Internet
    	ftp.borland.com (IP address: 143.186.15.10)

   -Borland-supported forums on CompuServe, Genie, BIX.
     	for CIS type: go BCPPWIN or go BCPPDOS 
       	            and choose library 2
     	for BIX type: join Borland 
     	for GENIE type: Borland
 
   Below are the steps to download a Technical Information
   Document from the Borland DLBBS.

   DOWNLOADING FILES

   Once you know the name of the file you want to download,
   type "D" for download at the File menu. When prompted,
   type 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 is TI649.ZIP.  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 in an
   archived (compressed) format and need to be uncompressed
   before they can be used. If you don't have the unarchiving
   utility PKUNZIP v.204G or newer, download PKZ204G.EXE from
   the DLBBS and execute it.  You'll receive PKUNZIP and PKZIP
   utilities. To unarchive the file, type PKUNZIP and then the
   name of the archived file. For example:

        PKUNZIP TI649.ZIP


SECTION -11-  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.  Device drivers such as mouse 
drivers, network drivers, TSRs, etc. 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). 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 might 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. 

Making a Boot Disk
------------------
In order to make a bootable floppy disk, follow the
instructions below.  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  format a: /s (format the disk)
         
At this point you have a bootable floppy disk.  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 DOS 5.0 and DOS 6.x running Windows
-----------------------------------------------------------
   1) Insert your "bootable floppy" in drive A:
   2) Type  edit A:\CONFIG.SYS
   3) Type in the following:
          <Insert REQUIRED drivers here>
          DEVICE=C:\DOS\HIMEM.SYS        
          FILES=40
   4) Exit the editor (Alt-F, then X, then Y)
   5) Type  edit A:\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  CD \WINDOWS
   9) type  copy WIN.INI WIN.BAK
  10) type  copy SYSTEM.INI SYSTEM.BAK
  11) type  edit WIN.INI
  12) Make sure that the "load=" and "run=" lines in your
      WIN.INI file look like the following:
          ------------
          [windows]
          spooler=yes
          load=
          run=
          Beep=yes
          ------------
  13) Exit the editor (Alt-F, then X, then Y)
  14) type  edit system.ini
  15) Ensure that your "shell=" line in your SYSTEM.INI file
       looks like the following:
          ------------
          [boot]
          shell=progman.exe
          ------------
  16) Exit the editor (Alt-F, then X, then Y)
  17) Make sure your "Bootable floppy" is in drive A: and
      reboot your computer.

-------------------END OF FILE INSTALL.TXT------------------
