install.txt

这个是Borland C++ 4.5安装原文件

        SET RTM=EXTMAX 12288


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 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, 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
    Borland's Disk Replacement Line at (800-621-3132). 
    Otherwise, see the Section 1 on booting clean, and if 
    the problem persists, contact Borland Technical Support
    (408-461-9133) 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.
      Refer to Section 0 for a list of the minimum
      installation requirements.

    - Boot your system with a clean configuration. Refer to
      Section 1 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.

E)  Win32s Issues

    Win32s is for use with Windows 3.1 or 3.11 only.
    Specifically, it is not required for a Win32
    operating system, and will not work with OS/2.

    Most of the time, if the Win32s setup utility fails, it is
    because the setup program had difficulty detecting a
    sufficient amount of virtual memory.  Ensure that you have
    virtual memory enabled in Windows, and that you are running
    in "Enhanced Mode."  To reinstall Win32s, either:

        - Insert the 27th disk in your floppy drive and
        execute SETUP.EXE

        or

        - Run SETUP.EXE from the INSTALL directory on your
        CD-ROM.



SECTION -4- CD-ROM INFORMATION
==============================

This section discusses a few issues that pertain specifically to
using BC45 from a CD-ROM.  If you did a "full installation", this
section is not relevant.

A)  "Drive not ready" When Starting Windows

At startup, Windows will check the status of all of the drives
listed in your PATH.  If a CD is not loaded in your CD-ROM drive
at this time, Windows will complain that the drive is not ready.
The following steps will minimize the number of "Drive not ready"
errors related to using BC45 from your CD, and will also ensure
that when starting Windows the contents of the CD loaded in your
drive will not be important.

    1)  Edit your AUTOEXEC.BAT file, and ensure that the
    \BC45\BIN directory on the CD is the last element of your
    path.  You will likely find a line that reads:

            PATH D:\BC45\BIN;%PATH%

    Change it to:

            PATH %PATH%;D:\BC45\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 TDDEBUG.386 from the
    \BC45\BIN directory on the CD to your configuration file
    directory and modify your WINDOWS\SYSTEM.INI file. For
    example,

           COPY D:\BC45\BIN\WINDPMI.386 C:\BC45\BIN
           COPY D:\BC45\BIN\TDDEBUG.386 C:\BC45\BIN

    Be sure to modify your Windows SYSTEM.INI file to reflect
    these changes. For example, change:

           [386Enh]
           device=D:\BC45\BIN\WINDPMI.386
           device=D:\BC45\BIN\TDDEBUG.386
    to:
           [386Enh]
           device=C:\BC45\BIN\WINDPMI.386
           device=C:\BC45\BIN\TDDEBUG.386

B) Command-Line Compiler Issues

Because the CD-ROM drive is a read-only device, special issues
are raised when using the command-line compiler included with
BC++ 4.  While the Windows-hosted tools can find BCW.INI in the
Windows directory, the command-line tools rely on finding
configuration files in either your current working directory or
in their home directory.  (E.g., C:\BC45\BIN)

The CD contains default configuration files that set these paths
to D:\BC45\INCLUDE and D:\BC45\LIB. If you need to change these
entries, or want to add options to the configuration files,
you'll need to copy the configuration files into the directory
where you run the tools and then edit the directory options.
Configuration files are simple ASCII files and can be edited in
most text editors. These files include TURBOC.CFG, TLINK.CFG,
BCC32.CFG, TLINK32.CFG. Also, BCROOT.INC defines a macro that is
commonly used in make files. You can override this value by
setting an environment variable for BCROOT.


C) Difficulty Finding Files

If you're experiencing difficulty finding files when running
BC45, 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 BC45 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.  

D)  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- 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       General Catalog of All C/C++ Documents Available
      * 649     General Protection Faults
      * 738     Memory Corruption
      * 1171    Problem Report Form
      * 1561    Clean Boot
      * 1738    Network Installations
      * 1773    How to Build DOS Applications in Borland C++ 4.0


A)  From within the US, fax the document from Borland's TechFax 
Service.

Call [phone] 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.

   -The Borland Download Bulletin Board Service (DLBBS)
        [phone], protocol 8N1

    [When downloading files from the DLBBS, you will
    need to select the appropriate "conference" from
    the main menu.]

   -The Borland Automated Online Service (OAS)
        [phone], protocol 8N1

   -The Borland FTP site on the Internet
        ftp.borland.com (IP address: 143.186.15.10)

    [all file names are case-sensitive on the FTP
    site, and almost always lower-case.]

   -Borland-supported forums on CompuServe and Genie.
        for CIS type: go BCPPWIN or go BCPPDOS 
                    and choose library 2
        for GENIE type: Borland

With rare exception, all files on the DLBBS and FTP site will be
compressed with a PKZIP 2.04 (or later) compatible archiver.  If
you do not have a version of PKZIP, you can download the file
pkz204g.exe; execute this file in an empty directory to extract
pkunzip.exe.


                   *** END OF FILE INSTALL.TXT ***