Technical Information Database
TI760C.txt Installing and Configuring Borland C++
Category :General
Platform :All
Product :Borland C++ 3.X
Description:
INSTALLATION AND CONFIGURATION PROBLEMS
=======================================
Instructions for installing Borland/Turbo C++ can be
found in the User's Guide and in the online text file README,
which is contained on Disk One. This document is provided for
those that are having difficulties installing or configuring.
It will explain some of the most common issues that cause
Borland/Turbo C++ to not be able to run, explain how to do a
clean boot, and contains the most common errors received during
installation and configuration and how to resolve them. At the
end of the document there is a listing of the minimum system
requirements needed in order to install the Borland/Turbo C++
compiler.
If you are having problems running Borland C++ under
OS/2 in a Dos box you need the Technical Information Document
number 1373. If you are having problems running Borland C++ for
OS/2 you will need to get Technical Information Document number
1301. If you try the procedures outlined in this document and
are still having problems, you should contact Borland Technical
Support.
COMMON INSTALLATION PROBLEMS
==============================
1) One of the most common reasons for the install to fail
is because of insufficient hard disk space. You should check to
make sure you have enough hard disk space to install the product
(see the section on Minimum System Requirements).
2) Another reason for an unsuccessful install is if there
is a conflict with some other software on your computer. The
best way to test this is to do a clean boot (see section on
Booting Clean) and then try to run the install again.
3) You could also have problems installing if you copied
between disk sizes, 3 1/2 to 5 1/4 or vise versa, or did not use
the Dos diskcopy command. If you copied between sizes, please
call the Disk Replacement service(800/621-3132) for the right
size disks. If you use diskcopy to copy between disks of the
same size and still have a problem, please call Borland Technical
Support.
COMMON CONFIGURATION PROBLEMS
==============================
Most configuration problems which will prevent the
product from running result from one of the three problems:
1) A need to run the configuration routine, DPMIINST.EXE
If you are getting a specific error message, look
it up in the error section to see if you need to
run DPMIINST.EXE. Even if you are not getting an
error message, it is usually a good idea to run
DPMIINST.EXE because the Borland C++ compilers
may need to 'learn' particulars about enabling
protected mode on your system. You should do a
clean boot before running this (see section on
Booting Clean).
In particular, the line DOS=HIGH, or any other
devices that get loaded high, in your config.sys
will cause DPMIINST.EXE to not be able to run.
DPMIINST.EXE needs to be able to access high
memory and if anything else is loaded in high
memory, it will not be allowed to. DPMIINST.EXE
is found in your Borlandc(or tc)bin directory.
Once you have done a clean boot (see section on
Booting Clean) and are in the bin directory type
DPMIINST and follow the instructions it gives
you.
2) Insufficient Available Extended Memory
The Borland C++ compilers need at least 1MB of
extended memory (a total of 2MB on the machine)
free in order to run. However, the compilers
that run under Windows need 2MB of extended
memory because Windows needs at least 1MB for
itself (a total of 3MB on the machine). The
easiest way to free up memory is to do a clean
boot (see section on Booting Clean).
To check if you have enough extended memory go
to the Dos prompt and type mem if running Dos
5.0 or later. The output of the Dos 5.0 mem and
Dos 6.0 mem look slightly different. Included is
an example of both and the line you should check
for extended memory.
DOS 5 VERSION OF MEM
===================
651264 bytes total conventional memory
651264 bytes available to MS-DOS
487520 largest executable program size
1048576 bytes total EMS memory
1048576 bytes free EMS memory
7340032 bytes total contiguous extended memory
0 bytes available contiguous extended memory
1048576 bytes available XMS memory 256K
Article originally contributed by Borland Staff