📄 install.txt
字号:
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, OS/2, or Windows 95
SECTION 3 Trouble Shooting Installation Problems
A) Internal Error, Unable to Start Install
B) Data Integrity or Bad Sector on Disk Errors
C) Install Program Terminates Prematurely
D) General Protection Fault/Unhandled Exception
E) Problems With Installing Win32s
SECTION 4 CD-ROM Information
A) "Drive not ready" When Starting Windows
B) Command-line Compiler Issues
C) Difficult Finding Files
D) Compiling and Running the Examples
SECTION 5 How to Get A technical Information Document
A) From TechFax
B) From an On-Line Service
SECTION -0- SYSTEM REQUIREMENTS
===============================
Before installing BC++ 4.5 please review the minimum system
requirements listed below:
A) Minimum Installation (no IDE)
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
B) Full Installation (16-bit/32-bit capability):
8 MB Total Memory
Intel 386 or higher
DOS 4.01 or later
Windows 3.1 or later
VGA
Win32s (included with BC++ 4.5)
3.5" High Density Disk Drive or CD ROM Drive
C) Hard disk requirements (may vary due to cluster size)
CD-ROM configuration (tools run from CD): 25 mb
DOS command line configuration: 25 mb
16-bit Windows configuration (incl. IDE): 75 mb
32-bit Windows configuration (incl. IDE): 75 mb
Full installation: 100 mb
NOTE: On a compressed hard disk the installation process
might need additional hard disk space, depending on how the
installation affects the overall compression ratio.
SECTION -1- BOOTING CLEAN
=========================
It is highly recommended that you boot clean before installing
BC++ 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:\BC45\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).
SECTION -2- BEFORE YOU BEGIN
============================
A) Boot Clean
It is highly recommended that you boot clean before
installing BC++ 4.5. Booting your system with a clean
configuration will eliminate any potential software
conflicts that might arise during installation. Refer to
Section 1 for instructions on how to boot clean.
B) Upgrading Issues
If you are upgrading from BC4 or BC4.02, before removing the
old version of the compiler, be sure to save the RTL, BIDS,
and OWL .DLLs if you have any executables that depend upon
them. Otherwise, you will need to rebuild those application
with the new libraries.
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.5. 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 BC45\DOC\COMPAT.TXT.
C) Network Installation
If you are installing BC++ 4.5 on a network, you may wish to
consult Technical Information Document number 1738. For
information on how to receive this document, refer to
Section 5.
D) Hard Drive Installation
If you have about 40 megabytes of hard drive space in
addition to what is required for the installation of BC++
4.5, 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; if you have the CD, XCOPY the
INSTALL directory. Then, run the INSTALL.EXE from the
temporary directory rather than from the installation disk.
E) Installing Under Windows NT, OS/2, or Windows 95
1) The install will fail if you enter any paths that use long
file names (more than 8 letters in the name, more than 3
letters in the extension, or exceeding a total path length
of 128 characters).
2) When installing under OS/2, WinOS/2 should be run in either
a full screen WinOS/2 session, or from Program Manager.
Also, the session must be in Enhanced Mode rather than
Standard. To check this, see the WinOS/2 settings for
the appropriate icon. Note that if run from a full screen
session (preferred), near the end of the installation,
focus will switch to the OS/2 desktop as a DOS program is
run; when this program exits, OS/2 will not return the
focus back to the WinOS/2 session, you will need to do
this manually.
3) Under Windows NT, To allow for the proper execution of OLE
applications that use .DLLs in the Borland C++ "bin"
directory, you must update the system path. To modify the
system path, you must have Administrator privileges or login
as the Administrator.
To update the system path,
1) In Program Manager, double-click the Control Panel
icon.
2) In the Control Panel group, double-click the System
icon.
3) In the System Environment Variable box, select the
"Path=" statement.
4) In the Value box, add the path to the Borland C++
"bin" directory. For example, if you installed
Borland C++ in the C:\BC45 directory, type
C:\BC45\BIN at the end of the path statement.
5) Choose Set.
6) Choose OK.
4) WINRUN.EXE will be installed in your StartUp Program
Manager group. Because OS/2 (as of version 3.0) does
not provide support for Windows VxDs, WINRUN.EXE will
issue an error message and fail to load. Simply remove
it from the StartUp group to prevent future error messages.
5) To run 16-bit protected-mode programs (bcc, tlink) under
an NT command prompt, you need to add the following line
to CONFIG.NT:
ntcmdprompt
Under the default NT command-line prompt, DOS COMMAND.COM
is run after returning from a TSR (such as RTM.EXE, which
bcc and tlink load). Adding the above line will cause the
original NT CMD.EXE to be run.
6) Under Windows 95, add the following line to your
AUTOEXEC.BAT file:
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -