
       ============================================================= 
             READC2A.TXT - AutoCAD R13c2a Maintenance Release
       ============================================================= 

                            April 3, 1995

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

    R13c2a Maintenance Release Information
    
        Purpose
    
        Background
    
        General Questions and Answers
    
        Installation Procedure
    
        What Problems Does it Fix?
        
        Additional Information
        
            Platform Independent Issues
            
            AutoCAD SQL Interface (ASI) Issues
        
            Documentation Issues

                Updates to the Windows/NT Installation Guide
            
                Updates to the AutoCAD Customization Guide
            
                Updates to the AutoCAD Developer's Guide

    R13c1 Maintenance Release Information
    
        What Problems Does it Fix?
        
        Additional Information
        

    
========================================================================== 
PURPOSE
======= 
Autodesk is committed to delivering products of the highest quality. With 
any major software release, some problems 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 AutoCAD Release 13c2a.

========================================================================== 
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 full 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 or configuration options.


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

Release 13 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).

- 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. A text file for each patch is posted so customers can determine 
whether they need a particular patch.  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.  Please contact your Authorized Autodesk 
Reseller or your local Autodesk office for a copy of the latest patch.

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 customers do these patches affect?

Software patches are distributed as either an Update Patch or a 
Maintenance Patch.

Update Patches typically contain a limited number of bug fixes or fixes to 
bugs that may not affect large groups of customers.  These patches are 
made on an as-needed basis.  Autodesk recommends that dealers distribute 
Update Patches to customers who have reported the specific problems that 
the patches fix.  Since we do not want to inconvenience our customers with 
multiple patches in a relatively short period of time, we do not recommend 
that these fixes be distributed to all customers.  However, some customers 
will always want the latest version and are willing to take the time to 
install it.  These customers should either download the patches 
electronically or work out an arrangement with their dealer.

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 Release 13 customers.  It is our goal to 
have all customers synchronized with the latest Maintenance Release.

Autodesk also recommends that dealers include the latest patch with any 
new sales or in any new installations.

- 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 R13c1 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 approximately forty-five minutes.

- 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?

Patches may be of two types:  historical and incremental.  Historical 
patches may be applied to more than one prior version.  For example, the 
C2 historical patch may be applied to C0, C0a, or C1.  It can determine 
which version it is trying to patch.  Incremental patches may only be 
applied to a single version.  For example, the C2 incremental patch may 
be applied to C1 only.  Incremental patches tend to be smaller than 
historical patches and are therefore better suited to electronic 
distribution.

The patch name indicates both the AutoCAD version that results from 
applying the patch and the minimum required current version. For example, 
the R13c2a_c2 patch must be applied to an installed R13c2 version of 
AutoCAD, the R13c2a_c1 patch can be applied to version R13c1 or later 
(i.e., R13c1a or R13c2), and the R13c2a_c0 can be applied to any version 
of AutoCAD Release 13.

- Should I exchange any unopened or uninstalled product?

It is not necessary to exchange existing product -- simply run the 
appropriate patch(es) after the standard installation.


========================================================================== 
INSTALLATION PROCEDURE
====================== 
If you are installing the R13c2a_c0 Historical patch (available only on 
CD), you simply install the latest patch.  The software determines the 
patch history of your software and automatically updates the appropriate 
files.  If you use the R13c2a_c1 Incremental patch, you must have R13c1 
installed prior to installing R13c2a.

-  On which versions of AutoCAD Release 13 does the R13c2a update work? 
     
The R13c2a update works with all English-language versions of Release 13 
for PCs. There are, however, eight separate update program files for the 
different versions of AutoCAD and the two patch types: 
 
     Historical, DOS Unlocked          Incremental, DOS Unlocked
     Historical, DOS Locked            Incremental, DOS Locked
     Historical, WIN Unlocked          Incremental, WIN Unlocked
     Historical, WIN Locked            Incremental, WIN Locked
     
The update for the locked version should be applied to the network 
version of AutoCAD. 

-  What about compatibility? 
     
No new authorization codes are required, and the serial number and 
personalization information of the installed copy of AutoCAD is retained. 

Reconfiguration is only necessary for those drivers that are updated with
this patch. The R13c2a update preserves existing configuration information.

-  How do you apply the R13c2a update? 
     
The update is applied after AutoCAD has already been installed, and must 
be applied separately to the DOS and Windows executables and to the files
in the common directory.

REMEMBER: If you are installing the R13c2a patch from media other than a 
CD, you have the incremental patch.  To install the incremental patch you 
must have installed the R13c1 patch prior to installing R13c2a.

1.  Because this is an extensive patch which involves many files, you may
wish to back up your current installation. In particular, you should back 
up all customized files.  The R13c2a patch program fails if it attempts to 
update a file that has been modified.  Therefore, certain files that are 
more likely to have been modified by the user are replaced rather than 
updated.  After the patch process is complete, it is up to you to add your 
modifications back into the updated files.

    Customized Files
    ----------------
    We highly recommend that you back up the following files (these files 
    are replaced by the patch process): 

        DOS                     Windows
        ---------------------   ------------------------
        support/acad.dwg        support/acad.dwg
        support/acad.mnl        support/acad.mnl
        support/acad.mnu        support/acad.mnu
        support/acad.pgp        support/acad.pgp
        support/acadr13.lsp     support/acadr13.lsp
                                support/acad.mnc
                                support/acad.mnr
                                support/acad.mns
                                support/acadfull.mnl
                                support/acadfull.mnu

    The installation batch files will also remind you that these files
    should be backed up prior to proceeding with the patch.

    Other files
    -----------
    The following files are updated by the patch process:

        DOS
        --------------------------------------------------------
        acad.exe                        drv/dgpms.exp
        acad.xmx                        drv/dgpsg.exp
        acadapp.exp                     drv/dl153100.res
        acadl.exp                       drv/plep.exp
        acadps.exp                      drv/plexport.exp
        ads/ads.lib                     drv/plhpgl2.exp
        ads/mvcads13.lib                drv/plpadi.exp
        ads/sample/msvcsamp.bat         drv/plpcan.exp
        ads/sample/w100samp.bat         drv/plpcanbj.exp
        ads/wcads100.lib                drv/plpcc.exp
        ase.arx                         drv/plpfile.exp
        ase/aseaph30.lib                drv/plphip.exp
        ase/aseapm80.lib                drv/plphplj.exp
        ase/aseclass.h                  drv/plphplp.exp
        ase/aserpm80.lib                drv/plphppj.exp
        ase/asesmp.exp                  drv/plppost.exp
        ase/asiaph30.lib                drv/plppro.exp
        ase/asiapm80.lib                drv/rcpdlx.exp
        ase/asiclass.h                  drv/rhpcanbj.exp
        ase/asismp.exp                  drv/rhppj.exp
        ase/asiucode.h                  drv/rhprtl.exp
        ase/sample/asesmp.lsp           geom3d.exp
        asidb3.exp                      geomcal.exp
        asidb4.exp                      kernel32.dll
        asifxp.exp                      rasterin.exp
        asipdx.exp                      readme.ads
        asipdx16.exe                    render.arx
        cfig386.exe                     render.xmx
        dosstyle.dll                    sample/acad.mnd
        drv/dgcal.exp                   support/acad.mnu
        drv/dgkur1.exp                  support/hpmplot.exp
        drv/dgkur23.exp                 support/r13new.dcl
        drv/dgphit.exp                  support/r13new.lsp
        readme.ase                      tellme.exe
        readme.drv                      readme.ren
        
        Windows/NT
        --------------------------------------------------------
                                        drv/plphip.dll
        acad.exe                        drv/plphplj.dll
        acad.xmx                        drv/plphplp.dll
        acadapp.exe                     drv/plphppj.dll
        acadbtn.dll                     drv/plppost.dll
        acadps.exe                      drv/plsys.dll
        acadres.dll                     dsacad.dll
        acw32s32.dll                    dsai.dll
        addisp16.dll                    dsai.hlp
        addisp32.dll                    geom3d.exe
        ads_perr.exe                    geomcal.exe
        ase.arx                         helloads.exe
        ase/aseatm80.lib                mfcblank.exe
        ase/aseclass.h                  mfclist.exe
        ase/asertm80.lib                mtedit.dll
        ase/asesmp.exe                  nsapi32.dll
        ase/asiatm80.lib                rasterin.exe
        ase/asiclass.h                  readads.wri
        ase/asismp.exe                  readme.wri
        ase/asiucode.h                  render.arx
        ase/sample/asesmp.lsp           render.xmx
        asidb3.exe                      sample/acad.mnd
        asifxp.exe                      sample/acadfull.mnd
        asiodbcs.exe                    sample/ddeads.exe
        asipdx.exe                      sample/ddeadspp.exe
        asipdx16.exe                    sample/ddelisp.exe
        conlin.exe                      sample/shaft.exe
        drv/dgcal.dll                   sample/shaft.mnu
        drv/dgcaln.dll                  sample/shaft.xls
        drv/dgkur1.dll                  support/acad.hlp
        drv/dgkur1n.dll                 support/acad.mnc
        drv/dgkur23.dll                 support/acad.mnr
        drv/dgkur23n.dll                support/acad.mns
        drv/dgphit.dll                  support/acad.mnu
        drv/dgphitn.dll                 support/acadfull.mnl
        drv/dgpsg.dll                   support/acadfull.mnu
        drv/dgpsgn.dll                  support/hpmplot.exe
        drv/dgwintab.dll                support/tutorial.hlp
        drv/dgwintbn.dll                support/tutorial.lsp
        drv/plexport.dll                tadc.exe
        drv/plhpgl2.dll                 tutorial/quiktour.tbk
        drv/plpcan.dll                  tutorial/whatsnew.tbk
        drv/plpcc.dll                   winnet32.dll
        drv/plpfile.dll                 readase.wri
        ads/cpp/adscpp/adscpp.inc       readdrv.wri
        ads/cpp/adscpp/adscpp.mak       readren.wri
        ads/cpp/adscpp/ddeads/ddeads.inc
        ads/cpp/adscpp/ddeads/ddeads.mak
        ads/cpp/adsmake.nt
        ads/cpp/amake.bat
        ads/cpp/dde/adsdde.inc
        ads/cpp/dde/adsdde.mak
        ads/cpp/general/adsbase.inc
        ads/cpp/general/adsbase.mak
        ads/cpp/general/adsdxf.cpp
        ads/cpp/general/adsdxf.h
        ads/cpp/helloads/helloads.cpp
        ads/cpp/helloads/helloads.inc
        ads/cpp/helloads/helloads.mak
        ads/cpp/mfcads/mfcads.inc
        ads/cpp/mfcads/mfcads.mak
        ads/cpp/mfcads/mfcblank/mfcblank.mak    
        ads/cpp/mfcads/mfcblank/mfcblank.rc
        ads/cpp/mfcads/mfclist/mfclist.mak
        ads/sample/winads.mak
        ads/win/ddeconv.h
        ads/win/ddewin.h
        ads/winads.lib

        Common
        --------------------------------------------------------
        acis.dll                        support/acad.dcl
        acrx/lib/rxapi.lib              support/acad.dwg
        acrx/sample/gravity.cc          support/acad.mnl
        acrx/sample/mkarx.mak           support/acad.pgp
        ads/adslib.h                    support/acadr13.lsp
        ads/sample/cal.c                support/ddattdef.lsp
        ads/sample/calerr.c             support/ddchprop.lsp
        ads/sample/callex.c             support/ddim.dcl
        ads/sample/calstdf.c            support/ddmodify.dcl
        ads/sample/calusrf.c            support/ddmodify.lsp
        ads/sample/mountain.c           support/ddrename.lsp
        ads/sample/sld2ps.c             support/ddview.lsp
        ads/sample/util.c               support/ddvpoint.dcl
        fonts/monotxt.shx               support/filter.lsp
        fonts/txt.shx                   support/mvsetup.lsp
        nsrvdi.exe                      support/xplode.lsp
        nsrvdn.exe                      tutorial/ex06.dwg
        nsrvni.nlm                      tutorial/ex07.dwg
        sample/psfilpat.dwg             tutorial/ex08.dwg
        support/acad.ahp                tutorial/ex10.dwg

2.  The R13c2a update adds the following new files to your installation.

        DOS
        --------------------------------------------------------
        ads/sample/vc2samp.bat  asiora.exp      msvcrt20.dll
        ads/vc2ads13.lib        asiora.xmx
        ads/vc2ads13.lnk        asiora16.exe

        Windows/NT
        --------------------------------------------------------
        asiodbc.exe             drv/ntlock
        asissrv.exe             drv/ntlock/i386
        asissrv.xmx             drv/ntlock/i386/rnbovtmp.
        nsapint.dll             drv/ntlock/i386/sentinel.
        nslms32.dll             drv/ntlock/i386/senttemp.
        nsrvgx.exe              drv/ntlock/oemsetup.inf
        nsrvgx.hlp              drv/ntlock/snti386.dll
        nticons.exe

        Common
        --------------------------------------------------------
        ads/fake_xmf.h          sample/bmake.dcl
        ads/sample/mkapps.bat   sample/bmake.lsp
        ads/sample/mkapps.nt    

3.  You need the appropriate update diskette or update program file for 
your specific AutoCAD version (unlocked or locked/network, DOS and/or 
Windows). You also need at least 15MB to 20MB of free hard disk space on 
the drive that contains your AutoCAD executable file, ACAD.EXE, in order 
to apply the update.

4.  The following installation instructions assume that you have installed 
AutoCAD DOS in the \acadr13\dos directory and/or AutoCAD Windows in the 
\acadr13\win directory on drive C.  If you have installed AutoCAD on a 
drive other than C or in directories with names other than the defaults, 
substitute your drive/directory names in the commands listed below for the 
default directory names. These instructions also assume that your floppy 
drive is drive A and your CD ROM drive is drive D.  If you are installing 
from a floppy drive other than A or a CD ROM drive other than drive D, 
replace those shown with drive letters appropriate to your system.

To complete the patch installation you must run a different batch file 
for each of the following items that apply to your installation:

    * AutoCAD for DOS - if you have installed AutoCAD for DOS.
    * AutoCAD for Windows - if you have installed AutoCAD for Windows.
    * Common files - must be installed.
    * AutoVision - if you have installed AutoVision.

    AutoCAD for DOS
    ---------------
    a. Navigate to the directory that contains the DOS ACAD.EXE file. 
       For example, enter the following at the DOS prompt: 
     
         c: 
         cd \acadr13\dos 
     
    b. If installing the unlocked version of the Historical patch from a 
       CD, enter the following: 
     
         d:\c2patch\dosinst d: /U
       
       or, if installing the locked version of the Historical patch from 
       a CD, enter the following:

         d:\c2patch\dosinst d: /L
     
    or,
     
    b. If installing the Incremental patch from a floppy drive, place the 
       disk labeled "Disk #1" in drive A, and enter the following to 
       install the unlocked version: 
     
         a:\dosinst a: /U

       or the following to install the locked version:

         a:\dosinst a: /L
     
    or, 
     
    b. If installing the Incremental patch from a directory on the hard 
       drive such as c:\update, enter the following to install the 
       unlocked version: 
     
         c:\update\dosinst c:\update /U
       
       or the following to install the locked version:
       
         c:\update\dosinst c:\update /L
    
    and follow the instructions on the screen. 
     
    AutoCAD for Windows
    -------------------
    a. Navigate to the directory that contains the Windows ACAD.EXE file. 
       For example, enter the following at the DOS prompt: 
     
         c: 
         cd \acadr13\win 
     
    b. If installing the unlocked version of the Historical patch from a 
       CD, enter the following: 
     
         d:\c2patch\wininst d: /U
       
       or, if installing the locked version of the Historical patch from 
       a CD, enter the following:

         d:\c2patch\wininst d: /L
     
    or,
     
    b. If installing the Incremental patch from a floppy drive, place the 
       disk labeled "Disk #1" in drive A, and enter the following to 
       install the unlocked version: 
     
         a:\wininst a: /U

       or the following to install the locked version:

         a:\wininst a: /L
     
    or, 
     
    b. If installing the Incremental patch from a directory on the hard 
       drive such as c:\update, enter the following to install the 
       unlocked version: 
     
         c:\update\wininst c:\update /U
       
       or the following to install the locked version:
       
         c:\update\wininst c:\update /L
     
    and follow the instructions on the screen. 

    Common Files
    ------------
    a. Navigate to the directory that contains the "common" directories. 
       For example, enter the following at the DOS prompt: 
     
         c: 
         cd \acadr13\common 
     
    b. If installing the Historical patch from a CD, enter: 
    
         d:\c2patch\cominst d: 
     
    or,
     
    b. If installing the Incremental patch from a floppy drive, place the 
       disk labeled "Disk #1" in drive A, and enter: 
     
         a:\cominst a: 
     
    or, 
     
    b. If installing the Incremental patch from a directory on the hard 
       drive such as c:\update, enter: 
     
         c:\update\cominst c:\update 
     
    and follow the instructions on the screen. 

    AutoVision
    ----------
    a. Navigate to the directory that contains the AutoVision patch files.
       For example, if you are installing from a floppy drive, enter the 
       following at the DOS prompt: 
     
         a: 
         cd \c2patch\autovis
       
       or, if you are installing from a CD, enter:
       
         d:
         cd \c2patch\autovis
       
    b. Now enter the batch command followed by the drive and directory
       where you installed the AutoVision filed.  For example, if you 
       installed the AutoVision files in the \av directory on the C drive
       enter the following:
       
         update c:\av


5.  The update is applied. This file, READC2.TXT, is also installed into 
the AutoCAD directory by the update program.  

6.  If you are running Windows NT and have installed AutoCAD for Windows,
the following instructions will set up an AutoCAD program group and icons 
in your Windows NT Program Manager.

    a. Choose Run from the File menu in the Windows NT Program Manager,
       enter the following in the Command Line edit box, and choose OK:
       
         c:\acadr13\win\nticons.exe
       
       (The NTICONS.EXE file is installed in the same directory as the 
       Windows ACAD.EXE file)
    
    b. Follow the instructions on screen.
       
7.  Launch AutoCAD as you normally would.  If you are using one of the 
display or digitizer drivers that was updated with the R13c2a patch, you 
are prompted to reconfigure those devices.  To retain your existing 
settings, accept the default (press RETURN) at all prompts to complete 
the reconfiguration.  You are not prompted to reconfigure any plotter
drivers that have been updated with the C2 patch.


========================================================================== 
WHAT PROBLEMS DOES IT FIX?
========================== 
This section explains the problems that are fixed with the R13c2a update.
The fixes are organized by the following topics:

  - Dimensioning and Tolerance Fixes
  - DXFIN, SAVEASR12, OPEN, and NEW Fixes
  - Object Creation and Editing Fixes
  - ASE Fixes
  - Rendering and File Export Fixes
  - Viewing and On-line Fixes
  - Customization/Developer Fixes


Dimensioning and Tolerance Fixes
--------------------------------
     --  DDIM now gives you the choice of stacked or longhand fraction 
formats for both architectural and fractional units styles. You now have 
a full range of choices over available styles for fractional unit formats.
     
     These choices are available through the DDIM Annotation dialog 
Primary Units and Alternate Units options. They can also be specified with
the dimensioning system variables DIMUNIT and DIMALTU. Both DIMUNIT and 
DIMALTU now accept values of 6 or 7, where the values are as follows:
 
     1   Scientific
     2   Decimal
     3   Engineering
     4   Architectural (stacked)
     5   Fractional (stacked)
     6   Architectural
     7   Fractional
 
     The new values are not accepted by the LUNITS system variable because 
the units formatting controlled by LUNITS cannot result in an MText stack. 

     --  The block name for the Right-angle arrowhead is now "OPEN90" 
to make it consistent with the international versions of AutoCAD.

     --  Underscored commands are now recognized at the Dim prompt.

     --  Dimensioning commands now correctly handle instances where the 
font file is not available by generating a text-free dimension block. 

     --  DIMTEDIT no longer changes the position of the selected dimension
when the UCS is near to perpendicular.

     --  The DIMDIAMETER and DIMRADIUS commands properly handle dimension 
placement using a DIMBLK of "DOT".

     --  The DIMANGULAR command correctly displays an error message for 
an invalid object selection and returns to the object selection prompt. 

     --  The first point of a leader is placed properly when Ortho mode 
is on. 

     --  AutoCAD properly handles the canceling of the DIM:Leader command
at the "Dimension text <>:" prompt. 

     --  The text in a tolerance object is correctly centered. 

     --  AutoCAD now allows an ENDPOINT osnap on a tolerance object. 


DXFIN, SAVEASR12, OPEN, and NEW Fixes
-------------------------------------
     --  The DXFIN command correctly assesses the contents of the current 
drawing when making the decision to do a partial or full DXFIN. 

     --  A partial DXFIN of an mline no longer causes the mline to lose 
its scale. 

     --  The SAVEASR12 command converts overlaid xrefs into attached 
xrefs. If this causes a circular reference, the xref is rejected when the 
drawing is opened. 

     --  The SAVEASR12 command converts xlines and rays into lines by 
clipping them based on the current drawing extents.  If there are no 
extents (for example, there are no objects other than xlines and rays),
the drawing is clipped based on the current view.  If xlines or rays pass
through the current view, that portion is converted into lines. 
Note: Due to the "infinite" nature of xlines and rays, they are not taken
into consideration when AutoCAD calculates the extents. 

     --  The SAVEASR12 command now converts the background fill color of 
mlines into the proper color solid-filled objects. 

     --  When opening an R12 drawing with layers marked as DELETED 
(typically converted from other CAD applications), AutoCAD places objects 
on those layers on layer 0. 

     --  The OPEN command's Find File, Search option now handles wild 
cards in the following way: if the search string does not contain path 
separators, the search will try to match either the full path or just the 
file name portion of the path. 

     --  When you start a new drawing (with the NEW command) after opening 
a drawing as read-only, the new drawing's status is no longer sets as 
read-only. 

     --  The SAVENAME system variable is properly updated. 


Object Creation and Editing Fixes
---------------------------------
     --  Many problems with the Object Grouping and Associative Hatching 
features have been resolved.

     --  DDMODIFY properly modifies aspects of leader objects and 
functions properly with R12 dimensions. 

     --  The PERP Osnap interacts properly with spline endpoints. 

     --  DDATTDEF now uses a default of 0,0,0 for the insertion point of 
middle justified text if no insertion point is specified. 

     --  The RECTANG command functions properly with Running Osnaps. 

     --  AutoCAD properly handles the rejection of non-closable splines 
by the SPLINEDIT command. 

     --  The MLINE, XLINE, and RAY commands now display polar coordinates 
(dist>ang) in the status bar when COORDS is set to 2. 

     --  Mline objects can now be used as a reference when creating an 
xline. 

     --  MTEXT properly handles more than 256 text styles. 

     --  Mtext objects can now be exploded into text objects. 

     --  The MTPROP command correctly converts vertical text to 
horizontal text. 

     --  Ctrl+X properly deletes selected objects. 

     --  The time required for AutoCAD to create layers has been reduced,
and objects on frozen layers now display properly in paper space. 

     --  The BHATCH command correctly handles invisible attributes. 

     --  The -GROUP (command line version) command properly applies 
wild-card specifications.  

     --  The text in a complex linetype scales properly. 

     --  Edits performed on a group now affect the objects within the 
group that are on a layer that is off. 

     --  AutoCAD properly handles drawings with xrefs nested three or more
levels deep. 


ASE Fixes
---------
     --  The ASE BIT and BIT VARYING data types work properly with the 
Oracle 6 driver. 

     --  In ASE, the datatypes DATE and TIME are now prohibited. 

     --  The ASE Oracle 6 driver correctly handles tables with a FOREIGN 
KEY REFERENCES constraint. 

     --  ASE correctly processes SQL files containing a line with 
only <TAB> or <SPACE>. 

     --  AutoCAD correctly handles exploded blocks that contain ASE Link 
Path names that already exist in the current drawing. 


Rendering and File Export Fixes
-------------------------------
     --  The STLOUT command now uses the FACETRES system variable. 

     --  By default the BMPOUT command creates a compressed BMP file. To 
generate a non-compressed file, add the line 'BmpOutCompression=0' to the 
[General] section of the acad.ini file.  Compressed BMP files use less 
disk space but may be unreadable by certain applications.  The c0 and c1 
releases of R13 always write compressed BMP files. 

     --  Polyface mesh colors render properly. 

     --  AutoCAD renders properly to a TGA file. 


Viewing and On-line Fixes
-------------------------
     --  DDVIEW properly handles view names that include a hyphen. 

     --  An Aerial View alert message now tells users that fast zooming 
must be enabled in order to use the Aerial Viewer. 

     --  The QuickTour feature runs properly when the TUTORIAL directory 
is added to the support path. 

     --  On-line help is now available during the CONFIG command. 


Customization/Developer Fixes
-----------------------------
     --  AutoCAD now allows support paths of greater than 256 characters. 

     --  The allowable string length of the <cfgname> and <cfgval> 
arguments of the AutoLISP (setcfg) and (getcfg) functions has been 
increased to 132 and 347 characters (respectively).

     --  AutoCAD now allows editing of toolbar icons. 

     --  The sample application BMAKE is now included with AutoCAD. 

     --  The new DCL attribute 'password_char' functions properly on DOS. 

     --  The ADS functions ads_setcfg, ads_getcfg, ads_dictsearch, and 
ads_dictnext work properly. 

     --  The AutoLISP (set_tile) function correctly handles a value of ""
(the null string). 

     --  The AutoLISP (grvecs) function properly honors XOR ink. 

     --  The AutoLISP and ADS entmake functions now properly accept a 
group code 48 in an entity definition list. 

     --  1005 xdata group codes within an exploded block are correctly
updated to the new handles. 

     --  The 2 group code (block name) of a dimension object is now
optional for the entmake function.  If the block name is omitted from the
entity definition list, AutoCAD creates a new one.  Otherwise, AutoCAD 
creates the dimension using the name you provide.

     --  The AutoLISP and ADS/ARX initget function can now provide
localized keywords.  The following syntax for the keyword string allows 
input of the localized keyword while it returns the 'language independent'
keyword:

    "<local1> <local2> <localn> _<indep1> <indep2> <indepn>"

Where <local1> through <localn> are the localized keywords, and <indep1>
through <indepn> are the 'language independent' keywords. There must 
always be the same number of localized keywords as language independent
keywords, and the first language independent is prefixed by an underscore.

For example:

    (initget "Abc Def _Ghi Jkl")
    (getkword "\nEnter an option (Abc/Def): ")
    
Entering 'A' returns 'Ghi' and entering '_J' returns 'Jkl'.

     --  When passing selection sets between AutoLISP and ADS/ARX 
applications, the following should be observed: 

    If a selection set is created in AutoLISP and stored in an AutoLISP
    variable, then overwritten by a value returned from an ADS or ARX 
    application, the original selection set is eligible for garbage 
    collection (i.e. it will be freed at the next automatic or explicit
    garbage collection).

    WARNING: This is true even if the value returned from the ADS/ARX 
             application was the original selection set.  For example:

         (setq var1 (ssget))
         (setq var1 (adsfunc var1))

    if the "adsfunc" ADS function returns the same selection set it was
    fed as an argument,  then this selection set will be eligible for
    garbage collection EVEN THOUGH IT IS STILL ASSIGNED TO THE SAME
    VARIABLE!

    If you want the original selection set to be protected from garbage
    collection, then you must NOT assign the ads_name (selection set)
    return value of the ADS/ARX application to the AutoLISP variable
    that already references the selection set.  Changing the example
    above to:

         (setq var1 (ssget))
         (setq var2 (adsfunc var1))

    prevents the selection set referenced by var1 from being eligible
    for garbage collection. 



========================================================================== 
ADDITIONAL INFORMATION
====================== 
This section provides additional information on the following topics:

  - Platform Independent Issues
  - AutoCAD SQL Interface (ASI) Issues
  - Documentation Issues
 

Platform Independent Issues
---------------------------
     --  An updated DXFIX application will be available soon.  DXFIX 
converts R13 DXF files into R12 DXF files.  The updated DXFIX application 
will be posted to the general forums of CompuServe, Global Village, and 
Internet.  It will also be available from your Authorized AutoCAD 
Reseller.

     --  The ASE application (the ASE.ARX file) MUST first be loaded 
before you use the OPEN, INSERT, XREF or DXFIN commands with any files 
containing ASE link information if you want that data to be recognized. 
This rule also applies to the DXFOUT command if you want links preserved 
in the exported DXF file.

To load the ASE application you should do one of the following:

    - Enter any ASE command, which automatically loads the application.
    - Use the AutoLISP arxload function, for example, by entering 
      '(arxload "ase")' at the command line.
    - Adding the line "ASE.ARX" to the ACAD.RX file automatically loads 
      the ASE application when AutoCAD starts. See the documentation on 
      the ACAD.RX file for further details on its use.

     --  Release 13 does not currently perform automatic purging of 
unreferenced anonymous blocks.  Therefore you should periodically use the
PURGE command to reduce the number of unreferenced anonymous blocks in a 
drawing.  Anonymous blocks are used for hatch patterns and dimensions.
Each time you grip edit an associative hatch pattern, AutoCAD generates a 
new anonymous block. Depending on your drafting style you can end up with
a large number of unreferenced anonymous blocks, which needlessly 
increases the drawing file size.

     --  The menu file syntax has been modified for R13 AutoCAD for 
Windows to provide additional functionality.  These menu files are not 
recognized by R13 DOS AutoCAD.  If you save a drawing in Windows and then 
open it in a DOS version, the menu may not appear as desired.  Use the 
MENU command to load the DOS menu file.  AutoCAD for Windows recognizes 
both the old and the new syntax.

     --  The Object Pager (OPG) is a new component of Release 13 C2, 
which allows you to limit the amount of virtual memory that AutoCAD uses 
to store the drawing currently being edited.  When you enable the object 
pager, AutoCAD keeps part of the current drawing in virtual memory and 
part of it in the object pager's swap files.  The object pager shuttles 
the data back and forth between virtual memory and the pager files, so 
that it always has what it needs in virtual memory.

If you are editing large drawings that are causing heavy disk swapping
or are causing the system to crash or otherwise act in an unstable way, 
then you might benefit from enabling the object pager.  This will reduce 
the strain on the system's swapping mechanism and should stabilize and 
perhaps speed up AutoCAD R13.

The object pager is controlled by the MAXOBJMEM variable.  This variable 
specifies approximately how much virtual memory AutoCAD will allow the 
drawing to take up before it starts paging the drawing out to disk.  For 
example, if MAXOBJMEM is set to 1000000 (one million), then AutoCAD will 
limit the current drawing's virtual memory use to 1,000,000 bytes.

You can set the MAXOBJMEM variable by entering MAXOBJMEM on the command 
line.  You can also set the environment variable ACADMAXOBJMEM.  Note 
that environment variables can be specified in the acadenv.ini file as 
well as in the actual environment.  See your Installation Guide for 
information on setting environment variables.

The default value of MAXOBJMEM is 0, which disables the object pager.
When MAXOBJMEM is set to a negative value, 0 or to 2,147,483,647, the 
object pager is disabled.  When MAXOBJMEM is set to any other value, the 
object pager is enabled and that value is used as the upper limit for how 
much virtual memory the pager will use.  We recommend setting MAXOBJMEM 
to the approximate size of your system's physical memory. For example, if 
your system has 24MB of RAM, you could set MAXOBJMEM to 24000000.

The object pager creates two temporary swap files.  These swap files use
a naming scheme of MPGR<nnnn>, where the <nnnn> varies per session. These 
files are created when you begin a drawing and are destroyed when you 
exit.  By default, they are created in the directory pointed to by the 
ACADPAGEDIR environment variable.  If that variable is undefined, they are 
created in the AutoCAD temp directory.  If you reboot the system without 
exiting AutoCAD, these files won't be properly deleted, so you should 
delete them yourself.  Do not attempt to delete them from within AutoCAD!

The object pager is separate from the other pager used by AutoCAD.  The 
other pager uses different swap files (PG*) and other variables 
(ACADMAXMEM and ACADMAXPAGE) to control its memory usage.  The one thing 
both pagers have in common is that they both use ACADPAGEDIR to decide 
where to place their swap files.

If ACADPAGEDIR is set to an invalid directory, AutoCAD disables the object 
pager and displays a warning message.  You should change ACADPAGEDIR to 
point to a writeable directory. 

If you change MAXOBJMEM, the pager will not turn on (or off) until you 
exit the current drawing and enter another.  Once the pager is turned on 
(or off), it remains in that condition for the duration of that drawing 
session (until the next NEW or OPEN).  However, if the pager is on, then 
changes to the value of MAXOBJMEM (to raise or lower the size of the 
virtual memory used) are noticed immediately. 

     --  As a side effect of the SPLINEDIT Move vertex option, the fit 
points which define the spline, if any, are purged.


AutoCAD SQL Interface (ASI) Issues
---------------------------------- 

DOS Issues
========== 
This version of AutoCAD includes an ASI Oracle 6.0 driver.  Details about 
this driver can be found in the new README.ASE file.  The ASI.INI file 
must be updated for ASE and other ASI applications to recognize the 
driver.  The following changes should be made to the ASI.INI file.

To the [ENVIRONMENTS.Dos] section add the following line:

    ORACLE60 =

To the [ASI DRIVERS] section add the following line:

    ORADRV = Oracle 6.0 ASI SQL driver

Below the [ASI DRIVERS] section, add the following entry which lists the 
logical name and path for the driver:

    [ORADRV]
    Path = asiora

You must also add an Environment description which uses the driver. This 
can be added in the same area of the file as other Environment 
descriptions.  Here is an example which will need to be modified based 
upon your system/network configuration:

    [ORACLE60]
    Driver = ORADRV
    BASE = T:server:ora
 
To the [ASE_CATALOGS] section addthe following line:

    ORACLE60 = ora

Make sure to see further information about the driver described in the 
new README.ASE file.

Windows NT Issues
================= 
This version of AutoCAD includes an ASI Microsoft SQL Server 4.2 driver 
for Windows NT.  Details about this driver can be found in the new
READASE.WRI file.  The ASI.INI file must be updated for ASE and other ASI 
applications to recognize the driver.  The following changes should be 
made to the ASI.INI file:

To the [ENVIRONMENTS.WinNT] section add the following line:

    SQLSRV =

To the [ASI DRIVERS] section add the following line:

    SSRVDRV = Microsoft SQL Server 4.20 ASI SQL driver

Below the [ASI DRIVERS] section, add the following entry which lists the 
logical name and path for the driver:

    [SSRVDRV]
    Path = asissrv
 
You must also add an Environment description which uses the driver. This 
can be added in the same area of the file as other Environment 
descriptions.  Here is an example which will need to be modified based 
upon your system/network configuration:

    [SQLSRV]
    Driver = SSRVDRV
    Server = SQLSERVER
    AutoCommit = OFF
    Language =
    Timeout = 15
 
To the [ASE_CATALOGS] section add the following line:

    SQLSRV = ""pubs""

Make sure to see further information about the driver described in the 
new READASE.WRI file.


Documentation Issues
--------------------
The following sections provide updates to the AutoCAD documentation set.

     --  Following the R13c2a release, Autodesk will be posting several 
electronic documents (in the form of WinHelp files) to the general forums 
of CompuServe, Global Village, and Internet.  These documents will serve 
to update and augment the current documentation set.


============================================ 
Updates to the Windows/NT Installation Guide 
============================================ 
The following sections contain information that updates the AutoCAD 
Windows/NT Installation Guide.

     --  The R13c2a Historical patch (available only on CD), provides the 
Windows/NT Installation Guide as an on-line electronic document (EDOC)
using the DynaText Viewer.  Just use this new CD instead of the one that 
came with AutoCAD when viewing EDOCs.
     
     --  If you are installing the R13c2a Incremental patch and want to 
run AutoCAD for Windows NT, you will need to get the Windows NT 
Installation Guide Supplement from your Authorized AutoCAD Reseller.
     
     --  In addition to testing on Windows NT 3.50, automated 
compatibility tests were run using a pre-release version of NT 3.51 
(Build 944). No problems were encountered, but compatibility with 
NT 3.51 has not been thoroughly tested.

     --  This release of AutoCAD R13 for NT is not NTFS aware.  AutoCAD 
files stored on an NTFS volume must use FAT 8.3 compatible file names.

     --  You cannot access files stored on an NTFS volume when booted in 
DOS.  Do not install or move common files from FAT volumes onto NTFS 
volumes.  Be especially aware that converting a FAT volume to NTFS will 
make all files on that volume inaccessible when booted in DOS.

     --  Initiating "Learning AutoCAD" from the Help menu generates the 
following "Winhelp mode error" message:

        Executing winhelp.exe rather than winhlp32.exe because 
        this help file uses a 16 bit DLL.

Select the OK button to continue with the tutorial, this is expected 
behavior.

     --  The AutoCAD R13c2a update provides Network License Server 
functionality for the NT platform.  The NT platform also provides multi 
session functionality with the C2 update.  NT users should be aware that 
all of the License server drivers have been updated by the C2 patch.  If 
you are adding NT clients to an existing network installation of AutoCAD, 
then your existing Novell and DOS TSR license servers should be upgraded 
to the C2 versions of the following files:
     
        NSRVNI.NLM  --  Novell file server license server driver.
        NSRVDI.EXE  --  DOS license server driver for IPX protocol.
        NSRVDN.EXE  --  DOS license server driver for NetBIOS protocol.


The AutoCAD R13 Network License Management System - Network Issues
================================================================== 
This section provides up-to-date information that was not included
in the printed documentation.

Installing R13 AutoCAD for network operation now requires the installation
and use of the AutoCAD network license management system by Rainbow
Technologies.  The following sections will discuss the network issues as
it pertains to the individual platforms.

General
-------
    Running the network version of AutoCAD for each workstation client 
requires a license from the AutoCAD license server.  A license server must 
be installed on the network before any requests from client AutoCADs can 
be made.  When a license request is made, AutoCAD must wait for the 
license server to grant this before it can complete its startup.  AutoCAD 
will display its logo screen while the license request is being processed.  
If the network is very large or extremely busy, the license granting 
process can take several minutes to complete.

One way to minimize installation problems is to plug the network hardware
lock on a client workstation.  Install AutoCAD and run it from that 
workstation.  This would allow you to test whether AutoCAD and its 
requisite files and subdirectories have been properly installed/created on 
the file server without the worry of possible license server problems due 
to network issues.  Once you know AutoCAD is running properly, you can 
return the hardware lock to its intended place (typically at the file 
server) and check the license server for proper operation.

As mentioned previously, requests to the license server can take some time
to respond on networks.  This is compounded with the use of a long 
department name list.  Each department name will be queried for a license 
in turn until one is found that can grant a license.  Be sure to order 
your list from left to right with the left being most likely to grant a 
license to the least likely.  If you have a list as follows:

    SET ACADSERVER=server1;server2;server3;

The department name server1 will be queried first, then server2, then 
server3.  Currently, each license server can only have one department name 
assigned to it and a maximum of 10 license servers can use the same 
department name.  You can have more than one network hardware lock for 
each license server with the limitation of one lock per parallel port for 
each machine.  You cannot cascade multiple AutoCAD network locks on a 
single parallel port.  The license server will auto scan for these locks 
on the standard parallel ports, LPT1, LPT2, LPT3.  You can also override 
these ports with the /P option as described in the installation guide 
under Security Server Command Line Options.  Multiple license servers are 
allowed on the network but only one license server per machine.  If you 
plan to have more than one network hardware lock to distribute licenses 
from several servers with pre-authorized licenses, be sure to have 
Autodesk authorize these locks for one AutoCAD serial number.  Use only 
that AutoCAD on the network.  This also holds true for field authorizing 
multiple network locks.  AutoCAD will only run with its authorized network 
lock, providing the lock has been authorized for more than the default 2 
licenses.

If you plan to use the NetBIOS/NETBEUI network protocol as the base 
protocol for the network license server, be sure that the Lana number on 
both your server and client machines are matched and set to zero.  The 
NetBIOS license server will only communicate on Lana0.  Network systems 
that support multiple network protocols, such as Windows for Workgroups, 
must have their NetBIOS/NETBEUI protocol assigned to Lana0.

The latest set of AutoCAD license servers can support license issuance 
from AutoCAD clients on any of the DOS, Windows, and NT platforms.  This 
provides the widest support across multiple platforms.


NT v3.5 Network Issues
----------------------
    The NT SAP Agent must be installed and started on workstations 
exchanging AutoCAD licenses via the IPX protocol.  Both NT license 
servers running NSRVGX.EXE and NT client workstations require the SAP 
agent to operate on the IPX protocol. Before installing this service, be 
sure to have available the NT3.5 installation diskettes/CD-ROM.  The 
required file, as is the service, is not part of the standard NT install. 
You must install this yourself. To install the service, follow these 
steps:

    1. Go to the Control Panel and run the Network applet
    2. The Network Settings dialog box displays, choose Add Software.
    3. Select the SAP AGENT item from the software list.
    4. Enter the path to where it can locate the SAP AGENT file,
       NWSAP.DLL

Restart NT if it requests that you do so.  To verify that the SAP AGENT
has been installed and started properly, run the Services applet in the
Control Panel and scan the list for SAP AGENT.  It should show that it
has been started.

If you are a NT client serviced by a NetBIOS/Netbeui license server or an 
NT license server supporting NetBIOS license clients, be sure the NetBios 
protocol support is configured and assigned to Lana0.  To check this, 
follow these steps:

    1. Go to the Control Panel and run the Network applet.
    2. The Network Settings dialog box displays.  
    3. Double click on the Netbios Interface item in the list to see 
       the Lana assignments.
    4. Check the Lana list to be sure of the following:
          0: Nbf->...
       If not, then reassign the numbers to comply.
    5. Exit the applet.

Restart NT if it requests that you do so.  If you are still having 
problems with acquiring a license from the NetBIOS license server, try 
changing Step 4. to select:

          0: NwlnkNB->...

The NT license server is a multi-protocol server.  This means it is
capable of granting licenses to either IPX or NetBios AutoCAD clients.
You may have to install one or the other protocol if you haven't done so 
already at install time.  You can limit which protocol you want the 
license server to support by using the following command line option
switch for NSRVGX:

  /SN:0  - Defines no NetBIOS/NETBEUI support.
  /SW:0  - Defines no NWLINK(IPX/SPX) support.

This might be useful in testing your network protocol support.

If the NT license server is installed, a status screen is available to
show the current status of the licenses it is managing.  The screen
information is updated automatically every 4 seconds. The NT license 
server will not warn you of in-use licenses if you exit the license 
server or NT.  No warning broadcast is sent to the existing AutoCAD 
clients when the license server is being shut down.  If the license 
server is shut down while AutoCAD clients are still running, an error 
message will display indicating that there is a network license problem.  
This will force you to abort AutoCAD with the option to save your current 
work.

To use the department name feature for license management under NT, for
a NT license server, specify the department name with the command line
option /dn:deptname when you start the server, as you would with any
other server.  For a NT client, you need to set the environment variable 
ACADSERVER with the department names to use.  This is done through the 
System applet in the Control Panel.  Once it is set, you can run the 
AutoCAD client immediately without restarting NT.


Windows for Workgroups Issues
-----------------------------
    When the default network configuration for Windows for Workgroups 
(WFW) is installed, it uses the Microsoft Netbeui network protocol as its 
network communications protocol.  To properly communicate with a NetBios 
license server, the Netbeui protocol must be set Lana number 0, by editing 
the PROTOCOL.INI file in the Windows subdirectory.  Determine if the 
following line is there:

    lana0=ms$ne2clone,1,ms$netbeui

Be sure that lana0 and ms$netbeui are on the same line.  The ms$ne2clone
will define the LAN adapter card you are using.  In this case, it is a
Novell 2000 clone card.

IPX network protocol support, such as a Novell client, is transparent.
No special instructions are needed if your WFW is running as a Novell
client, providing you have a IPX license server operational.

To set up a department name for WFW, you need to set the ACADSERVER 
environment variable before you start WFW.  Unfortunately, this does not 
provide you with a dynamic way of selecting a different department name 
without exiting WFW.


========================================== 
Updates to the AutoCAD Customization Guide
========================================== 
The following sections contain information that updates the AutoCAD 
Customization Guide.

PART II - CHAPTER 16 
==================== 
The group code tables presented here are intended to update those in the 
Customization Guide. Ellipsis (...) in the "group codes" column indicate 
that the remaining codes in the original documentation are correct, and 
ellipsis in the "description" column indicate that the description in the 
original documentation is correct.

Graphical Entities
================== 

Common Group Codes
------------------
Group codes that can apply to all graphical entities
----------------------------------------------------
Group                                                   If omitted
codes   Description                                     defaults to 
------- ----------------------------------------------  -------------
-1       ...
0        ...
5        ...
100     Subclass marker (AcDbEntity)                    Not omitted
67       ...
8        ...
62       ...
6        ...
48       ...

Group Codes by Entity Type
--------------------------
For information on group codes of entities, refer to "PART III - 
Chapter 13, ENTITIES Section" in the "Updates to the AutoCAD Developer's 
Guide" below.

Dimension Style Overrides
-------------------------
The example return value should be as follows:
  (-3 ("ACAD" (1000 . "DSTYLE")
    (1002 . "{")(1070 . 177)(1070 . 3) 
    (1070 . 71)(1070 . 1)(1002 . "}")
  )) 


Nongraphical Entities
===================== 
The section "Common Group Codes" does not apply to dictionary objects, it 
should be moved to the section "Block and Symbol Table Group Codes."

Dictionary Group Codes
----------------------
For information on group codes of dictionaries, refer to "PART III - 
Chapter 13, OBJECTS Section" in the "Updates to the AutoCAD Developer's 
Guide" below.

Block and Symbol Table Group Codes
----------------------------------
For information on group codes of blocks and symbol tables, refer to 
"PART III - Chapter 13, ENTITIES Section" in the "Updates to the AutoCAD 
Developer's Guide" below.


======================================== 
Updates to the AutoCAD Developer's Guide
======================================== 
The following sections contain information that updates the AutoCAD 
Developer's Guide. 

PART I - ADS
============ 
Sending commands to NT/Win AutoCAD
----------------------------------
You can send command strings directly to AutoCAD from an ADS (or other) 
application.  This is done by sending a WM_COPYDATA message to AutoCAD's 
main frame window.  This is similar to but not exactly the same as the 
WM_ACAD method used with R12 AutoCAD for Windows. 

The first thing you need to do is get the window handle of the main 
frame window.  This handle is passed in to ADS apps in the variable 
adsw_hwndAcad.  It can also be found using the EnumWindows call.  For 
each window, call GetWindowText() and see if the initial text matches 
"AutoCAD -".

Next, you need to construct a WM_COPYDATA message to send to this window.  
Please see the Win32 documentation on WM_COPYDATA and the COPYDATASTRUCT.  
Your COPYDATASTRUCT should have 1 in the dwData field, string length 
(including null) in the cbData field, and pointer to the string in the 
lpData field.  Then send the address of the structure as the LPARAM of 
the WM_COPYDATA message.  AutoCAD will return a 1 if it processes the 
message and a 0 otherwise.  It will not process the message if a 1 is not 
in the dwData field, or if the string does not appear to be 
null-terminated.


PART III - CHAPTER 13
===================== 
The group code tables presented here are intended to update those in the 
Developer's Guide. Ellipsis (...) in the "group codes" column indicate
that the remaining codes in the original documentation are correct, and 
ellipsis in the "description" column indicate that the description in the
original documentation is correct.

New for AutoCAD Release 13 
========================== 
The new DXF file sections are CLASSES and OBJECTS. A new table, 
BLOCK_RECORD, has been added to the TABLES section. 

Delete information about group code 90 (ADE object lock) from the "New 
group codes" table.

DXF File Structure
------------------
Add BLOCK_RECORD to the list of symbol tables.

Group Code Description by Number
--------------------------------
Delete information about group code 90 (ADE object lock) from the "AutoCAD
group codes (by number)" table.

Delete information about group code 90 (ADE object lock) from the "Overall
object (or entity) structure" table.

TABLES Section
============== 
Add "BLOCK_RECORD" to the list of valid table names in the second 
paragraph.

Add "a group 100 (AcDbSymbolTable subclass marker)" to the list of lines 
in the table header following group 5 and before group 70.

APPID group codes
-----------------
Group codes     Description
--------------  ---------------------------------------------------------
5               Handle
100             Subclass marker (AcDbSymbolTableRecord) 
100             Subclass marker (AcDbRegAppTableRecord) 
2               User-supplied application name; these table entries 
                maintain a set of names for all registered applications
70              Standard flag values

BLOCK_RECORD group codes 
------------------------ 
Group codes     Description  
--------------  ---------------------------------------------------------  
5               Handle  
100             Subclass marker (AcDbSymbolTableRecord)  
100             Subclass marker (AcDbBlockTableRecord)  
2               Block name
 
DIMSTYLE group codes
--------------------
group codes     description
--------------	---------------------------------------------------------
105             Handle
100             Subclass marker (AcDbSymbolTableRecord) 
100             Subclass marker (AcDbDimStyleTableRecord) 
2               Dimension style name
 ...
274             DIMALTTD
340             Handle of referenced STYLE object (used instead of storing 
                DIMTXSTY value)
275             DIMAUNIT
280             DIMJUST
281             DIMSD1
282             DIMSD2
 ...

LAYER group codes
-----------------
group codes     description 
--------------  --------------------------------------------------------- 
5               Handle
100             Subclass marker (AcDbSymbolTableRecord)  
100             Subclass marker (AcDbLayerTableRecord)  
2               Layer name
 ...

LTYPE group codes
-----------------
Group codes     Description  
--------------  --------------------------------------------------------- 
5               Handle 
100             Subclass marker (AcDbSymbolTableRecord)   
100             Subclass marker (AcDbLinetypeTableRecord)   
2               Linetype name
 ...
73              Number of linetype elements
40              Total pattern length. 
49              Dash, dot or space length (one entry per element). 
74              Complex linetype element type (one per element)
                0 = not complex
                2 = embedded text string
                4 = embedded shape
75              Complex shape code (one per element if code 74 > 0)
                1 if code 74=2
                <shape_number> if code 74=4
340             Pointer to STYLE object (one per element if code 74 > 0)
46              S= scale value (one per element if code 74 > 0) 
50              R= rotation value  (one per element if code 74 > 0)
44              X= x-offset value (one per element if code 74 > 0)
45              Y= y-offset value (one per element if code 74 > 0)
9               Text string (one per element if code 74 = 2)

STYLE group codes
-----------------
Group codes     Description   
--------------  --------------------------------------------------------- 
5               Handle 
100             Subclass marker (AcDbSymbolTableRecord)   
100             Subclass marker (AcDbTextStyleTableRecord)   
2               Style name 
 ...

UCS group codes
---------------
Group codes     Description    
--------------  ---------------------------------------------------------    
5               Handle  
100             Subclass marker (AcDbSymbolTableRecord)    
100             Subclass marker (AcDbUCSTableRecord)    
2               UCS name  
 ... 

VIEW group codes
----------------
Group codes     Description   
--------------  ---------------------------------------------------------
5               Handle 
100             Subclass marker (AcDbSymbolTableRecord)
100             Subclass marker (AcDbViewTableRecord)
2               View name 
 ...

VPORT group codes
-----------------
Group codes     Description
--------------  ---------------------------------------------------------
5               Handle
100             Subclass marker (AcDbSymbolTableRecord)
100             Subclass marker (AcDbViewportTableRecord)
2               Viewport name 
 ...


BLOCKS Section
============== 

BLOCKS group codes
------------------
Group codes     Description
--------------  ---------------------------------------------------------
5               Handle
100             Subclass marker (AcDbEntity)
8               Layer name
100             Subclass marker (AcDbBlockBegin)
2               Block name
70               ...
10, 20, 30       ...
3               Block name
1               Xref path name

ENDBLK group codes
------------------
Group codes     Description 
--------------  --------------------------------------------------------- 
5               Handle 
100             Subclass marker (AcDbEntity)
8               Layer name
100             Subclass marker (AcDbBlockEnd)


ENTITIES Section
================ 

Group codes common to all entities
----------------------------------
Group codes     Description  
--------------  ---------------------------------------------------------  
0               Entity type
5               Handle
100             Subclass marker (AcDbEntity)
67              Absent or 0 indicates that the entity is in model space. 
                One indicates that the entity is in paper space. Other 
                values are reserved.  (optional)
8               Layer name
6               Linetype name (if not BYLAYER). The special name BYBLOCK 
                indicates a floating linetype.  (optional)
62              Color number (if not BYLAYER). Zero indicates the BYBLOCK 
                (floating) color. 256 indicates the BYLAYER color.
                (optional)
48              Linetype scale  (optional)
60              Object visibility (optional)
                0=visible, 1=invisible 

3DFACE group codes
------------------
Group codes     Description  
--------------  ---------------------------------------------------------  
100             Subclass marker (AcDbFace) 
 ...

3DSOLID group codes 
------------------- 
Group codes     Description   
--------------  ---------------------------------------------------------   
100             Subclass marker (AcDbModelerGeometry)
70              
 ...

ARC group codes  
---------------  
Group codes     Description    
--------------  ---------------------------------------------------------    
100             Subclass marker (AcDbCircle)
10, 20, 30       ...
40               ...
100             Subclass marker (AcDbArc)
 ...

ATTDEF group codes   
------------------   
Group codes     Description     
--------------  ---------------------------------------------------------     
100             Subclass marker (AcDbText)
10, 20, 30       ... 
40               ... 
1                ...
100             Subclass marker (AcDbAttributeDefinition)
 ...   

ATTRIB group codes    
------------------   
Group codes     Description      
--------------  ---------------------------------------------------------      
100             Subclass marker (AcDbText)
10, 20, 30       ...  
40               ...  
1                ...
100             Subclass marker (AcDbAttribute)
 ...

BODY group codes  
----------------  
Group codes     Description    
--------------  ---------------------------------------------------------    
100             Subclass marker (AcDbModelerGeometry)
70              
 ...

CIRCLE group codes   
------------------   
Group codes     Description     
--------------  ---------------------------------------------------------     
100             Subclass marker (AcDbCircle)
 ...

DIMENSION group codes common to all dimension types    
--------------------------------------------------- 
Group codes     Description      
--------------  ---------------------------------------------------------      
100             Subclass marker (AcDbDimension) 
2                ...
10, 20, 30       ...
11, 21, 31       ...
70               ...
1                ...
53               ...
51               ...
210,220,230      ...
3                ...


Group codes for aligned, linear, and rotated dimensions
-------------------------------------------------------
Group codes     Description
--------------  ---------------------------------------------------------
100             Subclass marker (AcDbAlignedDimension)
12, 22, 32       ...
13, 23, 33       ...
14, 24, 34       ...

Group codes for linear, and rotated dimensions 
---------------------------------------------- 
Group codes     Description 
--------------  --------------------------------------------------------- 
100	        Subclass marker (AcDbRotatedDimension) 
50               ...
52               ...


Group codes for radial and diameter dimensions 
---------------------------------------------- 
Group codes     Description 
--------------  --------------------------------------------------------- 
100             Subclass marker (AcDbRadialDimension or 
                AcDbDiametricDimension)
15, 25, 35       ...
40               ...

Group codes for angular dimensions  
----------------------------------  
Group codes     Description  
--------------  --------------------------------------------------------- 
100             Subclass marker (AcDb3PointAngularDimension)
13, 23, 33       ...
14, 24, 34       ...
15, 25, 35       ...
16, 26, 36       ...

Group codes for ordinate dimensions   
-----------------------------------   
Group codes     Description   
--------------  ---------------------------------------------------------  
100             Subclass marker (AcDbOrdinateDimension)
13, 23, 33       ...
14, 24, 34       ...


ELLIPSE group codes
-------------------
Group codes     Description
--------------  ---------------------------------------------------------
100             Subclass marker (AcDbEllipse)
10, 20, 30       ...
11, 21, 31       ...
210, 220, 230   Extrusion direction
40              Ratio of minor axis length to major axis length
41               ...
42               ...

INSERT group codes
------------------
Group codes     Description 
--------------  --------------------------------------------------------- 
100             Subclass marker (AcDbBlockReference)
 ...
210, 220, 230   Extrusion direction

LEADER group codes 
------------------ 
Group codes     Description  
--------------  ---------------------------------------------------------  
100             Subclass marker (AcDbLeader)
  3             Dimension style name
 71             Arrowhead flag
                0=disabled
                1=enabled
 72             Leader path type
                0=Straight line segments
                1=Spline
 73             Leader creation flag (default = 3)
                0=leader created with text annotation
                1=created with Tolerance annotation
                2=created with Block Ref annotation
                3=created without any annotation
 74             Hookline direction flag
                0=hookline (or end of tangent for a splined leader)
                  is the opposite direction from the horizontal vector
                1=hookline (or end of tangent for a splined leader)
                  is the same direction as horizontal vector (see below)
 75             Hookline flag 
                0=no hookline 
                1=has a hookline
 40             Text annotation height
 41     	Text annotation width
 76		Number of vertices in leader (ignored for DXFIN)
 10, 20, 30	Vertex coordinates (one entry for each vertex)
 77		Color to use if leader's DIMCLRD=BYBLOCK
340		Hard reference to associated mtext entity 
		(Currently not used)
210,220,230	Normal vector
211,221,231	"Horizontal" direction for leader
212,222,232	Direction of annotation offset from last leader vertex
                (Currently not used)

LINE group codes  
----------------  
Group codes     Description   
--------------  ---------------------------------------------------------   
100             Subclass marker (AcDbLine)
 ...

MLINE group codes   
-----------------
Group codes     Description    
--------------  ---------------------------------------------------------    
100             Subclass marker (AcDbMline)
  2		String of up to 32 characters. The name of the style used 
  		for this mline. An entry for this style must exist in the 
		MLINESTYLE dictionary.
340		Pointer handle/ID of MLINESTYLE dictionary
 40		Scale factor
 70		Justification: 0=top, 1=zero, 2=bottom 
 71		Open/closed flag: 1=open, 3=closed
 72		Number of vertices
 73		Number of elements in MLINESTYLE definition 
 10,20,30	Mline start point
210,220,230	Extrusion direction; present only if the entity's 
		extrusion direction is not parallel to the WCS Z axis 
		(optional; default = 0, 0, 1)
 -----------    The remaining codes repeat (as a group) for each vertex
 11,21,31	Vertex coordinates (one entry for each vertex)
 12,22,32	Direction vector of segment starting at this vertex  
		(one entry for each vertex)
 13,23,33	Direction vector of miter at this vertex  
		(one entry for each vertex)
 -----------    The remaining codes repeat (as a group) for each element
                in this segment
 74		Number of parameters for this element 
		(one entry for each element in segment)
 41		Element parameters (repeats based on previous code 74)
 75		Number of area fill parameters for this element 
		(one entry for each element in segment)
 42             Area fill parameters (repeats based on previous code 75)

Note: The group code 2 in mline objects should only be used to retrieve
      the current mlinestyle name. To change the mlinestyle associated
      with an mline, modify the group code 340 to point to the new 
      mlinestyle object.

OLEFRAME group codes
--------------------
Group codes     Description     
--------------  ---------------------------------------------------------     
100             Subclass marker (AcDbOleFrame) 
 70		
 90		
310		Binary data (multiple lines)
  1		End of Ole data (the string "OLE")

POINT group codes
-----------------  
Group codes     Description      
--------------  ---------------------------------------------------------      
100             Subclass marker (AcDbPoint) 
 ...

POLYLINE group codes      
--------------------    
Group codes     Description       
--------------  ---------------------------------------------------------       
100             Subclass marker (AcDb2dPolyline) 
 ...

RAY group codes      
---------------    
Group codes     Description       
--------------  ---------------------------------------------------------       
100             Subclass marker (AcDbRay) 
 ...

REGION group codes      
------------------    
Group codes     Description        
--------------  ---------------------------------------------------------        
100             Subclass marker (AcDbModelerGeometry) 
 70		
 ...

SHAPE group codes       
-----------------     
Group codes     Description         
--------------  ---------------------------------------------------------
100             Subclass marker (AcDbShape) 
 ...

SOLID group codes
-----------------
Group codes     Description
--------------  ---------------------------------------------------------
100             Subclass marker (AcDbTrace) 
 ... 

SPLINE group codes
------------------
Group codes     Description
--------------  ---------------------------------------------------------
100             Subclass marker (AcDbSpline) 
210,220,230	 ...
 70		Spline flag (bit coded)
		1 = Closed spline
		2 = Periodic spline
		4 = Rational spline
		8 = Planar
		16 = Linear; planar bit is also set
 71		Degree of the spline curve
 ... 
 42		Fit tolerance (default = 0.0000001) 
 43		Control-point tolerance (default = 0.0000001) 
 44		Fit tolerance (if a fit spline) 
 ...

TEXT group codes
----------------
Group codes     Description
--------------  ---------------------------------------------------------
100             Subclass marker (AcDbText) 
 ... 

TOLERANCE group codes 
--------------------- 
Group codes     Description 
--------------  --------------------------------------------------------- 
100             Subclass marker (AcDbFcf) 
  3		 ...
 10,20,30	 ...
  1		 ...
210,220,230	Extrusion direction
 11,21,31	 ...

TRACE group codes 
----------------- 
Group codes     Description 
--------------  --------------------------------------------------------- 
100             Subclass marker (AcDbTrace) 
 ...  

VERTEX group codes  
------------------  
Group codes     Description  
--------------  ---------------------------------------------------------  
100             Subclass marker (AcDbVertex) 
100             Subclass marker (AcDb2dVertex or AcDb3dPolylineVertex) 
 ...

VIEWPORT group codes  
--------------------  
Group codes     Description  
--------------  ---------------------------------------------------------  
100             Subclass marker (AcDbViewport) 
 ... 

XLINE group codes   
-----------------   
Group codes     Description   
--------------  ---------------------------------------------------------   
100             Subclass marker (AcDbXline) 
 10,20,30	 ...
 11,21,31	Unit direction vector (in WCS)


OBJECTS Section
=============== 

Common object group codes table
-------------------------------
Group codes     Description
--------------  ---------------------------------------------------------
  5		Handle
102		Start of persistent reactors group, always 
		"{ACAD_REACTORS" (persistent reactors group appears in 
		all dictionaries except the main dictionary)
330		Soft pointer ID/handle to owner dictionary
102		End of persistent reactors group, always "}" 

DICTIONARY group codes
----------------------
Group codes     Description
--------------  ---------------------------------------------------------
100             Subclass marker (AcDbDictionary)
  3		Entry name (one for each entry) 
350		Handle of entry object (one for each entry) 

GROUP group codes 
----------------- 
Group codes     Description 
--------------  --------------------------------------------------------- 
100             Subclass marker (AcDbGroup)
300		Group description 
 70		"Unnamed" flag: 1=unnamed, 0=named
 71		Selectability flag: 1=selectable, 0=not selectable 
340		Handle of entity in group (one entry per object)

MLINESTYLE group codes  
----------------------  
Group codes     Description  
--------------  ---------------------------------------------------------  
100             Subclass marker (AcDbMlineStyle)
  2		Mline style name
 70		Flags (bit coded)
		1 = fill on
		2 = display miters
		16 = Start square end (line) cap
		32 = Start inner arcs cap
		64 = Start round (outer arcs) cap
		256 = End square (line) cap
		512 = End inner arcs
		1024 = End round (outer arcs) cap
  3		Style description (string, 255 characters max)
 62		Fill color (integer, default = 0). Multiple entries can 
 		exist; one entry for each element.
 51		Start angle (real, default is 90 degrees)
 52		End angle (real, default is 90 degrees)
 71		Number of elements
 49		Element offset (real, no default). Multiple entries can 
 		exist; one entry for each element
 62		Element color (integer, default=256). Multiple entries 
		can exist; one entry for each element
  6		Element linetype (string, default=BYLAYER). Multiple 
		entries can exist; one entry for each element

Note: The group code 2 in mlinestyle objects should only be used to 
      retrieve the mlinestyle name. To change an mlinestyle name, modify
      the group code 3 of the dictionary object that owns the MLINESTYLE
      dictionary.



========================================================================== 
R13c1 Maintenance Release Information - January, 1995
========================================================================== 
CONTENTS
======== 

    What Problems Does it Fix?
        
    Additional Information


========================================================================== 
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.


     
