PRODUCT  :  Borland C++                           NUMBER  :  1301
  VERSION  :  1.0
       OS  :  OS/2
     DATE  :  October 25, 1993                         PAGE  :  1/2

    TITLE  :  Configuring BC++ for OS/2




  Installing Borland C++ for OS/2 when your OS/2 root directory is
  not drive C:


  The Borland C++ for OS/2 installation program currently installs
  incorrectly on systems that do not have drive C as their OS/2
  root directory. This is usually the case in systems configured
  for dual boot or boot manager. The dual boot and boot manager
  allow the computer to contain more than one bootable operating
  system on its hard drive concurrently. On a typical dual boot
  system the OS/2 operating system and it associated configuration
  file (CONFIG.SYS) are located on drive D.  This is the typical
  scenario that could cause an incorrect installation.  When the
  installation program starts, all the files are copied and
  unpacked to the directory specified. The installation program
  allows the specification of the OS/2 operating system directory.
  The location of the OS/2 operating system directory should be
  used by the installation program to find the CONFIG.SYS and make
  the appropriate modification to allow the Borland C++ to run on
  the system. Regardless of the path that is specified in the
  installation program for the OS/2 operating system directory the
  installation program will always modify the CONFIG.SYS in drive
  C. These are the modification that take place and need to moved
  the the correct CONFIG.SYS:

       ADDITIONS TO CONFIG.SYS FILE:

       REM --BORLAND INSTALL--
       SET IPFC=D:\BCOS2\IPFC

  Cut and Paste these two lines from the CONFIG.SYS file on drive C
  to CONFIG.SYS file that is used by the OS/2 operating system at
  boot time.  Check the path to the IPF file in BCOS2 to verify
  that it is correct.

       MODIFICATIONS TO ENVIRONMENT VARIABLES:

  The installation program will make modifications to the LIBPATH
  and the PATH environment variables inside the CONFIG.SYS file.
  The full path to Borland C++ \BIN  is appended to the end of both
  the LIBPATH and the SET PATH statements in the CONFIG.SYS. These
  changes must be moved to the correct OS/2 CONFIG.SYS file. On a
  typical system where the BC++ OS/2 Compiler is installed on drive













  PRODUCT  :  Borland C++                           NUMBER  :  1301
  VERSION  :  1.0
       OS  :  OS/2
     DATE  :  October 25, 1993                         PAGE  :  2/2

    TITLE  :  Configuring BC++ for OS/2




  D, the LIBPATH and the SET PATH statements should have the path
  "D:\BCOS2\BIN" as their last item.  For Borland C++ to function
  properly, the following lines must be present in the OS/2
  CONFIG.SYS.  ( Let X represent the root OS/2 drive )

       1)   Add the line SET IPFC=X:\BCOS2\IPFC

       2)   Add the statement X:\BCOS2\BIN to the LIBPATH statement
            in the OS/2 CONFIG.SYS file.

       3)   Add the statement X:\BCOS2\BIN to the SET PATH
            statement in the OS/2 CONFIG.SYS file.

  In items 2 and 3, remember to separate each statement with a
  semicolon. For example:


       PATH=d:\;d:\borlandc\bin;e:\mydlls


  DISCLAIMER: You have the right to use this technical information
  subject to the terms of the No-Nonsense License Statement that
  you received with the Borland product to which this information
  pertains.