readme

汇编&c语言code

            WELCOME TO TURBO ASSEMBLER VERSION 2.01
            ---------------------------------------

  This README file contains important information about Turbo
  Assembler Version 2.01. For the latest information about
  Turbo Assembler 2.01, the accompanying programs, and the manual,
  read this file in its entirety. The UPDATE.DOC file contains
  information on the new features in Turbo Assembler version 2.01.
  The HELPME!.DOC file answers many common Technical Support
  questions.


TABLE OF CONTENTS
-----------------
1.  How to Get Help
2.  Installation
3.  Important Notes
4.  Files on the Disks


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

  If you have any problems, please read this file, HELPME!.DOC,
  UPDATE.DOC, and the Turbo Assembler 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 online charges.

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

  3. Write to us at the following address:

     Borland International
     Turbo Assembler 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, you may call the Borland
     Technical Support Department at [phone] Monday through
     Friday between the hours of 6 a.m. and 5 p.m. Pacific Time.
     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
        Assembler is displayed when you run the program.

     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 DOS prompt.)

     e. Contents of your AUTOEXEC.BAT and CONFIG.SYS files.


2.  INSTALLATION
----------------

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

  The Turbo Assembler/INSTALLATION disk contains a program called
  INSTALL.EXE that will assist you with the installation of Turbo
  Assembler 2.01.

  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: <Enter>
    INSTALL <Enter>

  If you have difficulty reading the text displayed by the INSTALL
  program, use the /B command-line parameter to force it to use
  black and white colors:

    a:install /B      - Forces INSTALL into BW80 mode

  Specifying the /B parameter may be necessary if you are using an
  LCD screen or a system that has a color graphics adapter and a
  monochrome or composite monitor.

  Notes for installation:

    INSTALL copies all Turbo Assembler files onto your hard disk
    and puts them into subdirectories. The default subdirectories
    are

      Turbo Assembler Directory:                   C:\TASM
      Examples Subdirectory:                       C:\TASM

  By default, all files from the distribution disks are placed in
  the Turbo Assembler Directory. If you would rather separate the
  examples programs into their own subdirectory, edit the default
  example files path before selecting START INSTALLATION.

  The Turbo Assembler distribution disks contain several files
  with a .ZIP file extension: TASM.ZIP, MANUAL.ZIP, etc. These
  files contain one or more other files that have been compressed
  and placed inside an archive. You can de-archive them yourself
  by using the UNZIP.EXE utility. For example,

    unzip /o tasm

  unpacks all the files stored in the TASM.ZIP archive into the
  current directory.

  INSTALL gives you a choice of copying the .ZIP files intact or
  de-archiving and copying all the individual files onto your hard
  disk during the installation process.


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

o Updated QUIRKS mode list
 
    The following apply to QUIRKS mode:
    1)  NEAR or SHORT jumps are generated even if FAR is specified,
        if source and destination segments are the same.
    2)  Type checking for some two-argument instructions is disabled,
        for example, MOV ES,BYTEPTR is allowed.
    3)  Forces an EQU to an expression with PTR in it to be a text
        macro.
    4)  Forces an EQU to an expression with : in it to be a
        text macro. 
    5)  Forces an EQU to an expression with OFFSET in it to be a text
        macro. 
    6)  Forces SHL operator to lose track of sign info.
    7)  Forces numeric equates (= or numeric EQU) to lose complex
        expression information such as segment, fixup type.
    8)  Reduces priority of GLOBAL, UNION keywords so that they may
        be overridden.
    9)  Causes warning instead of error to be generated if the second
        argument is missing in a two-argument instruction.
    10) Allows REPT without argument to be interpreted as REPT 0.
    11) Disables test for extra stuff on line after IF conditional.
 
    The following apply to QUIRKS with MASM51:
    1)  @@, @F, and @B are enabled.
    2)  Trailing language ID after NEAR or FAR in procedure
        declaration is allowed.
    3)  All procedure symbols are published globally.
    4)  :: label definitions are allowed.


o MASM compatibility pass

    Using TASM's /m command-line switch will generate a MASM-style
    second pass (compatibility pass) when the following
    constructions are present:

      o IF1 and IF2 directives
      o .ERR1 and .ERR2 directives
      o ELSEIF1 and ELSEIF2 directives
      o Forward references with IFDEF or IFNDEF
      o Forward references with the .TYPE operator
      o Recursively defined numbers (FOO=FOO+1)
      o Forward-referenced or recursively defined text macros 
          (FOO CATSTR FOO,<1>) 
      o Forward referenced macros

    The execution of the compatibility pass effectively disables
    the advantages associated with Turbo Assembler's multiple pass
    capabilities.


o Updated example files

    The WHEREIS example file has been updated to reflect some of
    the new TASM 2.01 features. In addition, IWHGLOBL.INC and
    IWHEREIS.ASM in TAEXMPL1.ZIP and GLOBALS.INC in TAEXMPL2.ZIP
    have been changed to remove the warning message "Global type
    doesn't match symbol type."


o SMART/NOSMART directives

    One of the optimizations that TASM 2.01 performs is to change
    FAR calls to an address in the same segment into a PUSH CS
    followed by a CALL NEAR.  Any FAR procedures that have an
    EXTRN definition declared inside a segment are considered to
    be in that segment, and TASM will generate the PUSH CS, CALL
    NEAR instructions for them.  To avoid this, put a procedure's
    EXTRN definition inside of a segment only if the procedure
    is actually in that segment, or put NOSMART and SMART
    directives around calls to the procedure in that segment.


o Turbo Assembler 2.01 Reference Guide corrections

    P. 187  In the section titled "Examples," make the following
    changes:

      prog.exe: myprog.asm prog2.asm include\stdio.inc
      tasm /t myprog.asm   # Recompile myprog using Turbo Assembler
      tasm /t prog2.asm # Recompile prog2 using Turbo Assembler
      tlink myprog prog2, prog

        Here are some better examples:

        prog.exe: myprog.obj prog2.obj
        tlink myprog prog2, prog

        myprog.obj: myprog.asm include\stdio.inc
        tasm myprog.asm

        prog2.obj: prog2.asm include\stdio.inc
        tasm prog2.asm

P. 196  The directives in Table D.1 should be uppercase.

P. 212  Ignore the second paragraph under the section "Turbo Link";
        TASM does not call TLINK.