                    DELPHI INSTALLATION NOTES

This file contains important information that you should read
BEFORE you install Delphi or Delphi Client/Server on your system.
Carefully review README.TXT once installation is complete. In
addition, there are separate READ????.TXT files in the RPTSMITH,
IBLOCAL, IDAPI and DBD directories. Errata for the documentation
can be found in \DELPHI\DOC\MANUAL.TXT.

Note that all printed and online documentation assume that you
have installed Delphi using the default directory structure.

IMPORTANT: For license information on deploying Delphi and Delphi
Client/Server applications and for a list of redistributable
files, refer to DEPLOY.TXT in the \DELPHI directory.

Table of Contents
-----------------
1. CD-ROM directory overview
2. Before you run SETUP...
3. Run SETUP!
4. Troubleshooting installation problems
5. Unpacking files manually


1. CD-ROM DIRECTORY OVERVIEW
----------------------------
\INSTALL   - Contains each disk image in a separate directory.
             Read this file and then run \INSTALL\SETUP.EXE to
             install Delphi on your system.
\RUNIMAGE  - Contains a complete installation. All files are
             unpacked and in the default directory structure.
\REDIST    - Contains the BDEINST, SQLINST, and RPTINST
             redistributables with each disk image in a separate
             directory. Refer to \DELPHI\DEPLOY.TXT for more
             information.
\VIDEOS    - Contains sample Windows video (.AVI) files.
\MANUALS   - Contains printed documentation in Adobe Acrobat
             format. Run the \MANUALS\INSTALL.EXE program to set
             up the Adobe Acrobat reader on your system.

2. BEFORE YOU RUN SETUP
-----------------------
o Borland Database Engine - This new version release of the
  Borland Database Engine (BDE, also known as IDAPI) has been
  fully tested and certified for use with dBase for Windows and
  Paradox for Windows.

  If you already have a copy of BDE installed on your system, we
  recommend that you backup the previous copy of the BDE, delete
  it from your system, and then install this version into the
  same directory.

  If you install SQL Links and IDAPI to different directories,
  manually edit WIN.INI and append your SQL Links directory onto
  the DLLPath entry in the IDAPI section. Make sure to place a
  semi-colon between each directory path.

  Note that the SETUP program incorrectly states that \IDAPI
  should be inserted into your DOS path. IDAPI is not required on
  your DOS path.

o Local Interbase Engine - After installing the Local Interbase
  Engine please see the file, READIB.TXT, found in the IBLOCAL
  directory for important configuration notes. Make sure the
  \IBLOCAL\BIN directory is on your DOS path. If you install the
  SQL Links for InterBase but do not install the Local InterBase
  Server, include the SQL Links directory you specify during
  SETUP on your DOS path.

  When specifying a target location for the Local InterBase
  Server, specify a local drive (not a remote or mapped network
  drive).

o WINSOCK.DLL - If you directed SETUP to rename your WINSOCK.DLL
  and you are now experiencing problems accessing your network,
  use your original WINSOCK.DLL (which SETUP renamed to
  WINSOCK.BOR). Make sure you exit and restart Windows for the
  change to take effect.

  If you're using the InterBase Workgroup Server, additional
  network protocol troubleshooting information is available in
  the InterBase Client for Windows User's Guide which came with
  your InterBase Workgroup Server documentation set.

o VBX controls - SETUP installs the following VBX files
  into the \WINDOWS\SYSTEM directory that will overwrite any
  existing VBX files with the same name:

    GAUGE.VBX
    SWITCH.VBX
    PICT.VBX
    CHART2FX.VBX

  Before running SETUP, check for filename collisions and backup
  your existing copies of these files.


  Delphi Client/Server installation only
  --------------------------------------
  o Using Oracle - Install places both ORA6WIN.DLL and ORA7WIN.DLL
    in your IDAPI directory. Remove the one you DON'T use or your
    system may not correctly access data from your Oracle server.

  o Using Sybase - If you encounter problems with W3DBLIB.DLL,
    contact Sybase for a more recent version.


3. RUN SETUP!
-------------
To install Delphi, run the setup program (SETUP.EXE) found on the
CD in the directory INSTALL\DISK1. The installation process
requires at least 3Mb of free disk space in your Windows
temporary directory and at least 30Mb of free disk space. A
complete installation of Delphi Client/Server requires
approximately 80Mb.

After installing we recommend that you exit windows and reboot
your computer so that any changes made to AUTOEXEC.BAT will take
effect.


4. TROUBLESHOOTING INSTALLATION 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 the Installation Notes section
on how to boot clean. This will eliminate many possible software
conflicts. Also, check the integrity of the file systems on your
hard drive using a utility like CHKDSK or SCANDISK; proceeding
with an installation while file system errors are present
increases the risk of a failure resulting in data loss. If these
two steps do not solve the problem, or you encounter a problem
not mentioned here, contact the Borland Technical Support Hot
Lines. Lines are open from 6:00 A.M. to 5:00 P.M. Pacific Time at
(408) 461-9195.

A)  Internal Error, Unable to Start Install

    1) Error -2: The install program was unable to create a
    temporary directory needed for the installation. Check that
    if you have either TMP or TEMP set as environment variables
    that they point to a valid directory on a drive with at least
    two megabytes of free space (four megabytes if you are using
    disk compression). If you do not have a TMP or a TEMP
    environment variable set, the install will place it's
    temporary files in the directory WINDOWS\BORLAND.TMP.

    2) Error -3: There was an error while copying and
    decompressing the file INSTRUN.EXE, which is used to launch
    phase two of the installation. Check that there is sufficient
    free space in your temporary directory (see above) and boot
    the machine clean. Also, if you have the diskspace available
    and you're installing from floppy disks, it is often helpful
    to copy all installation disks to a hard drive and a hard
    drive and then run SETUP from there.

    3) Error -69: The execution of INSTRUN.EXE (phase two of the
    installation process) failed. Probable causes: file
    corruption (see above), memory corruption (see the section on
    booting clean).

B)  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
    Technical Support at (408-461-9195). Otherwise, see the
    section below on booting clean, and if the problem persists,
    contact Borland Technical Support for further assistance.

    Outside the US, contact your local Borland representative.

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

D)  General Protection Fault/Unhandled Exception

    If you encounter a General Protection Fault or Unhandled
    Exception during installation, try the following steps:

    - Make sure your system meets the minimum requirements.

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

    - Perform an integrity check on your hard drive, using
      a utility such as "SCANDISK" or "CHKDSK".

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


  Booting Clean
  -------------
  If you experience problems running SETUP, we recommend that you
  boot clean before installing Delphi. Booting your system with a
  clean configuration will eliminate many potential software
  conflicts that might cause the installation to fail. You will
  need one blank floppy diskette. After making the disk bootable,
  use a text editor (EDIT, for example) to create and/or modify
  the files mentioned below.

  Note that the instructions below assume that DOS is installed
  into the directory C:\DOS, and that Windows in installed into
  the directory C:\WINDOWS.

  In the section below, you'll see the statement "<insert
  required drivers here>". For the purposes of the clean boot, a
  "required driver" is one that must be loaded so that you can
  access the devices necessary to complete the installation. For
  example, for a CD-ROM installation, MSCDEX (or equivalent)
  would be a required driver; if you are installing onto a
  network drive, your network drivers are required. Examples of
  things that are not "required drivers" include EMM386.EXE,
  QDPMI.SYS, and SMARTDRV.EXE. If you are unsure whether a driver
  is required, assume it is not.

  A) Making a Boot Disk

  It is suggested that you create the clean boot configuration on
  a floppy disk, in order to minimize the number of changes made
  to your normal system configuration.

  In most cases, inserting a blank diskette in drive A: and
  typing the command

    format a: /s

  will work.  See your DOS documentation for more details on
  creating a bootable floppy.


  B) Contents of CONFIG.SYS (on boot floppy)

    DEVICE=C:\DOS\HIMEM.SYS
    FILES=40
    <insert REQUIRED drivers here>

  C) Contents of AUTOEXEC.BAT (on boot floppy)

    REM the path statement should be copied verbatim
    REM from your current AUTOEXEC.BAT.  The line included
    REM below is an example only.

    PATH=C:\WINDOWS;C:\DOS;C:\IBLOCAL\BIN

  D) Changes to C:\WINDOWS\WIN.INI and C:\WINDOWS\SYSTEM.INI

  Before modifying these files, be sure to back them up: Windows
  will not properly start if they are corrupted (i.e., copy
  WIN.INI WIN.BAK).

    1)  Edit WIN.INI

    2)  Find all lines that begin with either "load=" or "run="
        and place a single ";" at the start of each line.

    3)  Edit SYSTEM.INI

    4)  If the line that starts with "shell=" is set to something
        besides "progman.exe", place a ";" at the start of the
        line, and replace it with "shell=program.exe" (no
        quotes).


5. UNPACKING FILES MANUALLY
---------------------------
If you're installing from floppy disks and wish to extract files
that are archived in a .PAK file, run the \DELPHI\UNPAQ.EXE
utility from the Program Manager File|Run menu. Files with a .ca?
extension are "split" files and cannot be decompressed. If you're
installing from a CD-ROM, you can simply copy the file(s) from
the \RUNIMAGE directory.
-----------------------------------------------------------------
