	 =============================================================
	              README.TXT - AutoCAD Release 13c1
	 =============================================================

	              January 14, 1995

========================================================================
CONTENTS
========

    R13C1 Update
    
        Purpose
        
        Background
        
        General Questions and Answers
        
        R13c1 Update - What Problems Does it Fix?
        
        Additional Information

    General Information


========================================================================
R13C1 UPDATE
============
     
PURPOSE
=======
Autodesk is committed to delivering products of the highest quality.  
As with any major software release, some bugs are found after the 
product ships.  Autodesk is committed to proactively addressing quality 
concerns, and therefore has developed a software update procedure to 
distribute bug fixes as quickly and easily as possible. The purpose of 
this document is to explain the update procedure in general, as well as 
specific information about C1. 


BACKGROUND 
========== 
Problems are reported through the dealer network to Autodesk Product 
Support or by customers by filling out a bug report form provided in 
the back of the Installation Guide and mailing it to Autodesk.  Once a 
problem is verified as a bug, it is entered into Autodesk's bug 
tracking system.  Once bugs are fixed, software patch programs are 
created to correct the problems.  

In the past, bug fixes required Maintenance Releases, such as C1 or C2. 
In most cases, these bug fixes required customers to reinstall and 
reconfigure the entire product.  Now, using software patch technology, 
dealers and customers are able to use a quick, straight-forward 
procedure to correct the problems without reinstalling AutoCAD.  In 
most cases, patches will not affect any customization options. 

Software patches are distributed as either an Update Patch or a 
Maintenance Patch.  All patches can be downloaded electronically, free 
of charge.  Or, diskettes may be purchased from Autodesk for a nominal 
charge.

Update Patches contain a limited number of bug fixes and are made on 
an as-needed basis.  Update Patches are released between Maintenance 
Patches.  Autodesk recommends that dealers distribute these patches to 
customers who have reported problems.  We also recommend that dealers 
include the patch with any new sales or in any new installations.

Maintenance Patches are significantly broader in scope than Update 
Patches.  They contain all bug fixes that have previously been made 
available through Update Patches, as well as additional bug fixes, and 
in some cases may include new functionality.  Maintenance Patches are 
synchronized with Maintenance Releases which are used to manufacture 
new units.  We recommend that dealers proactively distribute 
Maintenance Patches to all of their existing R13 customers and include 
the patch with any new sales or new installations.  


GENERAL QUESTIONS & ANSWERS 
=========================== 
- How do software patches work?

R13 was specifically designed so it can be easily updated in the field.  
The software patch is actually a program that is able to modify 
existing files.  When a patch is installed, it replaces the current 
file(s) with the new file(s). 

IMPORTANT NOTE:  Please be aware that a software patch supplements the 
original disk set and does not replace existing media.  Customers 
should store the software patch media with the original media disk set.

- What are the benefits of using patches?

Most importantly, it allows us to get bug fixes out to our customers 
faster.  Because it is a subset of the program, patches can be freely 
copied and distributed among AutoCAD dealers and customers.  Software 
patches can also be effectively distributed electronically.  Finally, 
patches do not require new serial numbers or authorization codes, and 
in most cases, will not affect customization.

- How does Autodesk distribute patches?

Software patches are posted worldwide to the general forums of 
CompuServe, Global Village, and Internet and can be freely downloaded 
by dealers and customers.  Once a patch is downloaded, it can be copied 
and distributed among AutoCAD customers.  In addition, Maintenance 
Patches are automatically mailed to all dealers for distribution to 
their customers.

Diskette media is also available through Autodesk Customer Service at a 
nominal charge. Contact Autodesk Customer Service at  800-538-6401 or 
707-794-1450 to order the latest patch.  For customers outside the US, 
Canada, or Latin America, please contact your Authorized Autodesk 
Dealer or your local Autodesk office for a copy of the latest patch.

- What customers do these patches affect?

It is our goal to have all customers synchronized with the latest 
Maintenance Release.  Therefore, we ask that Autodesk Dealers 
distribute Maintenance Patches to all customers.   

Customers can download Update Patches from the various electronic 
forums. A text file for each patch is posted so customers can 
determine whether they need a particular patch.  

We recommend that dealers include patches with all new sales and 
installations, as well as distribute them to customers who have 
reported bugs that are fixed in specific patches.

- Why isnt Autodesk recommending that Update Patches be distributed 
  to all customers?
  
Update Patches typically contain fixes to bugs that may not affect 
large groups of users and we do not want to inconvenience our users 
with multiple patches in a relatively short period of time.  Some 
customers will always want the latest version and are willing to take 
the time to do so.  We recommend that those customers either download 
the patches electronically or work out an arrangement with their dealer.

- How are Update Patches and Maintenance Patches differentiated?

Update Patches are designated with a letter and Maintenance Patches are 
designated by a number.  For example, R13c1 indicates a Maintenance 
Patch. R13c1a or R13c1b would indicate the sequence of Update Patches 
released after the c1 Maintenance Patch.

- How reliable is this patch technology?

When creating a patch, the patch builder program creates a checksum of 
the original file.  The patch program uses this checksum to ensure that 
it is modifying the correct file.  Other major software vendors are 
also using this technology with great success, and Autodesk used it in 
a number of cases with Release 12.

- What technology does Autodesk use to create these patches?

We use RTPatch from PocketSoft and PKZIP from PKWARE.

- How easy is a patch to install?

An easy-to-use batch file automates the whole procedure.  You simply 
type the batch command and follow the instructions on your screen.  
The entire process typically takes less than fifteen minutes.

- How large are the patches?

Each patch will vary in size.  You can expect to see patches range 
between 500K and a few megabytes.

- How can I tell whether a patch has been installed already?

The patch automatically updates the version number located in the Help 
About box. 

- If more than one patch exists, do I need to install all of them?

No, simply install the latest patch.  The software is able to determine 
the patch history of your software and automatically updates the 
appropriate files.

- Should I exchange any unopened or uninstalled product?

It is not necessary to exchange existing product -- simply run the 
latest patch after the standard installation.


R13C1 UPDATE -- WHAT PROBLEMS DOES IT FIX?
==========================================
The following problems were fixed with the R13a patch and are included
in the R13c1 release: 
     
     --  Attaching an xref drawing with missing nested attachments or 
opening a drawing with missing nested attachments works correctly. The 
same is true for drawings that are overlayed. 
     
     --  Editing an associative hatch's boundary when the hatch pattern 
is on a frozen layer works correctly. 
     
     --  Performing a DIMTEDIT/LEFT or RIGHT on a dimension in a 
paperspace viewport works correctly. 
     
     --  Switching to paperspace when an object's grips are active works 
correctly. 
     
     --  Mline styles are now associated with the correct layers in all 
cases. 
     
     --  When running the DOS version on fast PC's such as 90Mhz or 
faster Pentium computers, AutoCAD for DOS was overzealous in polling the 
keyboard, possibly leading to a performance slowdown.  This has been 
corrected (this problem is  not related to the Pentium floating point 
problem). 


The following problems are fixed with the R13c1 update: 

     -- PostScript and TrueType font mappings are now included in the 
acad.ini file.

     -- Anonymous group definitions within xrefs correctly translate 
into new definitions.

     -- Group name definitions within block references and xrefs are 
no longer retained within the drawing database which allows access to 
these names by editing commands. Group naming conflicts within block 
references has been corrected.

     -- The speed of group selection has been increased.

     -- GROUP Add correctly adds entities removed from group 
membership via GROUP Remove.      

     -- The combo boxes are now accessible after respacing buttons on 
the Object Properties toolbar. AutoCAD now correctly handles the 
creation of a custom toolbar and the modification of a toolbar flyout.
     
     -- Circles drawn perpendicular to the WCS display the correct 
linetype.
     
     -- The BREAK and TRIM commands properly duplicate associated 
xdata.
     
     -- A semicolon in the ***AUX and ***BUTTONS menu sections is now 
correctly interpreted as a return in menu macros, and the plus sign is 
now a valid character for screen menu labels. A backslash in a menu 
macro in the ***AUX menu section is now correctly replaced with the 
coordinates of the pick point.

     -- The AutoLISP (grvecs) function properly highlights entities as 
specified.

     -- The ADS function ads_printf() properly responds to format 
strings.
     
     -- In ARx ADS, the ads_command(RTNONE) function properly cancels 
a currently running AutoCAD command.

     -- Trimming and grip-copying splines now works correctly.

     -- A full plot preview now displays OLE objects properly.
     
     -- AutoCAD now imports DDE data correctly.

     -- AutoCAD properly saves the status of "Keystrokes" when the 
Preferences dialog is accessed from the Command Window or the Text 
Window.

     -- PSOUT now correctly renders 8-bit text objects on DOS.

     -- RENDER properly uses subentities' colors in a 3Dsolid, 
resulting in more consistency between SHADE and RENDER.

     -- The BHATCH dialog User, Normal, Inner and Outer options now 
return the proper values to the HPNAME system variable in localized 
versions of AutoCAD.

     -- Hatch patterns beginning with letter used for the "User" 
hatch pattern option (such as 'U' on US English versions) are now 
valid.

     -- DDCHPROP now properly handles a selection set of objects with 
varying thickness or linetype scale.

     -- Coordinate display and view centering problems with the Aerial 
Viewer have been fixed.

     -- Long path names in the Open Drawing dialog box do not force 
the Read Only check box to be selected. 

     -- Transparent Help is disallowed from AutoLISP on DOS - Calling 
for help by typing 'HELP as a prompt generated from an AutoLISP or 
ADS program has been disabled for DOS only.  You may still ask for 
help in these situations in AutoCAD for Windows. Note that this means 
that the AutoLISP function (setfunhelp) and the ADS function 
ads_setfunhelp() are useless for DOS, since the information they 
register will never be used.  
  

ADDITIONAL INFORMATION
======================

     -- The relative sizes of numbers in stacked fractions are now 
based on the DIMTFAC system variable (in the same way that tolerance 
values use this system variable).

     -- Unloading of ADS and RX apps fails on Windows if you 
are using SHARE.EXE. To maintain file protection in a multiuser 
environment, use VSHARE.386 instead of SHARE. You have three 
options, each explained in greater detail below:

  - Use VSHARE.386 instead of SHARE.EXE
  - Continue to use SHARE.EXE
  - Use neither SHARE.EXE nor VSHARE.386

VSHARE comes with newer Microsoft Windows products such as Office, 
Word, Windows for Workgroups, etc. VSHARE is a total replacement for 
SHARE.EXE, so you don't need both. Take SHARE.EXE out of your 
AUTOEXEC.BAT, and add the following line to the [386Enh] section of 
your SYSTEM.INI file:
    
       device=vshare.386. 
    
Continuing to use SHARE is not a problem assuming that you don't care 
about being able to unload ADS or RX applications. If you try to 
unload an application with SHARE loaded, the unload fails cleanly with 
a command line notice of the failure to unload -- AutoCAD continues 
on without a problem. 
    
It is also possible to run AutoCAD without loading SHARE or VSHARE. 
Doing so will allow you to unload ADS and RX applications but does 
have the following consequences:
    
  - You are unable to use ASE and ADE without SHARE or VSHARE
  - Many Microsoft programs require SHARE or VSHARE to be loaded
  - File protection in a multiuser environment is compromised


     -- The ACAD.PGP file is common to all platforms, however it 
references external commands that work only in DOS (such as CATALOG, 
DIR, EDIT, and TYPE). These are not meant to work on other platforms 
such as Windows.

     -- The diskette version of AutoCAD Release 13 contains basic 
customization tools such as AutoLISP and associated documentation. The 
programming interface files for ADS and ASI development, as well as 
all the advanced customization documentation, are only available on the 
CD version of AutoCAD Release 13. This electronic documentation is part 
of the complete documentation set available on the CD version.
     

========================================================================


	 =============================================================
	              README.TXT - AutoCAD Release 13
	 =============================================================

			   General Information
			      November, 1994


========================================================================
CONTENTS
========

    General Notes

    Windows-Specific Information

    DOS-Specific Information

    Manual Corrections and Additions

See the following documents for more README information:

    READDRV.WRI     Contains additional information on ADI 4.2 device
                    drivers.
      
    READADS.WRI     Describes the text files that explain how to
                    compile, link, and debug AutoCAD Development System
                    (ADS) Applications, and tells where to find them.
						   
    READASE.WRI     Contains additional information on the AutoCAD SQL 
                    Extension (ASE).
							       
    READREN.WRI     Contains additional information on AutoCAD Render.

    READNET.WRI     Contains additional information on networked AutoCAD
                    and the hardware lock. 


========================================================================
GENERAL NOTES
=============

What's New in Release 13
------------------------

    For information on what's new in AutoCAD 13, select "What's New in
    Release 13" from the Help menu. For a history of all AutoCAD
    revisions see the history.txt file (for DOS) or history.wri file
    (for Windows).

Using Release 12 Help Files
---------------------------

    You can't use Release 12 Help files in Release 13. If you keep 
    Release 12 Help files on your system, make sure your support path 
    lists the directory for the Release 13 Help file first.

Group Code 2 in MLINE and MLINESTYLE objects
--------------------------------------------

    The DXF groups with the 2 group codes in these record types are 
    redundant fields. These 2 groups shouldn't be modified under any 
    circumstances, although it's safe to read them and use their values.

    The correct fields to modify are:

    MLINE            the 340 group in the same object, which indicates 
                     the proper MLINESTYLE object.

    MLINESTYLE       the 3 group value in the MLINESTYLE dictionary
                     which precedes the 350 group that has the handle
                     or entname/ads_name of the current MLINESTYLE.

Editing Associative Hatched Geometry
------------------------------------

    Editing operations on geometry containing multiple associative hatch 
    blocks can produce unpredictable results. For best results when 
    editing hatched geometry, edit the bounding geometry.

    Associativity may also be lost when editing a hatch boundary if the
    hatch pattern is not available at the time of editing. You can either
    complete the edit, erase the hatch and re-hatch the boundary, or cancel
    the edit, make the pattern available, and reedit.

MTEXT and Vertical Fonts
------------------------

    Tolerances, multiple lines, underlined text, stacked fractions and 
    obliqued characters created with vertical fonts in MTEXT don't display 
    correctly.

DXFOUT Precision for Release 12 AME Solids
------------------------------------------

    It's recommended that you use the maximum precision (16) when using
    DXFOUT on Release 12 AME solids for use in Release 13. If you use a 
    low precision with DXFOUT, data might be incorrect and some operations 
    might fail.

Using Release 12 Files in Release 13
------------------------------------

    When you load an AutoCAD Release 12 file into Release 13, it will be 
    converted to Release 13 format. Release 12 drawings display differently
    as they are loaded into AutoCAD Release 13 than do Release 13 drawings.
    Release 12 drawings regen after they are loaded into memory, causing a
    delay before you see anything drawn on screen. Release 13 drawings regen
    as they are being loaded.

    In the unlikely event that Release 13 crashes, the file is automatically 
    saved in Release 13 format (you won't be given the opportunity to save 
    the file as Release 12 during an error abort.)

    If you need to keep the drawing in Release 12 format, either mark the  
    file as "read only," or load it into Release 13 and use the SAVEASR12 
    command to save it to a file in Release 12 format.

SAVEASR12 Command and Symbol Names
----------------------------------

    If you create a block and then use SAVEASR12, there's a chance that 
    some extended characters might be removed. This can result in duplicate 
    symbol naming. It's recommended that you check the messages displayed 
    in the text window before quitting AutoCAD.

Using AutoLISP to Access Objects Contained in an AutoCAD Group
--------------------------------------------------------------

    To get access to the entities contained in a group you should do the
    following:

    1. (setq objname (namedobjdict))

    2. (setq ls (dictsearch objname "ACAD_GROUP"))

       as an example, this returns:

       ((-1 . <Entity name: 8dc10468>) (0 . "DICTIONARY") (5 . "D") (102 . 
       "{ACAD_REACTORS") (330 . <Entity name: 8dc10460>) (102 . "}") (100 . 
       "AcDbDictionary") (3 . "G1") (350 . <Entity name: 8dc41240>))

    3. (setq group1 (dictsearch (cdar ls) "g1"))

       in this example, this returns the actual group definition:

       ((-1 . <Entity name: 8dc10518>) (0 . "GROUP") (5 . "23") (102 . 
       "{ACAD_REACTORS") (330 . <Entity name: 8dc10468>) (102 . "}") (100 . 
       "AcDbGroup") (300 . "one circle") (70 . 0) (71 . 1) (340 . <Entity name: 
       8dc10510>))

    4. The 340 code is the entity that belongs to the group.

General Help API
----------------

    The file extension is no longer required on the file name parameter 
    for the AutoLISP functions (help) and (setfunhelp), or the ADS functions 
    ads_help() and ads_setfunhelp(). By not requiring a file extension, 
    developers can call for Windows Help or Platform Independent (PI) Help 
    on other platforms with no source code change.

    The following is the search rule:

    If the file has an extension, look for that file,

      - find it                  SUCCEED
      - don't find it            FAIL

    If file has no extension

      - if this is AutoCAD for Windows, append .hlp
      - try again to find that file
      - find it                  SUCCEED
      - don't find it            FAIL
      - try again by appending .ahp
      - find it                  SUCCEED
      - if still not found try original file name with no extension
      - find it                  SUCCEED
      - don't find it            FAIL

    Note: The file without an extension isn't tried until last, so that 
    for example on UNIX, acad.ahp will be searched for before acad.

Platform-Independent Help from a CD-ROM or a Read-Only Directory
----------------------------------------------------------------

    AutoCAD writes a binary index (.hdx) file the first time it reads a 
    Platform Independent (PI) Help file. Normally, this file is written to 
    the same directory where the Help source file is found. If the source 
    file is in a read-only directory (for example, a restricted network 
    drive or a CD-ROM), this file can't be written to the Help source file 
    directory.

    The following sequence illustrates how PI Help places the .hdx file. 
    You can force AutoCAD to place the .hdx file anywhere on the ACAD path 
    by placing a dummy .hdx file in that directory.  

    - find the help source file
    - can I open an index file for writing that directory?
    - yes                        SUCCEED
    - no
    - look for an index file of that name on the acad path
    - find one?
    - yes, can I open an index for writing there?
    - yes,                       SUCCEED
    - no, keep trying
    - no, look for acad.ini on acad path
    - find it?
    - yes, can I open an index for writing there?
    - yes                        SUCCEED
    - no                         FAIL

    The next time, the same logic is used to find the built index file.
    The message "Help index in: xxx." displays on the command line 
    to indicate where the file was written.

Sample Solid Models on CD-ROM
-----------------------------

    Solid models are included with the Release 13 base system. These models 
    provide full 3D descriptions of an object, suitable for rendering. One 
    model, steering.dwg, is included with the Examples and Samples option of 
    the AutoCAD install/setup. Additional example models have been included 
    on the CD-ROM. Because of their size, they're not installed as part of 
    Release 13, however, you can either copy them to your hard drive or open 
    them directly from the CD. To provide the best display of each model, 
    use the HIDE command.

    The SAMPLE directory of the CD contains:

    File name                 Description              
    ---------                 -----------  
    robot.dwg                 Industrial robot 
    shave.dwg                 Disposable razor 
    carwheel.dwg              Car wheel          
    ductpath.dwg              Profile along a path 
    steering.dwg              Steering wheel       

Loading acadr13.lsp
-------------------

    The file acadr13.lsp is loaded immediately before acad.lsp to ensure 
    that the AutoCAD features provided by acadr13.lsp are always available 
    regardless of which menu is loaded. 

    The file acad.lsp extends basic AutoCAD. You should NOT modify 
    acadr13.lsp.

Known Geometry Limitations
--------------------------

Using CTRL+C in modeling operations

    There are known memory leaks when you cancel solid and region 
    modeling operations by pressing CTRL+C. If you cancel a lot of
    modeling operations in one AutoCAD session, AutoCAD might use
    up all available memory and crash.

Solids with poles

    Solids with poles can lead to failures during Boolean operations, 
    mass property computations, sectioning, slicing, interference 
    checking, and so on.

    Such solids result mostly from the TORUS command where the major
    and minor radii are equal, and from the REVOLVE command where the
    region being revolved touches the axis of revolution.

Boolean operations

    Boolean operations between solids with nearly tangent faces don't 
    work reliably. Eliminating the tangency or making the faces
    exactly tangent should help.

Revolved solids

    If the axis of revolution touches the region being revolved,  
    further operations on the solid created could fail. Some possible 
    workarounds include

    - Making sure that the region isn't tangential to the axis at
      the point(s) of contact.

    - Making sure that the edges that touch the axis are as simple
      as possible. If an edge touching the axis is a spline curve,
      replacing a small portion of that curve near the point of
      contact with a line or a circular/elliptical arc will help.

Tapered extrusions

       Extruding a region with a taper angle can result in a self-
       intersecting solid. Further operations on such a solid won't 
       work reliably.  The EXTRUDE command doesn't catch and report 
       self-intersections in the solid created.  Self-intersections can 
       be eliminated by reducing the extrusion height or the taper angle.

Section and slice through rolling ball fillets

    Sectioning or slicing a solid through rolling ball fillet faces 
    doesn't work reliably. This problem occurs more frequently when the 
    plane passes through the edge where the fillet face meets the 
    neighboring face.

Non-manifold edges and vertices

    Non-manifold edges and vertices may cause problems during Boolean
    operations, particularly when the two solids intersect at these
    non-manifold objects.

Coincident faces, edges, and vertices

    Coincident or almost coincident faces, edges and vertices and
    other singular cases may cause problems during Boolean operations.

Using FILLET and CHAMFER with 3D solids

    The following are issues to note while using the FILLET or CHAMFER
    commands for 3d Solids.

    - Filleting is a local operation, so if the fillet data causes
      the new fillet geometry to interfere with nonadjacent edges or
      faces, the result could be failure of the FILLET command or even
      an invalid solid.

    - Filleting a mixed-convexity edge case quite often has problems.
      That is, if one of the three edges at a vertex has a different
      convexity than the other two, then it is susceptible to failure.
      One workaround is to fillet the odd convexity edge separately,
      and then select the smooth sequence (of three edges) created. 

    - If all the edges incident at a vertex have their tangents lying
      in the same plane and it's desired to fillet them, and simultaneous
      selecting of them fails, try selecting (and blending) them singly.

    - Filleting an edge results in a new blend surface. Often, this surface
      needs to be "capped" by extending nearby surfaces, so that the
      blend surface is restricted properly to define a valid resulting
      solid. ACIS has problems when the capping operation requires
      the extension of spline surfaces. This isn't currently supported.

      In general, operations involving spline curve and surface geometry
      are more prone to failure than other operations. This will continue
      to improve with subsequent releases of ACIS.

    - In some situations, single edge filleting, where the edge is C1
      continuous with an adjacent edge, is not possible. This mainly
      happens when one of the two edges is a spline curve. Typically,
      however, where one of the edges is a line and the other is an arc,
      single edge filleting works.

    - An edge whose two adjacent faces are C1 continuous throughout can't
      be filleted. In general, if ACIS isn't able to fillet an edge since
      it's invalid, or it's a current ACIS limitation, the message
      "Cannot blend this edge" is displayed.

    - Chamfer of a single edge that has at least one adjacent tangent edge
      isn't well handled in ACIS currently, and isn't being allowed. 
   
    - Only chamfers of line and circle-arc edges are permitted.
   
    - Chamfering is a local operation, so if the chamfer data causes
      the new chamfer geometry to interfere with nonadjacent edges or
      faces, the result could be failure of the CHAMFER command or even
      an invalid solid.

    - ACIS has problems handling simultaneous selection of mixed-convexity 
      adjacent edges sometimes and fails to chamfer the selected edges. In
      such cases, chamfering each edge individually often provides the
      desired results.

Section planes

    The SECTION command says that the section plane does not intersect
    the solid even though the plane may be passing through an edge or
    a vertex of the solid. If there's some common area shared between
    the solid and the section plane, a region enclosing that area will
    result. Otherwise, the SECTION command will say that there's no
    intersection between the section plane and the solid.

Effects on objects using ACISOUT to ACISIN

    Some AcDb3dSolid objects will become AcDbBody objects when they're
    written out through ACISOUT and read back in through ACISIN. Because 
    all non-manifold ACIS bodies are converted to AcDbBody objects 
    during ACISIN. Some of these ACIS bodies could qualify as AcDb3dSolid
    objects even though they are non-manifold. But there's no reliable
    way to check at this time if an ACIS body is a valid (manifold or 
    non-manifold) solid.

Effect of DISPSILH with HIDE

    If the DISPSILH variable is ON, the HIDE command will display 
    AcDb3dSolid objects with silhouette edges only. It won't show the 
    internal edges produced by facetting the object.

Effect of offset operation on higher order splines

    Offset operation on higher order splines may not be successful.
    Also, multiple offset operations on splines, i.e. offset of an 
    offset spline, has the potential of splitting the resulting spline
    into multiple small segments resulting in a curve that might not
    be very useful for future operations. For example, you might not
    want to use such a spline as a path to extrude along since it
    will end up creating a large number of sweep sections.

Extruding profiles along a path

    While extruding profiles along path, avoid creating profile and
    path combinations that could result in self-intersecting solids.
    For example, this could happen in extruding larger profiles along 
    paths that have high areas of curvature, i.e. tight corners.

How ACISOUT saves ACIS bodies

    ACISOUT command saves the ACIS bodies using the api_save_entity_list()
    call. To read these bodies, api_restore_entity_list() must be used.

Shape (.shp) Files
------------------

    The shape (.shp) files are provided on the CD only.


========================================================================
WINDOWS-SPECIFIC INFORMATION
============================

Moving an Electronic Document to Hard Disk
------------------------------------------

    The AutoCAD Release 13 documents are available as electronic 
    documents (E-docs). When the E-doc viewer is installed, it's set up 
    for you to view the documents from your CD-ROM drive.

    To use a document, you need to change your setup so that you use 
    the electronic book from your hard disk. (If you copy the entire 
    document set, you will use about 90 megabytes of memory on your hard 
    disk.)
   
    Use the following collection directory structure. When creating your 
    directories, you must use the /books, /ents, and /figures naming 
    structure as indicated below. 

    collection level -->                acad_bks          
                                           |
                                     -------------
                                    |      |      | 
    book level       -->          books  ents  figures
                                    |
                                --------------------------
                               |        |        |        |  
    individual books -->    agibook  tutbook  acrbook  augbook  
    with associated
    subdirectories
    and files

    The individual AutoCAD Release 13 E-doc titles are
 
    E-doc       Full Title
    ----------------------
    agibook     Documentation Guide (roadmap to the docs and Master Index)
    tutbook     Learning AutoCAD for DOS
    acrbook     Command Reference
    augbook     User's Guide
    custman     Customization Guide
    devbook     Developer's Guide
    igdbook     Installation Guide for DOS
    igdbook     Installation Guide for Windows
  
    To change the setup so it uses books from your hard disk:

    1. On your hard disk, create the following directories:

       /collection
       /books

    2. Copy the "book" into the /books directory. For example, to copy the 
       AutoCAD Command Reference onto your hard disk, copy all the files 
       and directories from acad_bks/books/acrbook from the CD-ROM.
       
    3. Copy the /ents and /figures directories from the CD-ROM into your 
       /collection directory.
     
    4. Copy the booklist.txt file from the CD-ROM into your /collection 
       directory. The booklist.txt file contains the complete list of
       the AutoCAD documents and their aliases in Dynatext.

    5. Update the booklist.txt file in a text editor by removing the
       book entry names that aren't in the /collection directory. 

    6. Update your dynatext.ini file COLLECTION line to point to the 
       collection level directory, as follows: 
  
       COLLECTION=;c:\acad_bks=AutoCAD Documents;

       If you don't update your .ini file with the proper location, you'll 
       receive an error message telling you to install your CD-ROM disk.

Menu File Locking
-----------------

    Windows menu files aren't locked in Release 13. It's recommended that 
    if you use a network, you reference menu files locally.

DELL Computer Systems and Electronic Document Display Problems 
---------------------------------------------------------------

    On certain DELL OPTIPLEX 466/L systems with a Tseng video adaptor 
    and on the DELL ET 4000 version 1.11 VESA display driver, text might be  
    "blacked-out" (highlighted in black). This results in certain portions 
    of text from the electronic version of the AutoCAD documentation to be
    unreadable.

Norton Desktop Problems with AutoCAD Dialog Boxes
-------------------------------------------------

    When you have the Norton Desktop for Windows loaded, you might 
    encounter some difficulties with AutoCAD's file dialog boxes. To 
    workaround any problems, press ESC to cancel the dialog box, and then 
    reenter the command.

PostScript and TrueType Font Mapping in acad.ini
------------------------------------------------

    The acad.ini file assumes that AutoCAD's TrueType fonts are not 
    installed in Windows. If you do install AutoCAD's TrueType fonts 
    (by using the Control Panel), the following items in the [MTE Fonts]
    section should be changed as follows:

    bgothl=BankGothic Lt BT;400;0
    bgothm=BankGothic Md BT;400;0
    compi=CommercialPi BT;400;0
    comsc=CommercialScript BT;400;0
    dutch=Dutch801 Rm BT;400;0
    dutchb=Dutch801 Rm BT;700;0
    dutchbi=Dutch801 Rm BT;700;1
    dutcheb=Dutch801 XBd BT;900;0
    dutchi=Dutch801 Rm BT;400;1
    monos=Monospace821 BT;400;0
    monosb=Monospace821 BT;700;0
    monosbi=Monospace821 BT;700;1
    monosi=Monospace821 BT;400;1
    stylu=Stylus BT;400;1
    swiss=Swis721 BT;400;0
    swissb=Swis721 Blk BT;;400;0
    swissbi=Swis721 Blk BT;400;1
    swissbo=Swis721 BdOul BT;400;0
    swissc=Swis721 Cn BT;400;0
    swisscb=Swis721 BlkCn BT;400;0
    swisscbi=Swis721 BlkCn BT;400;1
    swisscbo=Swis721 BdCnOul BT;400;0
    swissci=Swis721 Cn BT;400;1
    swissck=Swis721 BlkCn BT;400;0
    swisscki=Swis721 BlkCn BT;400;1
    swisscl=Swis721 LtCn BT;400;0
    swisscli=Swis721 LtCn BT;400;1
    swisse=Swis721 Ex BT;400;0
    swisseb=Swis721 Ex BT;700;0
    swissek=Swis721 BlkEx BT;400;0
    swissel=Swis721 LtEx BT;400;0
    swissi=Swis721 It BT;400;1
    swissk=Swis721 Blk BT;400;0
    swisski=Swis721 Blk BT;400;1
    swissko=Swis721 BlkOul BT;400;0
    swissl=Swis721 Lt BT;400;0
    swissli=Swis721 Lt BT;400;1
    umath=UniversalMath1 BT;400;0
    vinet=Vineta BT;400;0

    The syntax of each of the above acad.ini entries is as follows:

    <name>=<face>;<weight>;<italic>

    where:

    name         is the AutoCAD font name
    face         is the Windows typeface name
    weight       1-1000 or 0 for default font weight
    italic       0 for upright or 1 for slanted (Italic)


COMPAQ DeskPro XL 566 Users
---------------------------

    Users of COMPAQ DeskPro XL 566's need to make sure that Windows is 
    configured to disable 32-bit disk access. Failure to do this can cause 
    problems in Window's virtual memory subsystem, which will prevent 
    Windows from running properly.

    To disable 32-bit disk access, edit the [386Enh] section of Window's 
    System.ini file, setting the 32BitDiskAccess flag off. For example:

         ;32-BIT ACCESS NEEDS TO BE TURNED OFF IN COMPAQ XL 5/66
         32BitDiskAccess=off

    DeskPro XL 566 user's can also use the 386 Enhanced icon from the 
    Windows Control Panel to change the 32-bit disk access setting. See 
    the Microsoft Windows User's Guide for more information on changing 
    swap file settings.

Windows Virtual Memory and the Swap File
----------------------------------------

    To utilize the full potential of the Windows swap file, based on
    available disk space, you can use the Windows Virtual Memory multiplier
    "PageOverCommit". This switch is placed in the Windows System.ini file.
    The default of this multiplier is 4, when no value is given.

    As an example, if you've set a 128mg permanent swap file and you have
    16mgs of RAM, Windows will use only 64mgs of that swap file with the 
    default settings. If you put the following line under the [386Enh] 
    section of the System.ini file:

    PageOverCommit=8

    Windows will use 16mgs RAM x 8 = 128mgs Virtual Swap space.
    You can verify this by checking "About Program Manager" in the Help
    pull down menu in the Windows Program Manager.

Clipboard Issues
----------------

    The Clipboard features for Release 13 don't gray out depending on data 
    in the Clipboard viewer. The features affected by this are Cut, Copy,
    Copy View, Paste, Paste Special, Links, and Insert Object.

Using Pasted Objects (OLE) in Paper and Model Space
---------------------------------------------------
 
    When TILEMODE is Off (set to 0), pasting OLE objects into AutoCAD
    from other applications, such as Paintbrush, will result in the
    object's belonging to the paper space viewport regardless of any
    model space viewports that might be active.
 
    When TILEMODE is On (set to 1), pasting OLE objects into AutoCAD
    from other applications, such as Paintbrush, will result in the
    object's belonging to the viewport into which they're pasted. They 
    won't move with the viewport when TILEMODE is turned Off (set to 0).

Lack of Response from 16-bit OLE 2.0 Applications
-------------------------------------------------

    AutoCAD might not respond to OLE requests from 16-bit OLE 2.0
    applications. For example, using Insert, Object, from Microsoft
    Word for Windows 6.0 and selecting AutoCAD will result in a message
    that the application can't be found. This is recognized as a known 
    problem with Windows and not necessarily an AutoCAD problem.

Microsoft Mouse Driver 9.01
---------------------------

    Using the Microsoft Mouse driver 9.01 can cause known errors, such as
    GROWSTUB errors. Your pointer might not snap to the default button in
    a dialog box; attempts to access the Mouse Manager in the Windows
    Control Panel cause the Mouse Manager to crash and the Control Panel
    to quit. To correct the problem, exit Windows and reload.

AutoCAD Sessions
----------------

    Only one session of AutoCAD can be run at a time. Before you begin a
    new session of AutoCAD, please wait until any previous session has
    exited completely.

Updated Shaft Application
-------------------------

    Release 13 includes an updated Shaft sample application, which 
    demonstrates a Dynamic Data Exchange (DDE) link between AutoCAD and 
    Microsoft Excel. The Shaft menu is now a partial menu that can be 
    inserted anywhere on the Windows menu bar. For more information on 
    this application, see the comments in the file shaft.mnu, which is 
    located in the Windows sample directory.

Default Mtext Editor Font
-------------------------

    When you choose CANCEL in the Select Font dialog box for a font to be 
    used in the Mtext Editor, AutoCAD uses the Arial font as the default 
    font.

RTF Text and the Mtext Editor
-----------------------------

    RTF text isn't recognized by the Mtext Editor. Text from other 
    programs with embedded formatting will lose formatting when Imported 
    or Pasted into the Mtext Editor.

Using acadfull.mnu
------------------

    The acadfull.mnu file includes pull-down menu access to menu items 
    and toolbar items from acad.mnu. Since acadfull.mnu closely matches 
    the DOS menu with the addition of Windows only tools, such as OLE, 
    it can provide a means of making the transition between DOS and 
    Window's AutoCAD.


========================================================================
DOS-SPECIFIC INFORMATION
========================

Vibrant Driver and Scripts
--------------------------

    You can't use scripts to configure this driver.  

MTEXT and Memory
----------------

    If you run out of memory when MTEXT attempts to use the DOS editor,
    configure your system so that you have more memory. You can put DOS
    in high memory or use the SHROOM command before invoking AutoCAD. 
    Consult your DOS manual for instructions on how you do this.

Importing a File with MTEXT and the Temporary File Name
-------------------------------------------------------

    When you import a file for MTEXT, load the file into the editor and 
    save it using the name AC000512. (the period or fullstop [.] after 
    "AC000512" is required). When you're prompted whether you want to 
    overwrite the existing file of the same name, choose Y (Yes).
      
    The temporary file name AC000512. must exist when using MTEXT in a 
    DOS editor. If you attempt to rename the temporary file to a name 
    other than AC000512., the MTEXT operation will be canceled.


========================================================================
MANUAL CORRECTIONS AND ADDITIONS
================================

General Notes
-------------

Leader Associativity

    Information which implies that leader objects and their
    annotation become associated with each other is incorrect.
    Leader objects and their annotation aren't associated
    with each other.

AutoCAD Command Reference, Publication #00105-010000-5030
---------------------------------------------------------

BHATCH, "Default Properties," page 113

    The section "Default Properties" should be removed.

DDIM, "Arrowheads," page 184 

    In the paragraph describing different arrowheads,
    add the information about the DIMSAH system so that
    it reads as follows:

    If you select different arrowheads for the first
    and second arrowheads, AutoCAD stores the names in
    the DIMBLK1 and DIMBLK2 variable respectively, and
    turns DIMSAH on.

DDIM, "Fit" option, page 186 

    The following option is missing:

    Arrows Only

    If space is available, AutoCAD places text and
    arrowheads between the extension lines. When space
    is available for the arrowheads only, AutoCAD
    places them between the extension lines and the 
    text outside. When no space is available for the
    arrowheads, AutoCAD places them both outside the
    extension lines.

DDIM, "Prefix," page 189 

    The following sentence is incorrect:

    AutoCAD displays how the prefixed dimension text appears in
    the image tile.

    The sentence should read:

    AutoCAD displays the tolerance text depending on the current
    type of tolerance (see "Tolerance," page 190).

    The image tiles change as you pick them, and the value of
    the Method list updates. If you select an item from the
    Method list, the image tiles change to reflect that type of
    tolerance setting.

DDIM, "Suffix," page 189

    The following sentence is incorrect:

    AutoCAD displays how the suffixed dimension text appears in
    the image tile.

    The sentence should read:

    AutoCAD displays the tolerance text depending on the current
    type of tolerance (see "Tolerance," page 190).

    The image tiles change as you pick them, and the value of
    the Method list updates. If you select an item from the
    Method list, the image tiles change to reflect that type of
    tolerance setting.

HATCHEDIT, "Inherit Properties," page 355

    The following sentence should be removed:

    AutoCAD does not allow the properties of a nonassociative
    hatch pattern to be inherited.

LENGTHEN, page 375

    The following sentence should be removed:

    Spline objects can be extended linearly.

MTEXT, pages 434 and 435
 
    The illustration showing the Edit MText dialog box erroneously
    shows a button for spell-checking (Spell). On the following page
    this button is described in the "Spell" section.
 
    Spell-checking within MTEXT is not available. To spell-check any
    text, complete the text creation and then use the SPELL command.
 
PREFERENCES, page 516

    The Render area of the Preferences dialog box is incomplete.
    Add the following options and their descriptions:

       Raster Preview Options
       Specifies the format of a preview drawing.

       Save WMF Preview      Saves the preview drawing in 
                             Windows metafile format (WMF).

       Save BMP Preview      Saves the preview drawing in
                             bitmap format (BMP).

PURGE, page 528

    The following paragraph is incorrect:

    To purge every unreferenced object from a drawing, use
    PURGE, then END, and then restart AutoCAD and try PURGE
    again. Repeat this sequence until PURGE reports that there
    are no unreferenced objects.

    The paragraph should read:

    PURGE removes only one level of reference. Repeat the 
    use of PURGE until there are no unreferenced objects. 

SAVEASR12, page 576

    The following sentence is incorrect:

    AutoCAD saves the original Release 13 drawing to a .bak
    backup file with the same file name.

    The sentence should read:

    If you specify the current drawing as the file name
    to save, AutoCAD saves the original Release 13 to
    a .bak backup file.

SCENE, page 582

    In the paragraph describing Scenes, add the information 
    about the ambient light intensity so that it reads as follows:

    If there are no lights in the drawing and `NONE' is selected, 
    AutoCAD assumes a default `over-the-shoulder' distant light 
    source with an intensity of 1, and an ambient light intensity 
    of 0.

SKETCH, page 594

    The descriptions of the buttons, beginning with the
    section "Pen (pick button)," assume that Tablet mode is 
    turned On.

STYLE, page 618

    In the sentence describing valid file types, include all the
    valid file types so that the sentence reads as follows:

    In the Select Font File dialog box, valid file types include 
    .pfa, .pfb, .shx, and .ttf.

    In the sentence following the "Obliquing angle <current>:
    Specify an angle or press RETURN" prompt, correct the
    values as follows:

    Entering values between -85 and 85 italicizes the text.

DELOBJ, page 705

    The values for objects deleted and retained need to be
    reversed to read as follows:

    1  Objects are deleted.
    0  Objects are retained.

DIMALTTZ, page 706

    The description of the DIMALTTZ system variable is incorrect
    and should be replaced with the following: 

    DIMALTTZ
    Type: Integer
    Saved in: Drawing
    Initial value: 0

    Controls suppression of zeros for alternate tolerance 
    values. DIMALTTZ stores this value when entered on the 
    command line or set in the Alternate Units dialog of the 
    Annotation dialog box.

    0	Suppresses zero feet and precisely zero inches.
    1	Includes zero feet and precisely zero inches.
    2	Includes zero feet and suppresses zero inches.
    3	Includes zero inches and suppresses zero feet.

    DIMALTTZ values 0-3 affect feet-and-inch dimensions only, 
    but you can add 4 to suppress leading zeros in all 
    decimal dimensions (e.g., 0.5000 becomes .5000), and add 
    8 to suppress trailing decimal zeros (e.g., 12.5000 
    becomes 12.5 and 30.0000 becomes 30). Adding 12 (both 4 
    and 8) suppresses both leading and trailing zeros (e.g., 
    0.5000 becomes .5 and 0.0000 becomes 0).

DIMALTZ, page 707

    The description of the DIMALTZ system variable is incorrect
    and should be replaced with the following: 

    DIMALTZ
    Type: Integer
    Saved in: Drawing
    Initial value: 0

    Controls the suppression of zeros for alternate unit 
    dimension values. DIMALTZ stores this value when entered 
    on the command line or set in the Alternate Units dialog 
    of the Annotation dialog box.

    0	Suppresses zero feet and precisely zero inches.
    1	Includes zero feet and precisely zero inches.
    2	Includes zero feet and suppresses zero inches.
    3	Includes zero inches and suppresses zero feet.

    DIMALTZ values 0-3 affect feet-and-inch dimensions only, 
    but you can add 4 to suppress leading zeros in all 
    decimal dimensions (e.g., 0.5000 becomes .5000), and add 
    8 to suppress trailing decimal zeros (e.g., 12.5000 
    becomes 12.5 and 30.0000 becomes 30). Adding 12 (both 4 
    and 8) suppresses both leading and trailing zeros (e.g., 
    0.5000 becomes .5 and 0.0000 becomes 0).

DIMFIT, page 710

    Replace the descriptions of DIMFIT 2 and DIMFIT 3
    with the following:

    2  If space is available, places text and 
       arrowheads between the extension lines. 
       When space is available for the arrowheads 
       only, AutoCAD places them between the extension 
       lines and the text outside. When no space is 
       available for the arrowheads, AutoCAD places 
       them both outside the extension lines.

    3  If space is available, places the text and 
       arrowheads between the extension lines. When 
       enough space is available for text, AutoCAD 
       places the text between the extension lines 
       and the arrowheads outside the extension lines. 
       When enough space is available for arrowheads, 
       AutoCAD places them between the extension lines 
       and the text outside the extension lines. When 
       no space is available for both text and arrowheads, 
       AutoCAD places them outside the extension lines.

DIMTZIN, page 717

    The description of the DIMTZIN system variable is incorrect
    and should be replaced with the following: 

    DIMTZIN
    Type: Integer
    Saved in: Drawing
    Initial value: 0

    Controls the suppression of zeros for tolerance values. 
    DIMTZIN stores this value when entered on the command line 
    or set in the Primary Units dialog of the Annotation dialog 
    box.

    0	Suppresses zero feet and precisely zero inches.
    1	Includes zero feet and precisely zero inches.
    2	Includes zero feet and suppresses zero inches.
    3	Includes zero inches and suppresses zero feet.

    DIMTZIN values 0-3 affect feet-and-inch dimensions only, 
    but you can add 4 to suppress leading zeros in all 
    decimal dimensions (e.g., 0.5000 becomes .5000), and add 
    8 to suppress trailing decimal zeros (e.g., 12.5000 
    becomes 12.5 and 30.0000 becomes 30). Adding 12 (both 4 
    and 8) suppresses both leading and trailing zeros (e.g., 
    0.5000 becomes .5 and 0.0000 becomes 0).

DIMZIN, page 718

    The description of the DIMZIN system variable is incorrect
    and should be replaced with the following: 

    DIMZIN
    Type: Integer
    Saved in: Drawing
    Initial value: 0

    Controls the suppression of the primary unit value. DIMZIN
    stores this value when entered at the command line, or in the
    Primary Units dialog of the Annotation dialog box. DIMZIN also 
    affects real-to-string conversions performed by the AutoLISP 
    rtos and angtos functions

    0	Suppresses zero feet and precisely zero inches.
    1	Includes zero feet and precisely zero inches.
    2	Includes zero feet and suppresses zero inches.
    3	Includes zero inches and suppresses zero feet.

    DIMZIN values 0-3 affect feet-and-inch dimensions only, 
    but you can add 4 to suppress leading zeros in all 
    decimal dimensions (e.g., 0.5000 becomes .5000), and add 
    8 to suppress trailing decimal zeros (e.g., 12.5000 
    becomes 12.5 and 30.0000 becomes 30). Adding 12 (both 4 
    and 8) suppresses both leading and trailing zeros (e.g., 
    0.5000 becomes .5 and 0.0000 becomes 0).

MENUNAME, page 725
 
    The entry for this system variable isn't correct and should
    be changed as follows:
 
    MENUNAME
    (Read-Only)
    Type: String
    Saved in: Application header
 
    The MENUNAME system variable stores the MENUGROUP name. If the
    current primary menu has no MENUGROUP name, the menu file includes 
    the path if the file location isn't specified in AutoCAD's environment 
    setting.

PICKSTYLE, page 728

    The initial value of the PICKSTYLE system variable is 1 and 
    not 3 as documented.

SAVEIMAGES, page 734

    SAVEIMAGES
    Type: Integer
    Saved in: Drawing
    Initial value: 0

    The SAVEIMAGES system variable controls writing graphics
    metafiles for application-defined objects, solids, bodies, 
    and regions.

    The SAVEIMAGES system variable is used to specify whether to
    save the images of application-defined objects, solids, bodies,
    and regions with the drawing. 
       
    0  The application's definition of the objects controls whether
       to save the graphical descriptions of objects. Solids, bodies 
       and regions aren't saved.
    1  Always saves images
    2  Never saves images

    If 1 or, for certain classes, when 0, then application-defined
    objects will be visible if the drawing is reloaded without the 
    supporting application present. The image displayed will be the 
    image that was last described by the supporting application.
      
    If 2 or, for certain classes and solids, bodies, and regions, when 
    0, then no image data will be saved for these application defined 
    objects if the drawing is reloaded without the supporting 
    applications.

    The ability to display application defined objects without
    their application present is very desirable. However, when
    graphical metafiles are saved, your drawing size will be larger 
    and the save time will be longer.

TEXTFILL, page 739 

    The initial value for TEXTFILL is 0, not 1.

AutoCAD User's Guide, Publication #00105-010000-5020
----------------------------------------------------

"Creating an Associative Hatch," page 71

    The following note should be included immediately following the
    steps "To hatch an area":

    When creating an associative hatch, specify one internal
    point per hatch block placement. Specifying more than one
    internal point can produce unexpected results when you edit
    the hatch boundary.

"Editing Hatches," page 197

    The following sentence is only partially correct:
    
    To select an associative hatch without its associative boundary,
    set PICKSTYLE to 0.
    
    It should be fully corrected to read:
    
    To select an associative hatch without its associative boundary,
    set PICKSTYLE to 0 or 1.

"Control keys used to edit text in Windows," page 248

    The keys CTRL+Z don't undo typing. You can, however, still 
    paste back text that you've cut.

"Creating Paragraph Text in Windows," page 248
 
    The illustration showing the Edit MText dialog box erroneously
    shows a button for spell-checking (Spell).
 
    Spell-checking within MTEXT is not available. To spell-check any
    text, complete the text creation and then use the SPELL command.

"Adding Text to Drawings," page 250

    Add the following information in a new section:

    "Special Unicode Characters in MTEXT"

    When using MTEXT, you can create the special characters for the
    degree symbol, plus/minus tolerance symbol, and the diameter
    symbol by entering the following Unicode character strings:

         %\U+00B0        Draws degree symbol
         %\U+00B1        Draws plus/minus tolerance symbol
         %\U+2205        Draws diameter symbol
    
    At the command line or with an external editor (such as the DOS 
    editor), you enter the same character strings, but without the
    % sign:

         \U+00B0        Draws degree symbol
         \U+00B1        Draws plus/minus tolerance symbol
         \U+2205        Draws diameter symbol

    For more information on Unicode, see "Unicode Font Descriptions"
    in chapter 3, "Shapes, Fonts, and PostScript Support" in the 
    AutoCAD Customization Guide. Also see "Using Unicode and Big
    Fonts" on page 255 in the AutoCAD User's Guide.

"Formatting Paragraph Text in a Text Editor," page 266

    The following information is absent from the discussion
    on formatting paragraph text and should be included
    immediately following the table of format codes for
    paragraphs:

    Mtext objects use word-wrap to break long lines into
    paragraphs. If you want AutoCAD to break lines automatically,
    you can create continuation lines by ending lines with
    either a backslash (\) or a space character.

    For example, if you enter the following text into the text
    editor, AutoCAD treats the text as one long line and breaks
    the line based on the width allowed for the Mtext object:

	 This is a test of the \
	 emergency broadcast system.

"Using Font Mapping," page 274 - 275

    The following information is absent from this section and should
    be included after the section "Specifying an Alternative Default
    Font," under the following new section title:

    "Font Mapping and MTEXT in Windows"

    AutoCAD fonts must be identified in the MTE Fonts section of the
    acad.ini file. When Windows doesn't recognize a font, AutoCAD
    displays the Select Font dialog box and prompts for a substitute 
    font to be used. Select a substitute font and then choose OK.

    You can also manually edit the acad.ini, to map the fonts to ones
    that the Mtext editor recognizes. The following example of the
    MTE Fonts section of the acad.ini shows AutoCAD fonts mapped to
    fonts recognized by the Mtext editor. When a pathname is required
    to locate the font, you must include it as shown in the last line
    of this example.

    [MTE Fonts]
    txt=Arial;400;0
    complex=Times New Roman;400;0
    gothice=Lucida Blackletter;400;0
    gothicg=Lucida Blackletter;400;0
    gothici=Lucida Blackletter;400;0
    greekc=Symbol;400;0
    greeks=Symbol;400;0
    italic=Times New Roman;400;1
    italicc=Times New Roman;400;1
    italict=Times New Roman;700;1
    monotxt=Courier New;400;0
    monotxt8=Courier New;400;0
    romanc=Times New Roman;600;0
    romand=Times New Roman;500;0
    romans=Times New Roman;400;0
    romant=Times New Roman;700;0
    scriptc=Script;700;0
    scripts=Script;400;0
    simplex=Arial;400;0
    C:\FONTS\TT\DUTCH.TTF=Times New Roman;400;0

    The syntax of each entry is as follows:

    <name>=<face>;<weight>;<italic>

    where:

    name         is the AutoCAD font name
    face         is the Windows typeface name
    weight       1-1000 or 0 for default font weight
    italic       0 for upright or 1 for slanted (Italic)

"Adding Primary Units," page 318

    The following sentence is incorrect:

    An image tile displays a representation of the prefix and
    suffix you supply.

    The sentence should be corrected to read:

    An image tile displays a representation of the tolerance text
    depending on the current type of tolerance (see "Adding Lateral
    Tolerances," on page 322).

"Adding Alternate Units," page 320

    The following sentence is incorrect:

    An image tile displays a representation of the prefix and
    suffix you supply.

    The sentence should be corrected to read:

    An image tile displays a representation of the tolerance text
    depending on the current type of tolerance (see "Adding Lateral
    Tolerances," on page 322).

"Compatibility with Release 12," page 592

    Freeplotting (acad -p)

    Freeplotting, the ability to plot from AutoCAD without using a 
    network license with the -p command line argument, has been
    removed.

AutoCAD Customization Guide, Publication #00105-010000-5040
-----------------------------------------------------------

ssget, page 472

    Add the information about pt_list so that the paragraph
    reads as follows:

    The following examples of ssget require that a list of points
    be passed to the function. The pt_list can't contain zero-length
    segments.

"Group codes by entity type," DIMENSION, page 549
     
    The Dimension group code 70 flag value of 32 is missing from
    the table, and should be described as follows:

        32   Added to other codes if the block reference in
             group code 2 is only referenced by this dimension

"Group codes by entity type," SPLINE, page 555

    The meanings of group codes 70 and 71 are incorrectly reversed.
    They should read as follows:
 
    70   Spline flag (bit values):
          1   Closed spline
          2   Periodic spline
          4   Rational spline
          8   Planar
         16   Linear (Planar bit is also set.)
 
    71   Degree of the spline curve

"Predefined Attributes"

    Add the following new attribute definitions to the specified pages:

    page 623, fixed_width_font = <true-false>; 

    If true, specifies that a list box or popup list will display text
    in a fixed pitch font. This provides for easier spacing or tab
    alignment of columns. The fixed_width_font attribute is functional
    on Windows/NT only.

    page 627, password_char= "<char>"; 

    Specifies the character to be used as the password character. If
    password_char is specified and is not null, that character is
    displayed in the edit box instead of the characters entered by the
    user. The use of this attribute has no effect on the retrieval of
    the value entered by the user, it only alters the display of the
    characters in the edit box.

    page 627, tab_truncate = <true-false>; 

    If true, specifies that text in a list box or popup list is
    truncated if it is larger than the associated tab stop. This
    prevents text with lots of M's followed by a tab, for example, from
    pushing the following text past its tab stop. The tab_truncate
    attribute is functional on Windows/NT only.

AutoCAD Installation Guide for DOS, Publication #00105-010200-5000  and 
------------------------------------------------------------------

AutoCAD Installation Guide for Windows, Publication #00105-011400-5000
----------------------------------------------------------------------

"CalComp 3300 Series Tablets, page 117 (DOS), page 104 (Windows)
 
    Add the following paragraph after the last item in 
    configuring the switch settings:
 
    Note: If the AutoCAD cursor oscillates while using the CalComp
    DrawingBoard digitizer, change the setting of soft switch
    number 7 on bank B from 1 to 0 on the digitizer.

"Raster File Format," page 171 (DOS), page 148 (Windows) 

    You can't modify the Raster file export ADI 4.2 
    (plexport.exp) configuration at plot time by using a 
    plot configuration parameters file (.pcp). Nor
    can you do this in the PLOT command's Change Device 
    Requirements dialog box. You must, instead, reconfigure
    the driver using the CONFIG command.

"Configuring the Tablet," page 114 (DOS), page 100 (Windows)

    Add the following section after the "Configuring the Tablet" section
    
    "Using the Tablet Swap"

    Tablet swap lets you change the function of each of the four menu areas
    on the template. Three areas are reserved for use by AutoCAD; the fourth
    can be used for a custom menu or an independently developed application.

    To make a swap, pick one of the four tablet icons located below the
    lower-right corner of the screen area. You can swap at any time, even
    when a command is active. Picking an icon a second time swaps to the
    original menu.

    The first icon on the left swaps the top area of the template to a 
    blank menu. This blank menu area is the same as previous versions of 
    the AutoCAD template and can be used for personal applications and 
    menu items.

    The second icon swaps the left area of the template. ZOOM and other
    display commands cancel the command in progress. VPOINT and DVIEW
    commands refer to the current UCS. When you swap back, display
    commands are transparent, and VPOINT and DVIEW refer to the World
    Coordinate.

    The third icon swaps the right area of the template. This swap
    changes units from Imperial (English) to metric.

    The fourth icon swaps the bottom area of the template. This swap
    changes the OSNAP picks (T12-22) to running OSNAP by resetting
    the OSMODE system variable. When you swap back, the last running
    OSNAP is the default for OSNAP override.

    When you make a swap, a number (1-4) replaces one of the four stars
    at the top of the screen menu. For instance, picking S19 and S21
    replaces two stars. To reset all menus areas to their original
    state, pick the heading AutoCAD above the line of stars.

    Command line prompts inform you of each swap if the EXPERT system
    variable is in the range of 0-3. A setting of 0 (default) gives
    you full prompts, while a setting of 1-3 gives you shorter prompts.
    A setting of 4 or above suppresses all prompts.

Enabling the Metric Numeric Menu
 
    The numeric menu (tablet menu area 3) on the tablet template is set
    to Imperial units (e.g. Inches) by default. The default should be
    determined by the measurement setting in the acad.ini file or the
    configured units in AutoCAD. To enable the metric numeric menu, 
    swap this area by selecting the tablet swap icon (S21 on tablet). 
    At the command line AutoCAD displays the message:

        Alternate tablet area 3 loaded. Select Metric units from
        the Numeric menu.

    Selecting this swap icon again will return the numeric menu back to
    Imperial units

AutoCAD Developer's Guide (electronic document)
-----------------------------------------------

    All occurrences of the file name acad.arx should be replaced with
    the correct file name: acad.rx.

