WELCOME TO TURBO C 2.01
                        -----------------------

This README file contains important, last minute information
about Turbo C 2.01. The HELPME!.DOC file on the COMPILER/UTILITIES
disk also answers many common Technical Support questions.


TABLE OF CONTENTS
-----------------
  1. How to Get Help
  2. Installation
  3. Important Notes
  4. Additional Notes
  5. Notes for Turbo Prolog Users
  6. Files on the Disks


 1. HOW TO GET HELP
-------------------

  If you have any problems, please read this file, the
  HELPME!.DOC file, and the Turbo C manuals first. If you still
  have a question and need assistance, help is available from
  the following sources:

  1. Type GO BOR on the CompuServe bulletin board system for
     instant access to the Borland forums with their libraries of
     technical information and answers to common questions.

     If you are not a member of CompuServe, see the enclosed special
     offer, and write for full details on how to receive a free
     IntroPak containing a $15 credit toward your first month's on-
     line charges.

  2. Check with your local software dealer or users' group.

  3. Write to us at the following address:

     Borland International
     Turbo C Technical Support
     1800 Green Hills Road
     P.O. Box 660001
     Scotts Valley, CA  95066-0001

     Please remember to include your serial number or we will be
     unable to process your letter.

  4. If you have an urgent problem that cannot wait and you have sent
     in the license agreement from the front of your manual, you may
     call the Borland Technical Support Department at (408) 438-5300.
     Please have the following information ready before calling:

     a. Product name and serial number on your original distribution
        disk.  Please have your serial number ready or we will be
        unable to process your call.

     b. Product version number. The version number for Turbo C is
        displayed when you first load the program and before you
        press any keys.

     c. Computer brand, model, and the brands and model numbers of
        any additional hardware.

     d. Operating system and version number. (The version number can
        be determined by typing VER at the MSDOS prompt.)

     e. Contents of your AUTOEXEC.BAT file.

     f. Contents of your CONFIG.SYS file.


 2. INSTALLATION
----------------
  The INSTALL/HELP/BGI disk contains a program called
  INSTALL.EXE that will assist you with the installation of
  Turbo C 2.01. There are three options for installation:

  1. Hard Disk - This option allows you to pick the subdirectories
     where the files will be loaded. It will create a TURBOC.CFG
     file based on those directories.

  2. Update from TC 1.5 - This allows for an easy update from version
     1.5.  After the files are copied, all the installed options
     from your current TC.EXE will be transferred to the new one.
     This is especially useful if you have modified the colors or
     editor keys.

  3. Floppy Disk - This option will build either a command line or
     Integrated Development Environment version for a two drive
     system. Be sure to have three formatted disks ready before
     you start.

  To start the installation, change your current drive to the one
  that has the install program on it and type INSTALL.  You will
  be given instructions in a box at the bottom of the screen for
  each prompt. For example, if you will be installing from drive
  A:, type:

    A:
    INSTALL

  You should read the rest of this README file to get further
  information about this release before you do the installation.


 3. IMPORTANT NOTES
-------------------

  o The file HELPME!.DOC contains discussions of common questions
    and answers concerning Turbo C 2.01. You should consult it for
    answers to problems that aren't covered in this file or in
    the manuals.

  o If you are running INSTALL or TCINST on a laptop or any other
    system that uses an LCD or composite display, you should set
    your system to black and white mode before running INSTALL
    or TCINST. You can do this from DOS with the following command
    line:

      mode bw80

    or, you can force INSTALL or TCINST to come up in black and
    white mode by using the /b switch:

      tcinst /b

  o /P PARAMETER FOR TC.EXE. A new command-line switch controls
    palette swapping on EGA video adapters. Using this switch

      tc /p hello

    is recommended only when the user program modifies the EGA
    palette registers. When /P is specified, the EGA palette will be
    restored each time the screen is swapped. In general, you don't
    need to use this switch unless your program modifies the EGA
    palette registers, or unless your program uses BGI to change
    the palette.

  o A program that takes over interrupt 9 cannot be debugged
    with the integrated debugger. Use the standalone Turbo Debugger
    instead.

  o exec() WITH NOVELL NETWORK. Versions of the Novell network
    system software earlier than 2.01-2 do not support a DOS
    call used by exec(), spawn(), and system(). If you are using
    the Integrated Development Environment to run a program that
    uses any of these functions and you have early Novell system
    software, run the program from DOS. To do this from the
    Integrated Development Environment you can use Alt-F/O.

  o If you used the INSTALL program to upgrade from version 1.5,
    or if you used CINSTXFR to transfer options from an
    installation of version 1.5, check the setting of the
    standard stack frame option in the Integrated Development
    Environment (Alt-O/C/C/S). If you are going to use the
    integrated debugger this option should be turned ON.

  o If you are having problems with the call stack or qualified
    names, make sure you have compiled with the standard stack
    frame option turned on.

  o The ANSI draft has changed the syntax of labels.  A label now
    must always be followed by a statement.  This means that code
    like this is no longer accepted:

      {
        .
        .
        .
        jump_label:
      }

    If you have code like this, change it to look like this:

      {
        .
        .
        .
        jump_label:
        ;       /* need a statement here! */
      }

  o TCC has a switch to specify which assembler to look for. By
    default, it will look for TASM.EXE. If you want to use a
    different assembler, use -E<filename>, as described in the
    Reference Guide.

  o When using THELP on an AT&T 6300, be sure to use the /L25
    command-line option, as described in the file THELP.DOC.

  o Because of the limited memory available in the Tiny model,
    it no longer supports graphics functions.

  o The Version 1.5 graphics drivers (*.BGI) are not compatible
    with the Version 2.01 graphics library. Use the graphics drivers
    distributed with Version 2.01.

  o When used with a Zenith Z-449 card, the BGI autodetection code
    will always select the 640X480 enhanced EGA mode. If you are
    using the Z-449 with a monitor that is not compatible with
    this mode, it will be necessary to override the GraphDriver
    and GraphMode parameters used in the BGI initgraph() call.


 4. ADDITIONAL NOTES
--------------------

  4.1 NOTES FOR VERSION 1.0 & 1.5 USERS
  -------------------------------------

  o You must use the Version 2.0 or 2.01 libraries with the 2.01
    compilers.

  o The Integrated Development Environment no longer displays the
    message "Press any key to return to Turbo C..." when your
    program terminates. Instead, at the end of your program the
    User screen is replaced by the Integrated Development
    Environment. To view the User screen, press Alt-F5 or
    select Alt-R/S. When you are viewing the User screen,
    pressing any key will return you to the Integrated
    Development Environment.

  o A new pseudo-variable has been added. _FLAGS now contains the
    value of the flags register so you can test the flags at any
    point in your program.

  o The ssignal() and gsignal() functions are no longer
    supported. See the section in this README on how to convert
    programs that use them.

  o The cprintf() function now works as documented. It does not
    translate line-feeds into CR/LF combinations.

  o Some compatibles had a problem under Version 1.5 because it
    used interrupt 18H. Version 2.01 does not use this interrupt,
    so you shouldn't encounter this problem anymore.

  o The program TCINST.COM in Version 1.0 has been changed to an
    .EXE file. You should delete the TCINST.COM program before
    trying to run the new TCINST.EXE. Otherwise, MS-DOS will actually
    run the old one.

  o The FILE structure for streams in Version 1.0 (but not 1.5) has
    been changed, so that the function tmpfile() could be implemented.
    You should recompile any modules that use stream I/O.

  4.2 THELP
  ---------

  THELP is a memory-resident utility program that gives you
  access to the Turbo C context-sensitive help system from any
  program. You don't need to use THELP if you're in the
  Integrated Development Environment, but it is especially useful
  if you use the command line compiler and your own text editor,
  or if you are debugging with the standalone Turbo Debugger. To
  use THELP, load THELP.COM into memory by typing at the DOS
  command line:

    thelp