Professional Documents
Culture Documents
Install
Install
TXT
===========
SEARCH INSTRUCTIONS: To go directly to a specific section,
search for "SECTION -#-" replacing the # with the appropriate
section number.
TABLE OF CONTENTS
SECTION 0
System Requirements
A) Minimum Installation
B) Full Installation
SECTION 1
Booting Clean
A) Making a Boot Disk
B) Contents of CONFIG.SYS
C) Contents of AUTOEXEC.BAT
D) Changes to WIN.INI and SYSTEM.INI
SECTION 2
Installation Notes
A) Boot Clean
B) Upgrading Issues
C) Network Installation
D) Hard Drive Installation
E) Installing Under Windows NT or OS/2
F) Installing Under OS/2
G) Installing Under Windows NT
H) Avoid Extended Characters in Path Names
I) Installing Adobe AcroRead
SECTION 3
SECTION 4
CD-ROM Information
A) "Drive not ready" When Starting Windows
B) Difficult Finding Files
C) Compiling and Running the Examples
SECTION 5
SECTION 6
4 MB Extended Memory
Intel 386 or higher
PC-DOS (MS-DOS) 4.01 or later
Microsoft Windows 3.1 or later
3.5" High Density Disk Drive or CD ROM Drive
* 8 MB of extended memory is highly recommended for:
- improved performance
- using the ObjectWindows Library
- running multiple applications on Windows
* The Install program requires Windows enhanced mode. It
does not run under standard mode.
* To view the Quick Tour, a screen resolution of 800x600 is
recommended.
B) Hard disk requirements (may vary due to cluster size)
CD-ROM configuration (tools run from CD): 20 MB
Full installation:
65 MB
The installation program requires about 5MB of
additional hard disk space to run.
More space is required on hard drives with large cluster
sizes (typically drives with a capacity of 1GB or more.)
SECTION -1- BOOTING CLEAN
=========================
It is highly recommended that you boot clean before installing
TCW 4.5. 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.
Twice below there is a 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:\TCWIN45\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).
The Turbo C++ install program asks where you will put the
Adobe viewer during its installation. The default answer
is C:\ACROREAD. Be sure to remember the viewer directory
when you run ACROREAD.EXE.
To install the Adobe viewer, run the ACROREAD.EXE
found in the INSTALL directory (not the one in the
ACROREAD directory.)
SECTION -3- 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 Section 1
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 Borland Technical Support.
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 its
temporary files in the directory WINDOWS\TEMP.
You will also see Error -2 if the Install program
cannot create this directory--if, for example, there
is already a file called TEMP in your WINDOWS
directory, or if your Windows drive does not have two
megabytes of free space.
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, a hard drive installation is often helpful.
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
PATH D:\TCWIN45\BIN;%PATH%
Change it to:
PATH %PATH%;D:\TCWIN45\BIN
and be sure that it is the last line in the file that sets
any component of your path.
2) Copy the files WINDPMI.386 and WINRUN.386 from the
\TCWIN45\BIN directory on the CD to your configuration
file directory and modify your WINDOWS\SYSTEM.INI file. For
example,
COPY D:\TCWIN45\BIN\WINDPMI.386 C:\TCWIN45\BIN
COPY D:\TCWIN45\BIN\WINRUN.386 C:\TCWIN45\BIN
Be sure to modify your Windows SYSTEM.INI file to reflect
these changes. For example, change:
[386Enh]
device=D:\TCWIN45\BIN\WINDPMI.386
device=D:\TCWIN45\BIN\WINRUN.386
to:
[386Enh]
device=C:\TCWIN45\BIN\WINDPMI.386
device=C:\TCWIN45\BIN\WINRUN.386
B) Difficulty Finding Files
If you're experiencing difficulty finding files when running
TCWIN45, check your PATH statement. Although having the PATH
statement point to the CD-ROM drive all the time will cause
Windows to complain "Drive not ready" if a CD is not in the
CD-ROM drive, sometimes when compiling if the CD-ROM drive is not
on the PATH and the files that are needed are on the TCWIN45 CD, the
compiler will not be able to find those files. Thus you might
need to add the CD Drive to your PATH; to minimize complaints
with "Drive not ready" errors, be sure that it is at the end. If
the path is correct, make sure your project directories are
valid. If you are relying on the CD-ROM drive to provide certain
library files, make sure the appropriate drive/path combination
is present in the directories section of your project.
C) Compiling and Running the Examples
All of the example projects will write their output by default to
the current directory. While this is ideal when the examples are
installed to the hard drive, the read-only nature of a CD-ROM
will cause the compilation to fail. To use any of the examples,
follow these steps:
1) Open the project file for the example you wish to run.
2) Select Options|Project
3) Set the temporary and final output directories to a
writeable location.
SECTION -5- PIPELINE AUTOMATIC REGISTRATION
===========================================
The installation program for this field test launches a
program from Pipeline to help customers register with
Borland. The Pipeline program asks for your name, address,
and other information. It then allows you to submit your
registration information by modem or to print it out and
mail it in yourself.
To register by modem, Pipeline dials a toll-free 800
number. Pipeline does not send any information other than
what it displays for you as it runs, nor does it create
hidden files on your machine. If you choose not to
register at installation, Pipeline sets up automatic
reminders every 14 days asking if you would like to
register yet.
The reminder feature can be disabled from your WIN.INI
setting. Removing the reminder under Windows NT requires
editing the system registry.
Begin by launching the Registry Editor, REGEDT32.EXE,
located in your SYSTEM32 directory. Select the
HKEY_CURRENT_USER window and go into the folder
hkey_current_user/Software/Microsoft/Windows NT/
CurrentVersion/Windows
There you'll see a "load:" line with the path to
REMIND.EXE. Double click on that line and delete it.
SECTION -6- 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.
Here is a list of commonly requested Technical Information Documents:
*
*
*
*
*
*
3
649
738
1171
1561
1738
A) From within the US, 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.
B) Download the document. The file name for document number NNN
would be tiNNN.zip.