AutoCAD Release 10
README.DOC for IBM PC/XT/AT and PS/2
October 26, 1988
This file highlights some important changes in AutoCAD Release 10 and includes
last-minute information that missed the deadline for the printed manuals.
TABLE OF CONTENTS
Page
Compatibility with Application Programs - FLATLAND 2
Extended AutoLISP Restrictions 3
AutoShade / AutoFlix Updates 3
AutoCAD AEC Architectural Updates 4
Performance 5
Multiple Viewports and ADI Display Drivers 5
Perspective Views 6
Miscellaneous Changes and Corrections 7
The DOS "SHARE" Utility 9
DOS 4.0 Notes 9
Known Problems 10
TDIBMRD4.3 Page 1 of 10
COMPATIBILITY WITH APPLICATION PROGRAMS - FLATLAND
* Some functions, including entity selection and object snap, have changed
subtly in Release 10 to accommodate 3D, viewports, and perspective views.
These changes have little effect when you're using AutoCAD interactively.
However, programs that generate AutoCAD command sequences may get
unexpected results. Therefore, the FLATLAND system variable is provided to
let you maintain compatibility with programs that have not yet been updated
to recognize and take advantage of Release 10's new capabilities.
When FLATLAND is zero, Release 10's 3D features are fully enabled. When
FLATLAND is nonzero, compatibility with previous versions is maintained.
The initial FLATLAND setting for a drawing is shown in the following table.
Condition | Initial setting
--------------------------------------- | ------------------------
Editing an old drawing (produced by | FLATLAND = 1
AutoCAD Release 9 or earlier) |
|
Editing a drawing created or previously | As saved with the drawing
edited with AutoCAD Release 10 |
|
Creating a new drawing (with "name=") | FLATLAND = 0
|
Creating a new drawing (without "=", | Set by prototype drawing -- in
or with "name=prototype") | the standard ACAD.DWG prototype,
| FLATLAND is zero.
If you're using AutoCAD AEC Architectural or a third-party application that
has not yet been updated to take advantage of Release 10's new features,
you may experience problems with entity selection or object snap if you set
FLATLAND to zero. In such cases, we recommend that you keep FLATLAND set
to 1 (set this in the prototype drawing, if necessary) and use only the
World Coordinate System when editing with AutoCAD Release 10.
NOTE: The FLATLAND system variable is a temporary conversion aid, and will
be removed in the next major update of AutoCAD. If you've written
your own application and it fails to work properly with FLATLAND set
to zero, run with FLATLAND set to 1 if necessary, but UPDATE YOUR
APPLICATION AS SOON AS IS PRACTICAL, because future versions of
AutoCAD will always operate as though FLATLAND was zero.
See the Release 10 Reference Manual (Appendix D) for further details.
* In previous versions, DXF files and the AutoLISP (entget) function supplied
a 38 group containing an entity's elevation. Release 10 continues to
supply this field if FLATLAND is set to 1 and the entity lies in the World
Coordinate System's XY plane. Otherwise, the 38 group is omitted and the
elevation is supplied as the Z coordinate of the object's 3D points.
This poses a small problem for Polylines, since the 38 group was supplied
with the POLYLINE (header) entity, but that entity has no associated point.
Therefore, if FLATLAND is zero or the Polyline doesn't lie in the XY plane
of the WCS, a "dummy" 3D point (10 group) is supplied with the POLYLINE
header entity, with its Z coordinate being the only item of interest.
TDIBMRD4.3 Page 2 of 10
EXTENDED AUTOLISP RESTRICTIONS
* In addition to the regular version of AutoLISP, a new Extended AutoLISP
(EXTLISP) program is supplied with Release 10. Extended AutoLISP utilizes
IBM AT-style Extended memory (available on 80286 and 80386 machines only)
to allow larger AutoLISP programs while freeing up some regular memory.
The initial version of Extended AutoLISP cannot run in certain
environments, including:
* environments that run the 80286 or 80386 in "virtual-8086" mode. This
includes COMPAQ's CEMM and Quarterdeck's QEMM.
* the Intel Inboard.
* certain NEC computers made for the Japanese market.
In these environments, regular AutoLISP must be used instead of Extended
AutoLISP.
An updated version of Extended AutoLISP that runs with most Intel Inboards
and with Quarterdeck's QEMM soon will be made available to all registered
AutoCAD Release 10 users who request it from their dealer. Dealers will
be notified when the new version is available. (In order for Extended
AutoLISP to work with COMPAQ's CEMM, COMPAQ will need to make certain
program changes. Some early Intel Inboards have hardware bugs that will
prevent Extended AutoLISP from ever working with them.)
AUTOSHADE / AUTOFLIX UPDATES
* If you use AutoShade 1.0 in conjunction with AutoCAD, we recommend that you
upgrade to AutoShade version 1.1 (to be released shortly). Very large 3D
meshes created in AutoCAD Release 10 may cause AutoShade 1.0 to abort with
the message "Heapmgmt - heap error. Cheap stack dump".
The problem can occur with drawings created by AutoCAD Release 9, but is
much more likely to occur with Release 10 due to the ease with which large
meshes can be constructed in Release 10.
AutoShade 1.0 can read meshes up to about 73 x 73. To be precise, M x N
must be less than 5420, where M and N are the sizes of the polygon mesh
(usually SURFTAB1 and SURFTAB2). Smaller meshes are handled without
difficulty. To use large meshes with AutoShade 1.0, EXPLODE them (forming
individual 3D Faces) before performing the FILMROLL command. This
limitation is removed in AutoShade 1.1. Registered AutoShade 1.0 users
will be sent a letter explaining how to update to version 1.1 for free.
* An updated version of the ASHADE.LSP file for use with AutoShade is
provided with AutoCAD Release 10. See Appendix A of the AutoLISP
Programmer's Reference for more information. (The AutoLISP manual states
that you must turn perspective viewing off after using ASHADE.LSP's new
CAMVIEW command, but this is no longer necessary.)
* Updated versions of the AutoFlix files AFLIX.LSP, AFWALK.LSP, and
AFKINET.LSP are provided with AutoCAD Release 10. See Appendix A of the
AutoLISP Programmer's Reference for more information.
TDIBMRD4.3 Page 3 of 10
AUTOCAD AEC ARCHITECTURAL UPDATES
* If you're an AutoCAD AEC Architectural 1.5/2.5 customer, we recommend that
you upgrade to the latest version of AEC Architectural (2.01/9.0 as of
this writing).
* If you have AEC Architectural 2.0/9.0 but have not sent in your
registration card, we recommend that you do so. An update (to 2.01/9.0)
has been sent to all registered 2.0/9.0 users.
* AEC Architectural 2.01/9.0 is the proper version to use with AutoCAD
Release 10, but has a problem with Attribute prompts when running with
Release 10; if you insert Blocks with Attributes, you'll get unreadable
Attribute prompts. The problem is due to incorrect usage of the string
"\r" in some of the AEC Architectural .LSP files. A patch program to fix
this (AECPATCH) is provided with AutoCAD Release 10. The patch, which
works only with AEC Architectural version 2.01/9.0, changes the version to
2.02/9.0. This problem will be corrected in a future release of AEC
Architectural, and the patch program will no longer be needed.
To run the AECPATCH program, perform these steps in this order:
1. Install AutoCAD Release 10 as outlined in the Installation and
Performance Guide.
2. Install AEC Architectural 2.01/9.0. If you're already using 2.01/9.0
with AutoCAD Release 9, simply run the RELOAD.BAT procedure as outlined
in Appendix A of the AEC Architectural User Guide, entitled "Installing
AutoCAD a Second Time", to ensure that the correct ACAD.LIN and
ACAD.PAT files are available to AEC Architectural.
AECPATCH uses the ACAD environment variable (SET ACAD=<drive>:\aec\a\d)
to locate the AEC LISP files. If you've placed this SET statement in
your AUTOEXEC.BAT file, reboot DOS to ensure that it has taken effect.
3. If you intend to use AEC Architectural's AUI, install it (if you
weren't already using it with AutoCAD Release 9).
4. If you intend to use AEC Architectural's Schedule Manager, check the
ACAD.PGP file in your AutoCAD directory. If it doesn't contain the
line:
dbSCHED,sched,350000,,4
then edit the ACAD.PGP file and add this line to it.
5. Now you're ready to run the AECPATCH program. The patch program is
supplied on an AutoCAD release disk; the following table indicates the
disk used for each of the AutoCAD release formats.
360KB 5.25" Format - Driver Disk 2 Disk 11 of 11
720KB 3.5" Format - Driver Disk Disk 6 of 6
1.2MB 5.25" Format - Executable/Driver Disk Disk 2 of 4
TDIBMRD4.3 Page 4 of 10
To apply the patch, place the indicated disk in a compatible drive and
type the following at the DOS prompt:
<drive>: (to make the drive containing the patch disk current)
CD \AEC (to make the patch directory current)
AECPATCH (to run the patch program)
NOTE: The message "ACAD environment variable not found. Aborting..."
will appear if you haven't "SET ACAD=<drive>:\aec\a\d". See step 2.
6. If you reinstall AEC Architectural's AUI after running AECPATCH, you'll
need to run AECPATCH (step 5) again.
The AECPATCH program
- copies corrected versions of the files AA23A.LSP, AE081.LSP, and
AH18A.LSP into your \AEC\A\L directory, and
- searches for the 2.01/9.0 ACAD.LSP file in your \AEC\A\D directory,
deletes all occurences of the string "\r" from it, and changes the
version number to 2.02/9.0. (The version number is displayed each time
the ACAD.LSP file is loaded.) Note that AECPATCH does not update the
version number displayed on the AEC screen menu.
PERFORMANCE
* Release 10 makes heavier use of overlays than did previous versions of
AutoCAD. To improve performance (particularly when running scripts, menus,
or AutoLISP programs that draw many new entities), we recommend use of a
RAM disk for AutoCAD's .OVL files. See Chapter 4 of your AutoCAD
Installation and Performance Guide for more information.
MULTIPLE VIEWPORTS AND ADI DISPLAY DRIVERS
* Release 10's new multiple-viewport feature works best with display drivers
that explicitly provide support for it. ADI display drivers written for
older versions of AutoCAD (ADI version 3.1 and earlier) should continue to
work with Release 10, with the following restrictions:
* Drivers that use display-list techniques will get very confused by
multiple viewports. Don't use multiple viewports with such drivers.
* Non-display-list drivers may clear viewports very slowly.
Release 10's ADI 4.0 has new features that allow drivers to clear viewports
quickly, and to make effective use of display-list techniques in
conjunction with multiple viewports. If you use an ADI display driver and
expect to use multiple viewports, contact the manufacturer of your driver
to see if an ADI 4.0 version of the driver is available.
TDIBMRD4.3 Page 5 of 10
PERSPECTIVE VIEWS
* During development of AutoCAD Release 10, we found it necessary to disable
many commands while a perspective view was active. The AutoCAD Tutorial
(page 67) reflects this, and the Release 10 Reference Manual (page 187)
states that the following prompt is issued if you attempt to use these
commands in a perspective view.
About to regen with perspective off -- proceed? <Y>
Most of the command restrictions have now been lifted. The only commands
now disallowed in perspective views are ZOOM, PAN, SKETCH, and transparent
'ZOOM and 'PAN. If you enter any of these commands from a viewport
containing a perspective projection, AutoCAD now displays the message:
This command may not be invoked in a perspective view.
and cancels the command. (The DVIEW command's Zoom and Pan options
function properly in perspective views.)
* Although most commands are now permitted in perspective views, use of a
pointing device to designate points is generally prohibited in such views.
You can type in coordinates using the keyboard, but if you use a pointing
device to enter points, AutoCAD displays the message:
Pointing in perspective view not allowed here.
Entity selection is the only activity that allows pointing device input in
perspective views. Even then, certain commands (BREAK, FILLET, CHAMFER,
TRIM, EXTEND, UCS Entity, and DIM by picking) use the pick point for
calculations and don't permit the point to be supplied by means of a
pointing device in a perspective view.
* On page 324, the Release 10 Reference Manual states that the "Window"
option for the PLOT and PRPLOT commands is not available for perspective
projections. This restriction has been lifted.
* If you use the PLOT/PRPLOT "Extents" option with a perspective view active,
and the CAMERA position is within the drawing extents, AutoCAD displays the
message:
PLOT and PRPLOT extents incalculable, using Display
and proceeds as though you had used "PLOT/PRPLOT Display".
* When plotting a perspective view, an explicit plot scale makes little
sense, so AutoCAD ignores it. If you specify a scale factor, AutoCAD
displays the message:
**Plot of perspective view has been scaled to fit available area.**
and proceeds as though you had responded to the "Specify scale" prompt
with "Fit". Use the paper size to control the overall size of the plot.
TDIBMRD4.3 Page 6 of 10
MISCELLANEOUS CHANGES AND CORRECTIONS
* The default setting for the WORLDVIEW system variable is now 1. This
variable affects the VPOINT and DVIEW commands, as described in Chapter 6
of the AutoCAD Reference Manual.
* The AutoLISP (entsel) function returns a list that includes the point by
which the entity was selected. This point is expressed in UCS coordinates.
* For some time, the AutoLISP Programmer's Reference has warned application
developers to avoid referencing the ATOMLIST symbol list when using the
(vmon) virtual function paging feature. Performance-related changes in
AutoLISP Release 10 make this more important than ever; the ATOMLIST
contents and the order of its items may change if (vmon) is enabled.
* It is now possible to OSNAP to the insertion point of an Attribute within a
Block. If you use "INSERTion" object snap and point to an Attribute within
a Block, the Attribute's insertion point is now chosen rather than that of
the Block. Note that if a Block consists entirely of Attributes, there is
now no way to object snap to the Block's insertion point.
* The FLIP SCREEN function key, all transparent commands, and several
AutoLISP functions are now disabled during certain commands, since some
displays must redraw when flipping from text mode to graphics mode, and a
redraw occurring at critical times could result in an incorrect image.
The commands affected are VPOINT, DVIEW, and ZOOM Dynamic. During these
commands, the FLIP SCREEN key and transparent commands are disabled, as are
the following AutoLISP functions:
(entdel) (getangle) (getpoint) (grtext)
(entmod) (getcorner) (graphscr) (redraw)
(entsel) (getdist) (grclear) (ssget)
(entupd) (getorient) (grdraw) (textscr)
* In previous versions, the HIDE command had trouble with non-planar 3D Faces
and entities that appeared as chevrons or bow-ties when viewed from
particular points in space. Sometimes they were hidden incorrectly, and
sometimes they were simply drawn as wire-frame images (not hidden). In
Release 10, such objects are hidden in a more consistent manner.
HIDE now detects anything that looks like a chevron or a bow-tie from the
current viewing point, and breaks it into two triangles (with an invisible
joining line) for the purpose of hidden-line removal. Any other non-planar
face is broken into two triangles along an arbitrarily chosen diagonal.
* The AutoCAD Reference Manual warns you not to delete AutoCAD's temporary
files while AutoCAD is running (by means of the FILES, SHELL, or SH
commands), and lists the temporary files as having file types of ".$a" or
".$ac". For Release 10, the file type ".ac$" should be added to this list.
* The examples in the middle of page 74 of the AutoLISP Programmer's
Reference are incorrect. They should read:
(setq p (cdr (assoc 10 ed))) would return (2.0 2.0 0.0)
(trans p e 0) would return (2.0 1.53209 1.28558)
TDIBMRD4.3 Page 7 of 10
* The AutoLISP Programmer's Reference states an incorrect range for the
values returned by ATAN. The actual range is -PI/2.0 to +PI/2.0.
* Polar arrays are handled differently in Release 10. In previous versions,
a "No" response to the "Rotate objects as they are copied?" prompt caused
each object to be replicated using its own reference point, as documented
in the AutoCAD Reference Manual. This resulted in the entities moving
independently, rather than retaining their relation to each other as they
would if you replied "Yes". (To visualize the effect, draw circles around
the array's center point and passing through one endpoint of each selected
line, through the center of each selected circle, and so on; then make
copies of each entity along the circumference of its own circle.)
In Release 10, all selected entities are replicated using the same
reference point, so they move as a rigid group, staying in the same
relation in all the copies. The reference point for all the entities is
that of the last entity in the selection-set. Therefore, if you pick the
entities one by one, the last one you pick provides the reference point for
all of them.
If you pick the entities by a Window or Crossing box, the last one in the
selection-set is arbitrary. You can, however, remove one entity from the
set and then add it back in, forcing it to be the last in the
selection-set.
The method recommended in the Reference Manual still works: make a Block of
the entities and create a polar array of the Block. This method gives
greater flexibility, since the reference point for making the array is the
Base (insertion) point of the Block, which can be any point you like. It
does, however, create an array of Block References, which must then be
exploded if you want the individual entities replicated.
* The following clarifies the purpose of the EXPERT system variable.
Some commands issue "are you sure?"-type (confirmation) prompts in odd
circumstances, such as when you use the LAYER command to turn off the
current layer. When you write scripts, menu macros, or AutoLISP programs
that issue command sequences, it is impractical to include responses to
these prompts, since they only appear in odd situations. Using the EXPERT
system variable, you can suppress these confirmation prompts and let the
script, macro, or AutoLISP program proceed with the operation unhindered.
If EXPERT is zero, all prompts are issued normally. Nonzero values
suppress successively more confirmation prompts; as new prompts are added
to AutoCAD, higher EXPERT values control those prompts as well as the older
prompts. In Release 10, an EXPERT value of 4 is sufficient to suppress all
special-situation confirmation prompts.
TDIBMRD4.3 Page 8 of 10
THE DOS "SHARE" UTILITY
* Although explicit network support is not provided, many customers use
AutoCAD on networks without difficulty. We have noticed some problems with
the DOS SHARE command, however.
In order to use AutoCAD Release 10 in conjunction with the DOS SHARE
command, a proper "FCBS=" statement must be present in the CONFIG.SYS file.
If your CONFIG.SYS file already contains an "FCBS=" statement, you should
increase the first value on the "FCBS=" statement (if necessary) until it
is at least 40 greater than the second value. If you have no "FCBS=" at
all, we recommend "FCBS=48,8". If you use AutoCAD's SHELL or "external
commands" feature to run applications that require FCBs, the requirements
of those applications should be added to the values you would otherwise
have used.
DOS 4.0 NOTES
* As of this date, IBM's PC-DOS 4.0 and 4.01 are the only versions of DOS 4.0
currently available, and they are not guaranteed to work on any computer
other than a true IBM PC/XT/AT or PS/2. Furthermore, Autodesk has not yet
certified that AutoCAD runs properly on these versions, even on IBM
computers. In particular, the "/X" option on the "BUFFERS=" and "FILES="
statements (in CONFIG.SYS), the FASTOPEN command, the "MODE CON LINES=43"
(or "=50") command, and IBM's expanded memory emulator may be incompatible
with AutoCAD or Extended AutoLISP.
* The memory reserve specified for external programs in ACAD.PGP (for the
SHELL and SH commands) must be higher for DOS 4.0, since the command
interpreter (COMMAND.COM) requires more memory than it did in previous
versions. For DOS 4.0, the minimum memory reserve is about 40K.
* If your system has hard disk partitions larger than 32 megabytes, DOS 4.0
automatically loads the SHARE program. Therefore, the SHARE notes above
apply to such a system.
TDIBMRD4.3 Page 9 of 10
KNOWN PROBLEMS
* In previous releases, if you set low values for LISPHEAP and LISPSTACK
(such as 5000 each), the memory not used by AutoLISP was made available to
AutoCAD as extra I/O page space, thereby improving AutoCAD's performance.
In Release 10, this is not the case. In fact, use of Extended AutoLISP
should make substantially more I/O page space available, but it does not.
An update to AutoLISP and Extended AutoLISP is planned soon, and will fix
these problems.
* In the initial version of Release 10, attempts to snap to the intersection
of two objects that didn't actually intersect sometimes placed illegal
values in the drawing file. Drawings that contain these illegal values
could cause ZOOM Dynamic and DVIEW to draw garbage on the screen, and
editing the offending entities could cause the system to freeze. This
problem has been fixed in the current version (Release 10 C2). To recover
drawings that were corrupted in this manner by the initial version of
Release 10, simply DXFOUT the drawing, begin a new drawing, and use DXFIN
to restore the corrupted drawing from the DXF file.
* Release 10's IGESIN command has a few known problems:
* Each composite curve is translated into an instance of an anonymous
Block. This accurately reflects the geometry of the composite curve,
but results in an entity that is difficult to edit. (To edit such
a curve, first EXPLODE the Block, forming individual segments.)
* Tabulated cylinders are translated as extrusions. The entity's
extrusion length and direction may be incorrect if it is not parallel
to the World Z axis.
* Dimensions and their defining points may be placed incorrectly if they
do not lie in the World XY plane.
* Early reports indicate that Release 10 may not work with some EGA-clone
display adapters that do not provide complete IBM EGA compatibility.
------------------------------------------------------------------------------
AutoCAD, AutoCAD AEC, and AutoLISP are U.S. registered trademarks of
Autodesk, Inc. ACAD, ADI, AutoFlix, AutoShade, and DXF are additional
trademarks of Autodesk, Inc.
COMPAQ is a registered trademark of COMPAQ Computer Corporation. IBM, AT,
PC-DOS, and PS/2 are registered trademarks of International Business Machines
Corporation. Inboard is a trademark and Intel is a registered trademark of
Intel Corporation.
TDIBMRD4.3 Page 10 of 10
README.ADS
如何找到與所用的編譯環境相關的
ADS 說明文件
1992年 7月11日
ADS 所支援的編譯程式與其它的發展工具，其說明文件都是以文字檔的形式發
行（ASCII 格式，延伸檔名為「.txt」）。這種格式下，當發展工具有所更動
推陳出新時，我們才能夠隨時跟著更新這類的說明文件。
注釋：README.ADS檔案並說明「AutoCAD 發展系統程式員參考手冊」之疏漏或
誤謬之處。相關資料可參考README.DOC檔（UNIX系統上為「readme.doc」檔）。
1.0 AutoCAD(R) 386
==================
說明檔都置於\acad\ads\docs之目錄內。此目錄目前含有下列幾個檔案：
watcom.txt 敘述使用 WATCOM(TM) C/386編譯程式進行編譯的情形。
highc.txt 敘述使用MetaWare(TM) High C(TM)編譯程式進行編譯的情
形。
ztc.txt 敘述使用Zortech C 與 C++ 編譯程式進行編譯的情形。
pharlap.txt 敘述使用 Phar Lap(R) 386|DOS-Extender(TM)環境時的一
般狀況與注意事項，也包括除錯的方式。
realmode.txt Describes compilation using the Real-Mode ADS
interface with the Microsoft(R) C or Borland
Turbo C(R) compiler
敘述使用「實際模式（Real-Mode）」ADS介面配合Borland
的Turbo C(R)或Micirsoft(R) C編譯程式進行編譯的情形。
2.0 AutoCAD SPARCstation(TM) 版
================================
這些說明檔都置於\acad\ads\docs之目錄內。此目錄目前含有下列幾個檔案：
cc.txt 敘述使用cc編譯程式進行編譯與鏈結的情形。
cc11.txt 敘述使用可選用的C 1.1編譯程式（名稱也是cc）進行編譯
與鏈結的情形。
acc.txt 敘述使用可選用的 ANSI C編譯程式（名稱是 acc）進行編
譯與鏈結的情形。
_________________________________________
SPARCstation 是 SPARC International, Inc. 的商標，獨家授權予 Sun
Microsystems, Inc. 其它的品牌與產品名稱皆屬於其相關所有者的商標或註
冊商標。
README.DOC for AutoCAD Release 11 (386)
October 17, 1990 17:25
CONTENTS
General notes ....................................... 2
Plot spooling ....................................... 2
Networking notes .................................... 4
International character (8-bit font) support ........ 5
Manual corrections
AutoCAD Reference Manual ........................ 9
AutoCAD 386 Installation and Performance Guide .. 14
AutoLISP Programmer's Reference ................. 16
ADS Programmer's Reference ...................... 16
AutoCAD Tutorial ................................ 18
Also see the separate Advanced Modeling Extension documentation
update, README.AME
The AME option is not available for the SHOW version of AutoCAD.
AC11386RD-1 Page 1 of 18
General notes
-------------
- Release 11 adds the following device support to AutoCAD 386:
- Summagraphics Microgrid digitizer
- Interrupt-driven choice for Summagraphics Microgrid and MM series
digitizers (offering greatly enhanced digitizer performance)
- IBM 8514/A display (integrated driver)
- COMPAQ Portable III plasma display (integrated driver)
- JDL printer plotter model 750
- Canon Laser Beam printer models LBP-8 and LBP-8II
- Enhanced CalComp plotter driver (now sends "beginning of plot" and
"end of plot" records). This driver should now work with CalComp's
electrostatic plotters.
- AutoCAD 386 now writes prompts and progress messages to the screen much
faster than previous releases. Plot to file and Hide are faster as a
result of this improvement.
- A utility program is provided to allow large programs to be run using
AutoCAD 386's Shell. SHROOM.COM and its documentation file SHROOM.DOC
are supplied in the SAMPLE directory.
Plot spooling
-------------
- The ACADPLCMD and ACADPPCMD environment variable hooks for Plot Spooling
have been enabled for all platforms except the DEC VAXstation.
When plotting to a file named "AUTOSPOOL", AutoCAD generates a unique
file name in the configured plot file directory. Then, if the ACADPLCMD
(for Plot) or ACADPPCMD (for Prplot) environment variable exists, it
composes an operating system command using the string defined by that
variable (substituting the plot file name for the first occurrence of
"%s" in the string), and submits the command to the operating system.
The spooler program (supplied by the operating system or a third-party
application vendor) is typically responsible for the following actions,
although it may do other things as well.
- plotting the file as a background task. A simple case would use
the DOS PRINT utility, but this only works for ASCII plot files.
(PRINT must be loaded as a TSR before running AutoCAD, and must be
directed to the parallel port to which the plotter is attached.)
AC11386RD-1 Page 2 of 18
PRINT doesn't support XON/XOFF protocol, so serial ports can't be
used unless the plotter is wired for hardware handshaking.)
- deleting the file upon completion to make way for more plot files.
Those are the typical requirements, although the actual functionality is
not monitored by AutoCAD in any way.
To use a plot spooler with AutoCAD:
A. Configure AutoCAD to use either an internal driver or a P386 ADI
driver that uses AutoCAD's plotter I/O support (see the supporting
documents for your driver). The spooling mechanism is activated
only if the plot is written to a file, so if you want to use
spooling by default, configure the plotter for plot to file.
(Real-mode ADI drivers have their own method for writing plots to a
file, and cannot use AutoCAD's plot spooling facility. See page 53
of the AutoCAD 386 Installation and Performance Guide.)
B. The configured plot spooler directory must exist, and both AutoCAD
and the spooler program need read/write access to it. When
configuring, include the trailing directory delimiter character for
the system, such as "\" for DOS.
C. Configure the default plot file name as "AUTOSPOOL", or enter
"AUTOSPOOL" as the file at plot time.
D. Set the environment variable "ACADPLCMD" to a DOS command string
that invokes the plot spooler, with "%s" where the plot file name
should get filled in.
E. If the operation of the plot spooler command depends on a TSR having
been installed, the TSR must be installed BEFORE you start AutoCAD.
Loading a TSR via execution of ACADPLCMD at plot time (or via the
Shell command) is likely to be fatal to both the TSR and AutoCAD, if
the TSR trashes any of the DOS Extender's interrupt vectors.
For example, if plots are to be processed by a SPOOLPL program on DOS,
the definition of ACADPLCMD might be:
SET ACADPLCMD=SPOOLPL %s
assuming that a plot spooler program named SPOOLPL is present on the
search path and accepts the plot file name as a parameter.
The mechanism is the same for the Prplot command, except the ACADPPCMD
environment variable is used.
NOTE: Placing the definition in AUTOEXEC.BAT is advisable if you intend
to use plot spooling frequently. However, in DOS batch (.BAT)
files, "%" is used to reference parameters. If you set ACADPLCMD
or ACADPPCMD using a .BAT file, remember to use two "%" signs in
a row, as in:
SET ACADPLCMD=PRINT %%s
AC11386RD-1 Page 3 of 18
Networking notes
----------------
AutoCAD Release 11 is designed to operate on a wide variety of networks.
Although several popular networks have been tested, no particular vendors
have been designated as "supported". A few problem areas have been
identified:
- Directory permissions for the 386|VMM swap file location must allow file
creation and read/write operations to occur. If the swap file cannot be
created, 386|VMM prints a message stating "Error creating swap file" and
AutoCAD exits.
- If you plan to execute AutoCAD while your current directory is one that
resides on a remote node, performance will be substantially better if
AutoCAD 386 is configured to place its VMM|386 swap file on a local disk
drive using the "-swapdir" switch documented on pages 76 and 170 of the
AutoCAD 386 Installation and Performance Guide (I&PG).
Furthermore, placing the swap directory on local storage is a workaround
for an apparent problem on Novell Netware 386, where running with a
current directory residing on a remote node often causes AutoCAD to exit
immediately after being called from the DOS command prompt.
- If you plan to run AutoCAD frequently from a drive mounted on a remote
node, you should also consider setting the "-nopgexp" switch to reduce
network traffic when paging program code. This switch is documented on
pages 43 and 169 of the AutoCAD 386 I&PG.
- AutoCAD's file locking, and AutoCAD itself, will not run properly on
Novell Netware 286 if read-only directories are used. There is no known
fix at this time.
- Novell NetWare 386 3.1 allows programs to open read-only files in
read-write mode if you have "READ ONLY COMPATIBILITY = On" in your
SHELL.CFG file, but reports an error when you try to write to the file.
In general, we recommend that you do not turn on this mode. However, if
this mode is required by another software application that you use, you
will need to obtain the "FIXOPEN" NLM patch available from Novell, or
AutoCAD will not function properly when editing read-only files.
- SunOS 4.0 lacks the DOS file sharing support required for proper
operation of AutoCAD on PC-NFS networks. Operation of AutoCAD in this
environment can result in bad data transfers. You can work around the
problem by using the /SHARE option on the NET USE command when mounting
any network drives used to store drawing files. (See your PC-NFS manual
for further information on the /SHARE option.) SunOS 4.0.1 and later
releases fix the problem.
- On 3Com networks, library/support files such as ACAD.DWG, ACAD.MNX, and
TXT.SHX must be read-only in order to be shared by multiple users. This
is also true of any other files to be shared on 3Com networks. In
particular, the ACAD.PWD login file shared by users must be read-only.
However, the copy of ACAD.PWD in the server's temporary files directory
must be read-write-createable, as this file keeps track of the number of
users currently using AutoCAD.
AC11386RD-1 Page 4 of 18
- AutoCAD holds the ACAD.MNX compiled menu file and any running or paused
script file open while you're in the drawing editor. Thus, if you've
loaded the DOS SHARE utility and you use Shell to run a DOS command such
as COPY or DEL on any of these open files, you'll receive a Sharing
violation and be given an opportunity to abort the command.
International character (8-bit font) support
--------------------------------------------
The International versions of AutoCAD 386 Release 11 support 8-bit ASCII
text characters for the benefit of languages that require them (provided
that the host system, the supplied shape files, and the display drivers
support them as well). 8-bit ASCII support means that 8-bit ASCII text
characters can be displayed in AUI and on the text screen, as well as in
Text, Attribute, and Dimension entity strings. There are no commands
specific to using 8-bit ASCII text; when an International version is
installed and configured with the proper display driver, more characters
become available.
The domestic (North American) version of AutoCAD 386 continues to support
only 7-bit fonts for AUI and text-screen characters. (AUI dialogue boxes
use character number 128 as the "check" mark.) If a text character with a
value greater than 128 is output to the display driver (in text mode or
through the AUI menus, dialog boxes, command line, etc), it is replaced
with a "?" character. However, entity text strings can contain 8-bit
characters (shape numbers 32 through 255).
The following is a fairly complete technical description of AutoCAD's
8-bit ASCII support. Drawings created with 8-bit and 7-bit versions of
AutoCAD are compatible with both versions of AutoCAD, with exceptions
noted in a later section.
I. The features of the 8-bit ASCII (International) version of AutoCAD are
listed here. Behavior of the 7-bit version for the same circumstances
is also listed when appropriate.
1. Built-in display drivers
In the 7-bit version of AutoCAD, built-in display drivers treat
character code 128 as the AUI "check" mark, and display "?" when
sent ASCII codes greater than 128.
In the 8-bit version of AutoCAD, built-in display drivers treat
character code 255 as the AUI "check" mark, and can display ASCII
codes greater than 127 for AUI text (such as dialogue boxes), the
command line, menus, and the text screen. The text "glyphs" are
obtained from the active DOS code page, as described in DOS
reference manuals.
NOTE: The Swedish version of AutoCAD is 8-bit, but may use yet
another value for the check mark, as both 128 and 255 are
used for ordinary characters by some Swedish platforms.
AC11386RD-1 Page 5 of 18
2. ADI display drivers
ADI 4.1 protected- and real-mode display drivers now perform
additional communication with AutoCAD to determine:
- whether they are talking to a 7-bit or 8-bit version of AutoCAD,
and:
- If an 8-bit version of AutoCAD is in use, which character code is
used for the AUI "check" mark.
ADI 4.1 display drivers also tell AutoCAD whether they support
8-bit characters. The 7-bit version of AutoCAD assumes that the
driver operates in 7-bit mode. 8-bit versions of AutoCAD can work
with either 7-bit or 8-bit drivers, but a 7-bit driver forces an
8-bit AutoCAD to operate in 7-bit mode. All display drivers
written for ADI 4.0 and earlier operate in 7-bit mode. See the ADI
4.1 Driver Development Kit manual for more information.
3. Special codes for dimensioning symbols
The 8-bit and 7-bit versions of AutoCAD use different integer codes
for the characters representing the three special dimensioning
symbols. The table below shows the names of these symbols, their
generic text control sequences, and their version-dependent integer
values.
Symbol Control 7-Bit 8-Bit
Name Sequence Value Value
--------------- -------- ----- -----
Degrees %%d 127 248
Plus-Minus %%p 128 241
Circle Diameter %%c 129 237
Although it is possible to use the integer values for these symbols
directly in a text control sequence (as in %%127), or to enter them
using the ALT key (as in ALT + 1-2-7), these approaches don't
account for the differing values in the 7-bit and 8-bit versions of
AutoCAD. Therefore, we recommend against using them if you want
your special symbols to be compatible with both 7-bit and 8-bit
versions of AutoCAD.
4. AutoCAD dimension strings
In previous versions of AutoCAD, the dimensioning commands used the
control sequences "%%127", "%%128" and "%%129" to generate the above
special symbols. In both the 7-bit and 8-bit versions of Release
11, these commands now use the "%%d", "%%p" and "%%c" sequences.
Thus, drawings created in one version can be loaded and displayed
without error in the other version.
AC11386RD-1 Page 6 of 18
5. Automatic conversion of Dimension entity strings in older drawings
When a pre-Release-11 drawing is loaded into Release 11's drawing
editor (from the Main Menu, or via an Insert, Xref, or Dxfin
command), its Dimensions may have text strings containing "%%127",
"%%128", and "%%129" control sequences for the three special
dimensioning symbols. If any are found, they are translated
automatically to "%%d", "%%p", and "%%c", respectively. Once you
End, Save, or Wblock the drawing, the new control sequences will be
permanently stored. This conversion is not performed on Release 11
drawings.
6. Automatic symbol mapping
When an 8-bit AutoCAD loads a font file and determines that it has
no entry for code 248, 241, or 237 (but that it does have an entry
for the corresponding 127, 128, or 129 code), the 127-129 shape
definitions are copied into their corresponding 8-bit codes. In
this manner, existing drawings and 7-bit font files can be used with
the 8-bit version of AutoCAD without difficulty.
7. Differing alphabetic character sets for different languages
Different sets of ASCII characters make up the alphabet in different
languages. However, to ensure that drawings will be compatible
across different language versions of AutoCAD, symbol table (e.g.,
layer, linetype, text style) entries must use a common subset of the
available characters. Currently, this subset is the upper-case
Roman letters "A" through "Z", the digits "0" through "9", and the
characters "$", "_" and "-".
8. Command option keyword abbreviations
The 8-bit ASCII versions of AutoCAD support abbreviations for
command option keywords that begin after the first letter of the
keyword, when the allowed abbreviation is represented by the first
contiguous string of capitalized alphabetic characters shown in the
prompt.
For example, the keyword "nanTUCKet" could be specified by the
string "TUCK".
The 7-bit ASCII version of AutoCAD continues to require
abbreviations of command option keywords to begin at the start of
the keyword. (Certain keywords, such as "eXit", are exceptions to
this rule. In the 8-bit ASCII versions, this is typical.)
II. Where 8-bit ASCII characters are defined
1. The DOS Code Page facility is used to change the "glyphs" of all
ASCII characters in text mode (and for AUI text on most display
drivers). Instructions for the use of Code Pages can be found in
the DOS Reference Manual.
AC11386RD-1 Page 7 of 18
2. The AutoCAD font files contain symbol definitions for the characters
in Text, Attribute, and Dimension entity text strings. Entries for
ASCII character codes 32 through 255 have always been supported, but
many of the font files shipped with AutoCAD have only their first
129 characters defined. There are exceptions, usually denoted by an
"8" at the end of their font name, such as ISO8.SHP/SHX. So, if you
intend to use a full 8-bit ASCII character set, you may have to
extend some of the font files yourself, or obtain 8-bit font files
from other sources. Defining the 8-bit characters is done in the
same manner as the existing 7-bit characters, and they can be added
to existing font files with no harm done.
III. Compatibility notes and exceptions
1. A drawing created in an 8-bit AutoCAD can be edited with a 7-bit
AutoCAD. However, if the drawing has the character code 128 in
entity text strings, AUI dialogue boxes that display the text (such
as for Ddatte or Ddedit) will display a "check" mark in place of the
desired character. (The AUI "check" mark is two character cells
wide, so it will obscure the following character as well.) This is
harmless, but looks ugly. Other ASCII codes greater than 128 are
replaced by "?" marks in AUI text strings; this is also harmless.
2. KANJI (Japanese) AutoCAD uses 7-bit codes, but certain codes are
interpreted as the first byte of a two-byte (16-bit) KANJI code.
Therefore, KANJI AutoCAD drawings will not display correctly on
8-bit ASCII AutoCAD, because all characters will be interpreted as
8-bit ASCII characters.
Conversely, 8-bit ASCII strings can be confused for KANJI 16-bit
characters in a 7-bit AutoCAD, although this is far less likely,
since the code must be defined in a BIGFONT shape file, etc.
3. Drawings that reference font files containing definitions for
character codes 248, 241, and 237, when loaded into 8-bit AutoCAD,
will use those codes for the degree, plus/minus, and diameter
symbols when the AutoCAD dimensioning commands or other commands
enter the "%%d", "%%p", and "%%c" control sequences into drawing
entity text strings.
4. The text control sequences "%%127", "%%128", and "%%129" are
converted to "%%d", "%%p", and "%%c" if found within Dimension
entities in a pre-Release-11 drawing. Only Dimension entities are
converted, however. Therefore, if such a drawing is loaded into an
8-bit AutoCAD, any non-Dimension entities containing these control
sequences may no longer display the desired symbols. There should
be no problem in the 7-bit version of AutoCAD, however.
5. At this writing, it is not clear that all languages can be
restricted to use of upper-case Roman letters for symbol table
entries, and thus be compatible with each other.
AC11386RD-1 Page 8 of 18
AutoCAD Reference Manual corrections
------------------------------------
Chapter 2
- "Entity Selection". In the description of the "Previous" option on page
62, the last sentence in the Note should read:
AutoCAD remembers the space (model or paper) in which each
selection-set is obtained; the "previous" selection-set is also
cleared if you switch spaces and attempt to use it in the other
space.
Chapter 4
- "Text Command", pages 129-134. The description of the new text
alignment modes is incorrect, and should be changed as follows:
Page 129. The last paragraph should read:
You can align text using any combination of
top/middle/baseline/bottom and left/center/right alignment modes.
Baseline refers to the line along which the bases of the capital
letters lie. If you imagine a box surrounding the text, then
letters with descenders (such as p, g, and y) dip below the
baseline to the bottom of the box, and capital letters reach the
top of the box. The middle position is halfway between the
baseline and the top. The following figure shows the text
alignment positions.
Page 130. The "middle" indicator in the figure should be halfway
between the baseline and the top.
Page 134, "Text M - Fully Centered Text". The Note at the top of the
page should read:
The difference between this option and MCenter is that rather than
using the halfway point between the baseline and the top, Middle
uses the midpoint of an imaginary box surrounding the text string.
Therefore, its effect differs depending on whether the text string
has descenders or any characters that reach the top.
Page 134. In Table 4-2, the notation "(same as M)" should be removed
from the MC entry.
Chapter 5
- "Entity Selection". In the third paragraph on page 146, it should be
noted that UCSes whose extrusion directions are directly opposite each
other are not considered "parallel".
AC11386RD-1 Page 9 of 18
- "Filleting Two Straight Lines", page 172. The first paragraph's second
sentence is incorrect and should read:
It then trims the lines (retaining the "picked" segments if they
cross) and creates a fillet arc with the current fillet radius.
- "Undo - Notes and Interactions", page 201. The following should be added:
Undo does not undo changes made to the CVPORT system variable by the
SETVAR command (or the equivalent AutoLISP/ADS functions).
Chapter 7
- "Color Numbers", page 260. At the end of the fourth paragraph, "Mslide
command" should be replaced by "Vslide command".
- "Entity Handles", page 262. The following should be appended to the
first paragraph:
Entity handles are often, but not always, assigned sequentially.
- "Which Operations Change Handles?". The "Wblock *" command now retains
entity handles, so the last paragraph on page 263 should begin:
With the exception of "Wblock *", all forms ...
- "Ddlmodes Command". Append the following to the first paragraph on page
283:
(Hatch blocks, Dimensions, and Blocks whose entities use color "by
block" won't adapt to transparent color changes until the next
regen, although no alert will appear.)
Chapter 8
- "Axis Command", page 291. In addition to the restrictions noted in the
second paragraph, the Axis command works only when TILEMODE is on.
- "Object Snap Modes", page 307. Add the following to the description of
"Nearest" mode:
Use of this mode with Circles and Arcs requires that their extrusion
direction be parallel to the Z axis of the current UCS.
AC11386RD-1 Page 10 of 18
Chapter 9
- "Wblock Command". The "*" form of the Wblock command now retains entity
handles, as well as all named views, User Coordinate Systems, and
viewport configurations. The first paragraph on page 331 should now
read:
The entire drawing is written. This is similar to the Save command
("Save Command - Updating Without Exit" on page 68), except that
unreferenced symbols (Block Definitions, layers, linetypes, text
styles, and dimension styles) are not written. AutoCAD writes model
space entities to model space in the new drawing, and paper space
entities to paper space.
and the third paragraph on page 331 should now read:
With the exception of the "*" form of the command, Wblock sets the
output file's HANDLES system variable to 0 (disabled) and does not
write entity handles to the output file.
- "Using an Xref's Dependent Symbols", page 347. In the second paragraph,
replace "though any changes" with "but if the VISRETAIN system variable
is set to 0 (the default) any changes". Following the second paragraph,
add:
When VISRETAIN is set to 1, the current drawing's On/Off and
Freeze/Thaw settings for Xref-dependent layers take precedence.
They are saved with the drawing and are preserved during Xref reload
operations.
Color and linetype settings for Xref-dependent layers are not
affected by VISRETAIN, but are always reset upon reload of the Xref.
Chapter 10
- "Diameter Dimensioning", page 375. In the paragraph beginning "The
third style ...", the last two sentences are incorrect and should be
deleted.
Chapter 11
- "Variables and Expressions". Note #2 at the bottom of page 414 is
incorrect. TEXTEVAL does not affect the Dtext command.
Chapter 13
- New "Processing entity: nnn" messages may appear during plotting if many
entities have been processed without generating plot vectors. The new
message is simply meant to let you know that something's happening.
AC11386RD-1 Page 11 of 18
Appendix A
- "Standard Prototype Drawing", pages 446-447. The object selection
pickbox size is shown as being stored in both the prototype drawing and
AutoCAD's configuration file. It is actually stored in the
configuration file only.
- "Modify Pull-down Menu", page 451. The "Mirror" description incorrectly
states that Auto selection mode is used.
- "Options Pull-down Menu", page 453. The "Donut Diameters" description
should read:
Invokes the Donut command, allowing you to set the inside and
outside diameters.
- "System Variables", pages 467-475. Two new system variables should be
added to Table A-1.
DIASTAT (integer, not saved)
Dialogue box exit status. If 0, the most recent dialogue box
was exited via "CANCEL". If 1, exit was via "OK". (read-only)
VISRETAIN (integer, saved with drawing)
If set to 0 (the default value), On/Off and Freeze/Thaw settings
for Xref-dependent layers are reset to their state in the
referenced drawing upon each reload. When set to 1, the current
drawing's settings are preserved.
Appendix B
- "Extended and Expanded Memory Usage", page 481. This section applies
only to the 640K DOS version of AutoCAD. Use of expanded memory with
AutoCAD 386 requires a memory manager that conforms to the VCPI
interface standard. See the AutoCAD 386 I&PG for further information.
- "Menu Bar and Pull-down Menus". Two changes should be made to page 489.
The following should be appended to the second paragraph:
If the titles won't all fit in the menu bar, AutoCAD truncates
characters one by one from the longest title (checking each time to
see which is now longest), until they all fit. This can result in
some silly-looking titles, so you should attempt to fit everything
in 80 columns if possible.
and the last paragraph should be changed to read:
Each pull-down menu ordinarily appears directly beneath its menu bar
title. However, the rightmost menus shift to the left to
accommodate long menu items. The maximum number of items in a
pull-down menu is governed by the display device, and may be as low
as 21; be sure to consider this when designing custom menus.
AC11386RD-1 Page 12 of 18
- "Extended big-font", page 512. The first two lines of the bigfont
format description should be replaced by:
*0, 5, font name
character height, character depth, modes, character width, 0
- "Command Aliases and Abbreviations", page 523. The following note
should be added at the bottom of the page:
Aliases cannot be used in a command script. Use of aliases in menu
files is not recommended.
Appendix C
- "HEADER Section", page 536. $VISRETAIN should be added to the list of
DXF header variables (type 70; 1 = retain Xref-dependent visibility
settings, 0 = don't retain).
- "TABLES Section", page 537. Add the following to the DIMSTYLE group
code listing: 49 (dimgap), and 146 (dimtfac).
- "TABLES Section", page 538. Table C-3 (Group 70 bit codes for LAYER
table) is incorrect. It should read:
Flag bit
value Meaning
-------- --------------------------------------------------
0 Layer is On and Thawed.
1 Layer is Frozen.
2 If set, layer is frozen by default in new Viewports.
4 Unused
8 Unused
16 if set, layer is externally dependent.
32 if this bit and bit 16 are both set, this externally
dependent layer has been successfully resolved.
Xref-dependent layers are output during Dxfout. For such layers, the
associated linetype name in the DXF file is always CONTINUOUS.
- "Viewport", pages 546-547. In Table C-13, the first 1070 group should
be described as an integer whose value is 16 for Release 11. Also, the
description for the "1003..." entry near the end of the table should
read:
The names of layers that are frozen in this Viewport. This list may
include Xref-dependent layers. Any number of 1003 groups may appear
here.
- "DXB File Format". Byte code 255 should be removed from Table C-15 on
page 560. It is valid for Binary DXF, but not for DXB.
AC11386RD-1 Page 13 of 18
Appendix D
- "Command Differences". The following entries should be added to Table
D-3 on pages 571-572:
Dim Changes to the Radius and Diameter subcommands result in an
additional prompt in some situations. This may cause
failure of some old scripts and AutoLISP programs that
issue these commands.
Fillet When filleting two Lines that cross, AutoCAD now retains
the "picked" line segments. In previous versions, the
shorter ends were trimmed, no matter what points you used
to select the Lines.
Osnap Running object snap modes are now ignored during entity
selection.
and the following should be added to the "Wblock" entry on page 572:
The "*" form of the Wblock command now retains all entity
handles, named views, UCSes, and viewport configurations.
- "System Variable Differences". The following entries should be added to
Table D-4 on page 573.
CECOLOR In Release 10, this variable contained a string consisting
of "BYLAYER", "BYBLOCK", a color number (e.g., "15"), or a
standard color number and name (as in "1 (red)"). This
last form has been dropped, so applications will no longer
need special code to cope with its embedded blank. The
standard color numbers now appear simply as "1" - "7".
OSMODE Running object snap modes are now ignored during entity
selection.
AutoCAD 386 Installation and Performance Guide corrections
----------------------------------------------------------
- "AutoCAD 386 and Memory Managers", page 3. Add to this section:
"HIMEM.SYS does not conform to the VCPI specification, and is not
compatible with AutoCAD 386."
- "Essential Hardware and Software". In the second paragraph on page 8,
"8.7 megabytes" should be changed to "9 megabytes". Also, it should be
noted that additional free disk space is needed by AutoCAD 386's virtual
memory system, especially when editing large drawings.
- "1.2 Megabyte Release Format" and "720K Release Format", pages 13-18.
The acad.pwd login file is not supplied on the release disks; it is
created during initial configuration. Also, the ADS disk for AutoCAD
386 does not include a DDE directory.
- "Installation Steps", The second paragraph on page 24 (a bullet
concerning acadcfg.old) is incorrect and should be deleted.
AC11386RD-1 Page 14 of 18
- "Reconfiguring AutoCAD", page 27. Add the following:
Never swap ACAD.CFG configuration files (via a Shell or Files
command) while AutoCAD is running; doing so may cause unpredictable
behavior of AutoCAD.
- "The Acad.pwd File", page 42. The two paragraphs in this section are
incorrect and should be replaced by the following:
Acad.pwd is the "login file" that contains encrypted authorization
data essential to running AutoCAD on both stand-alone and networked
machines. AutoCAD creates the acad.pwd file during the server
authorization phase of the configuration process. If the file
becomes corrupted, AutoCAD forces a reconfiguration and rebuilds it.
- "The AutoCAD Shell Command". The following should be added after the
fourth paragraph on page 63:
A utility program called SHROOM.COM is provided to allow very large
programs to be run via AutoCAD 386's Shell. [ For details, see the
separate file SHROOM.DOC. SHROOM.COM and SHROOM.DOC are supplied in
the SAMPLE directory. ]
- "IBM Enhanced Graphics Display", page 92. Append the following to the
first paragraph:
EGA cards with less than 256K video memory are not supported. A
"semi" dual-screen mode occurs if you are using two video displays,
and the EGA is not the current display. In "semi" dual-screen mode,
AutoCAD uses the EGA to display the drawing, the status line, the
menus, the dialogue boxes, and the command prompts, and uses the
other display for the text screen. (In true dual-screen mode, the
other display is also used for the command prompts.)
- "Houston Instrument DMP Series", page 136. The number of pens supported
on the DMP-62MP plotter has been increased from 6 to 8.
- "PostScript Laser Printers", page 138. Replace the first paragraph with
the following:
AutoCAD 386 supports PostScript laser printers and plotters using
either a Centronics-type parallel I/O port or an RS-232C serial I/O
port. If a serial port is used, set the printer for 9600 baud, even
parity, 7 data bits, 1 stop bit, and XON/XOFF protocol (some have a
choice of XON/XOFF or DTR). See your hardware documentation for
specific installation instructions.
- "Noswfgrow1st Switch", page 170. The following should be added:
The longer you remain in AutoCAD, the larger the swap file will grow
(up to a point). If you often spend hours or days without exiting
AutoCAD, we suggest that you use the "-noswfgrow1st" switch so
you'll be less likely to run out of disk space during an editing
session.
- "Swap File Size", page 170. In the second paragraph, "-maxswfize"
should be "-maxswfsize".
AC11386RD-1 Page 15 of 18
AutoLISP Programmer's Reference corrections
-------------------------------------------
- "(fix)", page 42. If the result is outside the range of integers for
this implementation of AutoLISP, (fix) returns as a real. For instance,
if the implementation uses 16-bit integers,
(fix 32767.5) would return 32767
but
(fix 32768.5) would return 32768.0
- "(*error*)", page 76. The following should be added:
Your *error* function should NOT include any calls to (command).
- "Error Codes". The description of ERRNO code 52 on page 169 is
incorrect. It should be "Entity selection: null response".
ADS Programmer's Reference corrections
--------------------------------------
- "Common Characteristics of ADS Library Functions", page 8. Add the
following to the end of this section:
ADS user functions and data type definitions begin with the prefix
"ads_". Another prefix, "adsi_", is reserved for internal use.
- "Retrieving Extended Entity Data". At the bottom of page 78, "static
struc resbuf" should be "static struct resbuf" (add missing "t").
- "Entity Data Functions". In the example on page 71, the first argument to
ads_buildlist() should be RTDXF0 rather than 0.
- "ads_cmd", page 89. In the second paragraph, RTSTRING should be RTSTR.
- "ads_cmd" and "ads_command", pages 89-90. The following details should
be added to the descriptions:
- ADS programs can pause for user input by using ads_cmd() or
ads_command() to pass a string containing a single backslash. Since
the particular control string may change in the future, we suggest
that a preprocessor macro be used for this purpose. For example:
#define PAUSE "\\" /* a single backslash */
ads_command(RTSTR, "Zoom", RTSTR, PAUSE, RTNONE);
(In C, as in AutoLISP, two backslashes must be used to produce one
backslash in a string constant.)
- Certain AutoCAD commands (such as Trim, Extend, and Fillet) require
a "pick" point to be supplied along with the entity to be operated
upon. In order to supply such entity/point data pairs, an ADS
program must use the sequence:
AC11386RD-1 Page 16 of 18
RTLB, RTENAME, <entity>, RTPOINT, <point>, RTLE
or
RTLB, RTENAME, <entity>, RT3DPOINT, <point>, RTLE
with ads_command(). A similar chain of result buffers can also be built
using ads_buildlist()) and passed to ads_cmd(). The 2D or 3D "pick"
point must follow the entity name, and the pair must be surrounded by
RTLB/RTLE. For example, the following trims a line to a circle.
ads_point p1
ads_name first, last;
ads_command(RTSTR, "Circle", RTSTR, "5,5", RTSTR, "2", 0);
ads_command(RTSTR, "Line", RTSTR, "1,5", RTSTR, "8,5",
RTSTR, "", 0);
ads_entnext(NULL, first); /* Get circle */
ads_entlast(last); /* Get line */
p1[X] = 2.0; p1[Y] = 5.0; p1[Z] = 0.0; /* Set pick point */
ads_command(RTSTR, "Trim", RTENAME, first, RTSTR, "",
RTLB, RTENAME, last, RT3DPOINT, p1, RTLE,
RTSTR, "", 0);
- "The DOS Extender (AutoCAD 386) Environment", page 171. The supported
version of MetaWare High C 386 is 1.62 (for 32-bit systems). The Watcom
C 386 compiler is not yet supported. A Watcom environment will be
provided in a future update.
- "Avoiding Trouble", page 163. The following new topic should be added:
File Access Modes
For compatibility with the way AutoCAD and AutoLISP open files,
ADS programs should set the appropriate network file access modes
whenever opening files with the fopen() library function.
In MetaWare High C 386, this is done by #including <system.cf> and
setting a global variable just before calling the fopen() library
function. If you're opening a file for writing or appending, use:
Sharing_mode = Deny_read_write;
to prevent others from reading or writing the file while your
application is accessing it. To open a file for reading:
Sharing_mode = Deny_write;
allowing others to read the file, but not write to it. When
fopen() returns, reset Sharing_mode via:
Sharing_mode = Compatibility;
- "Symbolic Codes for On-Line Program Errors". The description of error
code OL_ENTSELNULL (value 52) on page 185 is incorrect. It should be
"Entity selection: null response".
AC11386RD-1 Page 17 of 18
AutoCAD Tutorial corrections
----------------------------
- "Creating Another Dimension Style", page 54. In the example, "dimclre"
should be "dimclrd" to change the dimension line color.
- "Plotting to Scale in Model Space Viewports", page 166. At the bottom
of the page, the ".25xp" example should read "1mm=4mm" rather than
"1mm=14mm".
- "Editing Viewports", page 170. The third paragraph should begin:
Since we no longer need the 2-foot line ...
- "Standardizing the Height of Dimension Text in Model Space", page 179.
The arithmetic should read:
.18 (size in model space drawing units)
X 1/180 (XP zoom scale factor)
--------
= .001 (size in plot units)
In the next large paragraph, "setting DIMSCALE to 96" should read
"setting DIMSCALE to 180".
- "Adding the Border and View Labels". On page 195, in the paragraph
below Figure 6-46, "8-by-10-inch border" should be "32-by-21-inch
border".
AC11386RD-1 Page 18 of 18
README.ADS
How to Find Platform-Specific
ADS Documentation
June 11, 1992
The documentation for supported compilers and other development
tools is distributed in the form of text files (in ASCII format,
with a ".txt" filename extension). This format enables us to update
this documentation as development tools change and new tools become
available.
NOTE: This file, README.ADS, does not describe any bugs or omissions
in the printed "AutoCAD Development System(TM) Programmer's
Reference." For that information, refer to the file README.DOC
("readme.doc" on UNIX(R) systems).
1.0 AutoCAD(R) 386
==================
The document files are distributed in the directory \acad\ads\docs.
This directory currently contains the following files:
watcom.txt Describes compilation using the WATCOM(TM) C/386
compiler
highc.txt Describes compilation using the MetaWare(TM)
High C(TM) compiler
ztc.txt Describes compilation using the Zortech C and C++
compiler
pharlap.txt Describes some general conditions and
considerations of the Phar Lap(R)
386|DOS-Extender(TM) environment, including
debugging
realmode.txt Describes compilation using the Real-Mode ADS
interface with the Microsoft(R) C or Borland
Turbo C(R) compiler
2.0 AutoCAD FOR THE SPARCstation(TM)
====================================
The document files are distributed in the directory /acad/ads/docs.
This directory currently contains the following files:
cc.txt Describes compiling and linking using the C
compiler cc
cc11.txt Describes compiling and linking using the optional
C 1.1 compiler (also named cc)
acc.txt Describes compiling and linking using the optional
ANSI C compiler (named acc)
_________________________________________
SPARCstation is a trademark of SPARC International, Inc., licensed
exclusively to Sun Microsystems, Inc. Other brand and product names
are trademarks or registered trademarks of their respective holders.
Welcome to AutoSchema User! You have purchased the [AutoSchema-complete]
AutoSchema is sold in the following packages:
Nov 1990
==============================================================================
[AutoSchema-introductory offer] which include manual and system disk.
[AutoSchema-complete] which include manual, system disk and library disk.
[AutoSchema-full package] which include manual, system & library disk, and
tutorial disk pack.
Please note that you must have at least 4 MB of free disk space before you
can install AutoSchema and make sure the library file would not grow out of
disk space as you continue using AutoSchema. The schematic and PCB parts
library files, when properly installed, contains more 2 MB of compressed
drawing parts & symbols which is equivalent to about 7 MB when fully expanded.
If you have bought [AutoSchema-introductory offer], only very limited
schematic library are availible. The user can check the available
symbols by browsing through the pages of icon menu. The user can get the
full set of library symbols by upgrading to [AutoSchema-complete].
[AutoSchema-complete] include full set of schematic & PCB parts library.
Please check the available symbol library by browsing the ICON_SCH, ICON_LIB
and ICON_PRT. (ICON_PRT is under the PART_PL command sub-menu)
AutoPCB include full set of AutoSchema commands plus additional features in
component placement and autorouting. Please contact your local dealers for
information.
===============================================================================
Nov 1990
-------------------------------------------------------------------------------
For some reasons, some users may use drive B: to install AutoSchema or AutoPCB.
Since our installation program assumes the users install from drive A:; if for
some reasons that the installation would be in drive B:, please use the
following DOS command first before installation:-
ASSIGN a = b
If the users are installing either the program files or the APBCUSER working
directory in drive other than C:, check that the PATH statement in the
AUTOEXEC.BAT file is correct:-
set acad=[x:]\prolib\lib
path [x:]\dos;[x:]\prolib\bin;[x:]\acad;
where [x:] is the appropiate drive destination. For example, C:.
===============================================================================
June 6, 1990
-------------------------------------------------------------------------------
Good news!! Now you can browse around the libraries through
the ICON menu that comes with the package.
Three new screen commands are now avaiable:
1. ICON_SCH -- for invoking the schematic icon menu.
2. ICON_PRT -- for invoking the PCB icon menu.
3. ICON_LIB -- for invoking the general library icon menu.
You can insert any component from the library by selecting
any icon from the icon menu.
Furthermore, you can update this icon menu by following the
steps below. Of course, these operations must be performed
after the system has been properly installed.
At the DOS prompt and in any of your workspace, type:
makeicon <enter>
The system will prompt you which library to generate the icons
from. Select the one that you have new components created. The
rest is automatic. Depending upon the size of the library, for
example, the schematic library is so large that it requires at
least 10 M bytes left in the disk drive where the library resides.
Also, generating the schematic icon menu may take several hours.
June 27, 1990
________________________________________________________________________________
1. In AutoPCB User's Manual page 29, section 2.1.2 Usage:MPC; you don't have
to give a Hard Drive name. MPC will automatically find your APCBUSER work
directory, and will create a new work space subdirectory under APCBUSER.
The Format is : MPC workspace_name <enter>
2. AutoPCB User's Manual page 30, section 2.1.3.
Usage : GPC; same as MPC usage, you only need to type is:
GPC workspace_name <enter>
3. AutoPCB User's Manual page 31, section 2.1.4.
Usage of LPC; same as MPC or GPC, you only need to type :
LPC <enter>
LPC will automatically find any work space subdirectory under APCBUSER.
4. Hybrid Users:
The following are the recent additions:
a, You can specify both the printed resistor overlap and the
conductor pad width during the schematic post processing.
b, The printed resistors together with their conductor pads will
be created automatically before the parts placement. You need
not specify the insertion point, the locations of the reference
designator and the resistor value.
c, Resistor table ".res" generated by the schem program provides
another means of data input into the system for design
modification.
d, Substrate pads for the dies will be created on separate layers
(G1 thru G16) where G1 corresponds to C1, etc.
5. Schematic symbols are now equiped with connection marks for
positive identification of signal line connections during
schematic entry. The system will automatically detect line overlap
and will repair such connections immediately. Solder dots for "T"
junctions are dropped automatically wherever needed.
July 15, 1990
------------------------------------------------------------------------------
Please note the default layer for SMT pad (component side) now changed to
layer G1, instead of layer 44; layer for SMT pad on solder side now change
to layer G2, instead of layer 45. If you want to change the default layer,
you have to edit Trace Layer Menu (refer to AutoPCB's User Manual page 167,
section 4.6.4.7). For example: Change G1 to 44, G2 to 45 etc.
Nov. 12, 1990
_______________________________________________________________________________
We have a new Schem Compiler in this package:
SCHEM386.EXE.
This SCHEM386.EXE program requires 80386 (or 80486) machine with 80387.
*************************************************************************
* The SCHEM386.EXE will only generate ASCII format netlist (*.NET), you *
* need to run NETCOMP.EXE program in order to generate a binary format *
* netlist (*.BNL) for the AutoPCB's Router!!! *
*************************************************************************
SCHEM.EXE now is only for the customers whose have AutoHybrid version
Package. AutoHybrid customers should run SCHEM.EXE program first, and
then run SCHEM386.EXE. The SCHEM.EXE will tell you when to run SCHEM386
program. Just follow the instruction!
Customers whose have regular package (i.e. PCB-1, PCB-2, AutoPCB-
Professional, AutoSchema, and AutoPCB-Push&Shove etc.) need only run
SCHEM386 program!
Note: When you using SCH_ICON command to get parts from library, during the
unzip stage, if the message is " warning: insufficent memory ", pleae
do the following things:
1. Save your drawing file.
2. Exit AutoCAD.
3. Go to your AutoCAD directory (e.g. c:\acad)
4. Using text editor to edit ACAD.PGP file.
5. Inside ACAD.PGP file, you will see :
SHELL,,127000,*DOS COMMAND: ,0
Change 127000 to 131000.
6. Save ACAD.PGP file.
7. Go back your working directory, and try again.
* A copy of the edited ACAD.PGP file is located in System Disk 1, simply
copy/overwrite this file into your ACAD directory.
If you have any question, please call our local sales agent or
FAX your problem to our Hong Kong Customer Service Hotline:-
FAX No. : 887-3432 (office hours)
(Please don't forget to include your return phone so that your problem
can be answered)
日合AutoCAD中文Ver. 2.1更新說明
1. Ver. 2.0在R12上使用,編輯的字串無法抄入中文視窗中.
2. Ver. 2.1更正上述錯誤.
3. Ver. 2.1更新檔案:
SUNNEX.EXE --- 執行檔更新
SUNNEXH.EXE --- 執行檔更新
CE.LSP --- 執行檔更新
SUNNEX.KEY --- 暫存檔取消
SUNNEX.K00 --- 暫存檔增加
SUNNEX.K01 --- 暫存檔增加
4. Ver.2.1和Ver.2.0其使用與安裝方法相同.
README.DOC for AutoCAD Release 11 (386)
October 17, 1990 17:25
CONTENTS
General notes ....................................... 2
Plot spooling ....................................... 2
Networking notes .................................... 4
International character (8-bit font) support ........ 5
Manual corrections
AutoCAD Reference Manual ........................ 9
AutoCAD 386 Installation and Performance Guide .. 14
AutoLISP Programmer's Reference ................. 16
ADS Programmer's Reference ...................... 16
AutoCAD Tutorial ................................ 18
Also see the separate Advanced Modeling Extension documentation
update, README.AME
The AME option is not available for the SHOW version of AutoCAD.
AC11386RD-1 Page 1 of 18
General notes
-------------
- Release 11 adds the following device support to AutoCAD 386:
- Summagraphics Microgrid digitizer
- Interrupt-driven choice for Summagraphics Microgrid and MM series
digitizers (offering greatly enhanced digitizer performance)
- IBM 8514/A display (integrated driver)
- COMPAQ Portable III plasma display (integrated driver)
- JDL printer plotter model 750
- Canon Laser Beam printer models LBP-8 and LBP-8II
- Enhanced CalComp plotter driver (now sends "beginning of plot" and
"end of plot" records). This driver should now work with CalComp's
electrostatic plotters.
- AutoCAD 386 now writes prompts and progress messages to the screen much
faster than previous releases. Plot to file and Hide are faster as a
result of this improvement.
- A utility program is provided to allow large programs to be run using
AutoCAD 386's Shell. SHROOM.COM and its documentation file SHROOM.DOC
are supplied in the SAMPLE directory.
Plot spooling
-------------
- The ACADPLCMD and ACADPPCMD environment variable hooks for Plot Spooling
have been enabled for all platforms except the DEC VAXstation.
When plotting to a file named "AUTOSPOOL", AutoCAD generates a unique
file name in the configured plot file directory. Then, if the ACADPLCMD
(for Plot) or ACADPPCMD (for Prplot) environment variable exists, it
composes an operating system command using the string defined by that
variable (substituting the plot file name for the first occurrence of
"%s" in the string), and submits the command to the operating system.
The spooler program (supplied by the operating system or a third-party
application vendor) is typically responsible for the following actions,
although it may do other things as well.
- plotting the file as a background task. A simple case would use
the DOS PRINT utility, but this only works for ASCII plot files.
(PRINT must be loaded as a TSR before running AutoCAD, and must be
directed to the parallel port to which the plotter is attached.)
AC11386RD-1 Page 2 of 18
PRINT doesn't support XON/XOFF protocol, so serial ports can't be
used unless the plotter is wired for hardware handshaking.)
- deleting the file upon completion to make way for more plot files.
Those are the typical requirements, although the actual functionality is
not monitored by AutoCAD in any way.
To use a plot spooler with AutoCAD:
A. Configure AutoCAD to use either an internal driver or a P386 ADI
driver that uses AutoCAD's plotter I/O support (see the supporting
documents for your driver). The spooling mechanism is activated
only if the plot is written to a file, so if you want to use
spooling by default, configure the plotter for plot to file.
(Real-mode ADI drivers have their own method for writing plots to a
file, and cannot use AutoCAD's plot spooling facility. See page 53
of the AutoCAD 386 Installation and Performance Guide.)
B. The configured plot spooler directory must exist, and both AutoCAD
and the spooler program need read/write access to it. When
configuring, include the trailing directory delimiter character for
the system, such as "\" for DOS.
C. Configure the default plot file name as "AUTOSPOOL", or enter
"AUTOSPOOL" as the file at plot time.
D. Set the environment variable "ACADPLCMD" to a DOS command string
that invokes the plot spooler, with "%s" where the plot file name
should get filled in.
E. If the operation of the plot spooler command depends on a TSR having
been installed, the TSR must be installed BEFORE you start AutoCAD.
Loading a TSR via execution of ACADPLCMD at plot time (or via the
Shell command) is likely to be fatal to both the TSR and AutoCAD, if
the TSR trashes any of the DOS Extender's interrupt vectors.
For example, if plots are to be processed by a SPOOLPL program on DOS,
the definition of ACADPLCMD might be:
SET ACADPLCMD=SPOOLPL %s
assuming that a plot spooler program named SPOOLPL is present on the
search path and accepts the plot file name as a parameter.
The mechanism is the same for the Prplot command, except the ACADPPCMD
environment variable is used.
NOTE: Placing the definition in AUTOEXEC.BAT is advisable if you intend
to use plot spooling frequently. However, in DOS batch (.BAT)
files, "%" is used to reference parameters. If you set ACADPLCMD
or ACADPPCMD using a .BAT file, remember to use two "%" signs in
a row, as in:
SET ACADPLCMD=PRINT %%s
AC11386RD-1 Page 3 of 18
Networking notes
----------------
AutoCAD Release 11 is designed to operate on a wide variety of networks.
Although several popular networks have been tested, no particular vendors
have been designated as "supported". A few problem areas have been
identified:
- Directory permissions for the 386|VMM swap file location must allow file
creation and read/write operations to occur. If the swap file cannot be
created, 386|VMM prints a message stating "Error creating swap file" and
AutoCAD exits.
- If you plan to execute AutoCAD while your current directory is one that
resides on a remote node, performance will be substantially better if
AutoCAD 386 is configured to place its VMM|386 swap file on a local disk
drive using the "-swapdir" switch documented on pages 76 and 170 of the
AutoCAD 386 Installation and Performance Guide (I&PG).
Furthermore, placing the swap directory on local storage is a workaround
for an apparent problem on Novell Netware 386, where running with a
current directory residing on a remote node often causes AutoCAD to exit
immediately after being called from the DOS command prompt.
- If you plan to run AutoCAD frequently from a drive mounted on a remote
node, you should also consider setting the "-nopgexp" switch to reduce
network traffic when paging program code. This switch is documented on
pages 43 and 169 of the AutoCAD 386 I&PG.
- AutoCAD's file locking, and AutoCAD itself, will not run properly on
Novell Netware 286 if read-only directories are used. There is no known
fix at this time.
- Novell NetWare 386 3.1 allows programs to open read-only files in
read-write mode if you have "READ ONLY COMPATIBILITY = On" in your
SHELL.CFG file, but reports an error when you try to write to the file.
In general, we recommend that you do not turn on this mode. However, if
this mode is required by another software application that you use, you
will need to obtain the "FIXOPEN" NLM patch available from Novell, or
AutoCAD will not function properly when editing read-only files.
- SunOS 4.0 lacks the DOS file sharing support required for proper
operation of AutoCAD on PC-NFS networks. Operation of AutoCAD in this
environment can result in bad data transfers. You can work around the
problem by using the /SHARE option on the NET USE command when mounting
any network drives used to store drawing files. (See your PC-NFS manual
for further information on the /SHARE option.) SunOS 4.0.1 and later
releases fix the problem.
- On 3Com networks, library/support files such as ACAD.DWG, ACAD.MNX, and
TXT.SHX must be read-only in order to be shared by multiple users. This
is also true of any other files to be shared on 3Com networks. In
particular, the ACAD.PWD login file shared by users must be read-only.
However, the copy of ACAD.PWD in the server's temporary files directory
must be read-write-createable, as this file keeps track of the number of
users currently using AutoCAD.
AC11386RD-1 Page 4 of 18
- AutoCAD holds the ACAD.MNX compiled menu file and any running or paused
script file open while you're in the drawing editor. Thus, if you've
loaded the DOS SHARE utility and you use Shell to run a DOS command such
as COPY or DEL on any of these open files, you'll receive a Sharing
violation and be given an opportunity to abort the command.
International character (8-bit font) support
--------------------------------------------
The International versions of AutoCAD 386 Release 11 support 8-bit ASCII
text characters for the benefit of languages that require them (provided
that the host system, the supplied shape files, and the display drivers
support them as well). 8-bit ASCII support means that 8-bit ASCII text
characters can be displayed in AUI and on the text screen, as well as in
Text, Attribute, and Dimension entity strings. There are no commands
specific to using 8-bit ASCII text; when an International version is
installed and configured with the proper display driver, more characters
become available.
The domestic (North American) version of AutoCAD 386 continues to support
only 7-bit fonts for AUI and text-screen characters. (AUI dialogue boxes
use character number 128 as the "check" mark.) If a text character with a
value greater than 128 is output to the display driver (in text mode or
through the AUI menus, dialog boxes, command line, etc), it is replaced
with a "?" character. However, entity text strings can contain 8-bit
characters (shape numbers 32 through 255).
The following is a fairly complete technical description of AutoCAD's
8-bit ASCII support. Drawings created with 8-bit and 7-bit versions of
AutoCAD are compatible with both versions of AutoCAD, with exceptions
noted in a later section.
I. The features of the 8-bit ASCII (International) version of AutoCAD are
listed here. Behavior of the 7-bit version for the same circumstances
is also listed when appropriate.
1. Built-in display drivers
In the 7-bit version of AutoCAD, built-in display drivers treat
character code 128 as the AUI "check" mark, and display "?" when
sent ASCII codes greater than 128.
In the 8-bit version of AutoCAD, built-in display drivers treat
character code 255 as the AUI "check" mark, and can display ASCII
codes greater than 127 for AUI text (such as dialogue boxes), the
command line, menus, and the text screen. The text "glyphs" are
obtained from the active DOS code page, as described in DOS
reference manuals.
NOTE: The Swedish version of AutoCAD is 8-bit, but may use yet
another value for the check mark, as both 128 and 255 are
used for ordinary characters by some Swedish platforms.
AC11386RD-1 Page 5 of 18
2. ADI display drivers
ADI 4.1 protected- and real-mode display drivers now perform
additional communication with AutoCAD to determine:
- whether they are talking to a 7-bit or 8-bit version of AutoCAD,
and:
- If an 8-bit version of AutoCAD is in use, which character code is
used for the AUI "check" mark.
ADI 4.1 display drivers also tell AutoCAD whether they support
8-bit characters. The 7-bit version of AutoCAD assumes that the
driver operates in 7-bit mode. 8-bit versions of AutoCAD can work
with either 7-bit or 8-bit drivers, but a 7-bit driver forces an
8-bit AutoCAD to operate in 7-bit mode. All display drivers
written for ADI 4.0 and earlier operate in 7-bit mode. See the ADI
4.1 Driver Development Kit manual for more information.
3. Special codes for dimensioning symbols
The 8-bit and 7-bit versions of AutoCAD use different integer codes
for the characters representing the three special dimensioning
symbols. The table below shows the names of these symbols, their
generic text control sequences, and their version-dependent integer
values.
Symbol Control 7-Bit 8-Bit
Name Sequence Value Value
--------------- -------- ----- -----
Degrees %%d 127 248
Plus-Minus %%p 128 241
Circle Diameter %%c 129 237
Although it is possible to use the integer values for these symbols
directly in a text control sequence (as in %%127), or to enter them
using the ALT key (as in ALT + 1-2-7), these approaches don't
account for the differing values in the 7-bit and 8-bit versions of
AutoCAD. Therefore, we recommend against using them if you want
your special symbols to be compatible with both 7-bit and 8-bit
versions of AutoCAD.
4. AutoCAD dimension strings
In previous versions of AutoCAD, the dimensioning commands used the
control sequences "%%127", "%%128" and "%%129" to generate the above
special symbols. In both the 7-bit and 8-bit versions of Release
11, these commands now use the "%%d", "%%p" and "%%c" sequences.
Thus, drawings created in one version can be loaded and displayed
without error in the other version.
AC11386RD-1 Page 6 of 18
5. Automatic conversion of Dimension entity strings in older drawings
When a pre-Release-11 drawing is loaded into Release 11's drawing
editor (from the Main Menu, or via an Insert, Xref, or Dxfin
command), its Dimensions may have text strings containing "%%127",
"%%128", and "%%129" control sequences for the three special
dimensioning symbols. If any are found, they are translated
automatically to "%%d", "%%p", and "%%c", respectively. Once you
End, Save, or Wblock the drawing, the new control sequences will be
permanently stored. This conversion is not performed on Release 11
drawings.
6. Automatic symbol mapping
When an 8-bit AutoCAD loads a font file and determines that it has
no entry for code 248, 241, or 237 (but that it does have an entry
for the corresponding 127, 128, or 129 code), the 127-129 shape
definitions are copied into their corresponding 8-bit codes. In
this manner, existing drawings and 7-bit font files can be used with
the 8-bit version of AutoCAD without difficulty.
7. Differing alphabetic character sets for different languages
Different sets of ASCII characters make up the alphabet in different
languages. However, to ensure that drawings will be compatible
across different language versions of AutoCAD, symbol table (e.g.,
layer, linetype, text style) entries must use a common subset of the
available characters. Currently, this subset is the upper-case
Roman letters "A" through "Z", the digits "0" through "9", and the
characters "$", "_" and "-".
8. Command option keyword abbreviations
The 8-bit ASCII versions of AutoCAD support abbreviations for
command option keywords that begin after the first letter of the
keyword, when the allowed abbreviation is represented by the first
contiguous string of capitalized alphabetic characters shown in the
prompt.
For example, the keyword "nanTUCKet" could be specified by the
string "TUCK".
The 7-bit ASCII version of AutoCAD continues to require
abbreviations of command option keywords to begin at the start of
the keyword. (Certain keywords, such as "eXit", are exceptions to
this rule. In the 8-bit ASCII versions, this is typical.)
II. Where 8-bit ASCII characters are defined
1. The DOS Code Page facility is used to change the "glyphs" of all
ASCII characters in text mode (and for AUI text on most display
drivers). Instructions for the use of Code Pages can be found in
the DOS Reference Manual.
AC11386RD-1 Page 7 of 18
2. The AutoCAD font files contain symbol definitions for the characters
in Text, Attribute, and Dimension entity text strings. Entries for
ASCII character codes 32 through 255 have always been supported, but
many of the font files shipped with AutoCAD have only their first
129 characters defined. There are exceptions, usually denoted by an
"8" at the end of their font name, such as ISO8.SHP/SHX. So, if you
intend to use a full 8-bit ASCII character set, you may have to
extend some of the font files yourself, or obtain 8-bit font files
from other sources. Defining the 8-bit characters is done in the
same manner as the existing 7-bit characters, and they can be added
to existing font files with no harm done.
III. Compatibility notes and exceptions
1. A drawing created in an 8-bit AutoCAD can be edited with a 7-bit
AutoCAD. However, if the drawing has the character code 128 in
entity text strings, AUI dialogue boxes that display the text (such
as for Ddatte or Ddedit) will display a "check" mark in place of the
desired character. (The AUI "check" mark is two character cells
wide, so it will obscure the following character as well.) This is
harmless, but looks ugly. Other ASCII codes greater than 128 are
replaced by "?" marks in AUI text strings; this is also harmless.
2. KANJI (Japanese) AutoCAD uses 7-bit codes, but certain codes are
interpreted as the first byte of a two-byte (16-bit) KANJI code.
Therefore, KANJI AutoCAD drawings will not display correctly on
8-bit ASCII AutoCAD, because all characters will be interpreted as
8-bit ASCII characters.
Conversely, 8-bit ASCII strings can be confused for KANJI 16-bit
characters in a 7-bit AutoCAD, although this is far less likely,
since the code must be defined in a BIGFONT shape file, etc.
3. Drawings that reference font files containing definitions for
character codes 248, 241, and 237, when loaded into 8-bit AutoCAD,
will use those codes for the degree, plus/minus, and diameter
symbols when the AutoCAD dimensioning commands or other commands
enter the "%%d", "%%p", and "%%c" control sequences into drawing
entity text strings.
4. The text control sequences "%%127", "%%128", and "%%129" are
converted to "%%d", "%%p", and "%%c" if found within Dimension
entities in a pre-Release-11 drawing. Only Dimension entities are
converted, however. Therefore, if such a drawing is loaded into an
8-bit AutoCAD, any non-Dimension entities containing these control
sequences may no longer display the desired symbols. There should
be no problem in the 7-bit version of AutoCAD, however.
5. At this writing, it is not clear that all languages can be
restricted to use of upper-case Roman letters for symbol table
entries, and thus be compatible with each other.
AC11386RD-1 Page 8 of 18
AutoCAD Reference Manual corrections
------------------------------------
Chapter 2
- "Entity Selection". In the description of the "Previous" option on page
62, the last sentence in the Note should read:
AutoCAD remembers the space (model or paper) in which each
selection-set is obtained; the "previous" selection-set is also
cleared if you switch spaces and attempt to use it in the other
space.
Chapter 4
- "Text Command", pages 129-134. The description of the new text
alignment modes is incorrect, and should be changed as follows:
Page 129. The last paragraph should read:
You can align text using any combination of
top/middle/baseline/bottom and left/center/right alignment modes.
Baseline refers to the line along which the bases of the capital
letters lie. If you imagine a box surrounding the text, then
letters with descenders (such as p, g, and y) dip below the
baseline to the bottom of the box, and capital letters reach the
top of the box. The middle position is halfway between the
baseline and the top. The following figure shows the text
alignment positions.
Page 130. The "middle" indicator in the figure should be halfway
between the baseline and the top.
Page 134, "Text M - Fully Centered Text". The Note at the top of the
page should read:
The difference between this option and MCenter is that rather than
using the halfway point between the baseline and the top, Middle
uses the midpoint of an imaginary box surrounding the text string.
Therefore, its effect differs depending on whether the text string
has descenders or any characters that reach the top.
Page 134. In Table 4-2, the notation "(same as M)" should be removed
from the MC entry.
Chapter 5
- "Entity Selection". In the third paragraph on page 146, it should be
noted that UCSes whose extrusion directions are directly opposite each
other are not considered "parallel".
AC11386RD-1 Page 9 of 18
- "Filleting Two Straight Lines", page 172. The first paragraph's second
sentence is incorrect and should read:
It then trims the lines (retaining the "picked" segments if they
cross) and creates a fillet arc with the current fillet radius.
- "Undo - Notes and Interactions", page 201. The following should be added:
Undo does not undo changes made to the CVPORT system variable by the
SETVAR command (or the equivalent AutoLISP/ADS functions).
Chapter 7
- "Color Numbers", page 260. At the end of the fourth paragraph, "Mslide
command" should be replaced by "Vslide command".
- "Entity Handles", page 262. The following should be appended to the
first paragraph:
Entity handles are often, but not always, assigned sequentially.
- "Which Operations Change Handles?". The "Wblock *" command now retains
entity handles, so the last paragraph on page 263 should begin:
With the exception of "Wblock *", all forms ...
- "Ddlmodes Command". Append the following to the first paragraph on page
283:
(Hatch blocks, Dimensions, and Blocks whose entities use color "by
block" won't adapt to transparent color changes until the next
regen, although no alert will appear.)
Chapter 8
- "Axis Command", page 291. In addition to the restrictions noted in the
second paragraph, the Axis command works only when TILEMODE is on.
- "Object Snap Modes", page 307. Add the following to the description of
"Nearest" mode:
Use of this mode with Circles and Arcs requires that their extrusion
direction be parallel to the Z axis of the current UCS.
AC11386RD-1 Page 10 of 18
Chapter 9
- "Wblock Command". The "*" form of the Wblock command now retains entity
handles, as well as all named views, User Coordinate Systems, and
viewport configurations. The first paragraph on page 331 should now
read:
The entire drawing is written. This is similar to the Save command
("Save Command - Updating Without Exit" on page 68), except that
unreferenced symbols (Block Definitions, layers, linetypes, text
styles, and dimension styles) are not written. AutoCAD writes model
space entities to model space in the new drawing, and paper space
entities to paper space.
and the third paragraph on page 331 should now read:
With the exception of the "*" form of the command, Wblock sets the
output file's HANDLES system variable to 0 (disabled) and does not
write entity handles to the output file.
- "Using an Xref's Dependent Symbols", page 347. In the second paragraph,
replace "though any changes" with "but if the VISRETAIN system variable
is set to 0 (the default) any changes". Following the second paragraph,
add:
When VISRETAIN is set to 1, the current drawing's On/Off and
Freeze/Thaw settings for Xref-dependent layers take precedence.
They are saved with the drawing and are preserved during Xref reload
operations.
Color and linetype settings for Xref-dependent layers are not
affected by VISRETAIN, but are always reset upon reload of the Xref.
Chapter 10
- "Diameter Dimensioning", page 375. In the paragraph beginning "The
third style ...", the last two sentences are incorrect and should be
deleted.
Chapter 11
- "Variables and Expressions". Note #2 at the bottom of page 414 is
incorrect. TEXTEVAL does not affect the Dtext command.
Chapter 13
- New "Processing entity: nnn" messages may appear during plotting if many
entities have been processed without generating plot vectors. The new
message is simply meant to let you know that something's happening.
AC11386RD-1 Page 11 of 18
Appendix A
- "Standard Prototype Drawing", pages 446-447. The object selection
pickbox size is shown as being stored in both the prototype drawing and
AutoCAD's configuration file. It is actually stored in the
configuration file only.
- "Modify Pull-down Menu", page 451. The "Mirror" description incorrectly
states that Auto selection mode is used.
- "Options Pull-down Menu", page 453. The "Donut Diameters" description
should read:
Invokes the Donut command, allowing you to set the inside and
outside diameters.
- "System Variables", pages 467-475. Two new system variables should be
added to Table A-1.
DIASTAT (integer, not saved)
Dialogue box exit status. If 0, the most recent dialogue box
was exited via "CANCEL". If 1, exit was via "OK". (read-only)
VISRETAIN (integer, saved with drawing)
If set to 0 (the default value), On/Off and Freeze/Thaw settings
for Xref-dependent layers are reset to their state in the
referenced drawing upon each reload. When set to 1, the current
drawing's settings are preserved.
Appendix B
- "Extended and Expanded Memory Usage", page 481. This section applies
only to the 640K DOS version of AutoCAD. Use of expanded memory with
AutoCAD 386 requires a memory manager that conforms to the VCPI
interface standard. See the AutoCAD 386 I&PG for further information.
- "Menu Bar and Pull-down Menus". Two changes should be made to page 489.
The following should be appended to the second paragraph:
If the titles won't all fit in the menu bar, AutoCAD truncates
characters one by one from the longest title (checking each time to
see which is now longest), until they all fit. This can result in
some silly-looking titles, so you should attempt to fit everything
in 80 columns if possible.
and the last paragraph should be changed to read:
Each pull-down menu ordinarily appears directly beneath its menu bar
title. However, the rightmost menus shift to the left to
accommodate long menu items. The maximum number of items in a
pull-down menu is governed by the display device, and may be as low
as 21; be sure to consider this when designing custom menus.
AC11386RD-1 Page 12 of 18
- "Extended big-font", page 512. The first two lines of the bigfont
format description should be replaced by:
*0, 5, font name
character height, character depth, modes, character width, 0
- "Command Aliases and Abbreviations", page 523. The following note
should be added at the bottom of the page:
Aliases cannot be used in a command script. Use of aliases in menu
files is not recommended.
Appendix C
- "HEADER Section", page 536. $VISRETAIN should be added to the list of
DXF header variables (type 70; 1 = retain Xref-dependent visibility
settings, 0 = don't retain).
- "TABLES Section", page 537. Add the following to the DIMSTYLE group
code listing: 49 (dimgap), and 146 (dimtfac).
- "TABLES Section", page 538. Table C-3 (Group 70 bit codes for LAYER
table) is incorrect. It should read:
Flag bit
value Meaning
-------- --------------------------------------------------
0 Layer is On and Thawed.
1 Layer is Frozen.
2 If set, layer is frozen by default in new Viewports.
4 Unused
8 Unused
16 if set, layer is externally dependent.
32 if this bit and bit 16 are both set, this externally
dependent layer has been successfully resolved.
Xref-dependent layers are output during Dxfout. For such layers, the
associated linetype name in the DXF file is always CONTINUOUS.
- "Viewport", pages 546-547. In Table C-13, the first 1070 group should
be described as an integer whose value is 16 for Release 11. Also, the
description for the "1003..." entry near the end of the table should
read:
The names of layers that are frozen in this Viewport. This list may
include Xref-dependent layers. Any number of 1003 groups may appear
here.
- "DXB File Format". Byte code 255 should be removed from Table C-15 on
page 560. It is valid for Binary DXF, but not for DXB.
AC11386RD-1 Page 13 of 18
Appendix D
- "Command Differences". The following entries should be added to Table
D-3 on pages 571-572:
Dim Changes to the Radius and Diameter subcommands result in an
additional prompt in some situations. This may cause
failure of some old scripts and AutoLISP programs that
issue these commands.
Fillet When filleting two Lines that cross, AutoCAD now retains
the "picked" line segments. In previous versions, the
shorter ends were trimmed, no matter what points you used
to select the Lines.
Osnap Running object snap modes are now ignored during entity
selection.
and the following should be added to the "Wblock" entry on page 572:
The "*" form of the Wblock command now retains all entity
handles, named views, UCSes, and viewport configurations.
- "System Variable Differences". The following entries should be added to
Table D-4 on page 573.
CECOLOR In Release 10, this variable contained a string consisting
of "BYLAYER", "BYBLOCK", a color number (e.g., "15"), or a
standard color number and name (as in "1 (red)"). This
last form has been dropped, so applications will no longer
need special code to cope with its embedded blank. The
standard color numbers now appear simply as "1" - "7".
OSMODE Running object snap modes are now ignored during entity
selection.
AutoCAD 386 Installation and Performance Guide corrections
----------------------------------------------------------
- "AutoCAD 386 and Memory Managers", page 3. Add to this section:
"HIMEM.SYS does not conform to the VCPI specification, and is not
compatible with AutoCAD 386."
- "Essential Hardware and Software". In the second paragraph on page 8,
"8.7 megabytes" should be changed to "9 megabytes". Also, it should be
noted that additional free disk space is needed by AutoCAD 386's virtual
memory system, especially when editing large drawings.
- "1.2 Megabyte Release Format" and "720K Release Format", pages 13-18.
The acad.pwd login file is not supplied on the release disks; it is
created during initial configuration. Also, the ADS disk for AutoCAD
386 does not include a DDE directory.
- "Installation Steps", The second paragraph on page 24 (a bullet
concerning acadcfg.old) is incorrect and should be deleted.
AC11386RD-1 Page 14 of 18
- "Reconfiguring AutoCAD", page 27. Add the following:
Never swap ACAD.CFG configuration files (via a Shell or Files
command) while AutoCAD is running; doing so may cause unpredictable
behavior of AutoCAD.
- "The Acad.pwd File", page 42. The two paragraphs in this section are
incorrect and should be replaced by the following:
Acad.pwd is the "login file" that contains encrypted authorization
data essential to running AutoCAD on both stand-alone and networked
machines. AutoCAD creates the acad.pwd file during the server
authorization phase of the configuration process. If the file
becomes corrupted, AutoCAD forces a reconfiguration and rebuilds it.
- "The AutoCAD Shell Command". The following should be added after the
fourth paragraph on page 63:
A utility program called SHROOM.COM is provided to allow very large
programs to be run via AutoCAD 386's Shell. [ For details, see the
separate file SHROOM.DOC. SHROOM.COM and SHROOM.DOC are supplied in
the SAMPLE directory. ]
- "IBM Enhanced Graphics Display", page 92. Append the following to the
first paragraph:
EGA cards with less than 256K video memory are not supported. A
"semi" dual-screen mode occurs if you are using two video displays,
and the EGA is not the current display. In "semi" dual-screen mode,
AutoCAD uses the EGA to display the drawing, the status line, the
menus, the dialogue boxes, and the command prompts, and uses the
other display for the text screen. (In true dual-screen mode, the
other display is also used for the command prompts.)
- "Houston Instrument DMP Series", page 136. The number of pens supported
on the DMP-62MP plotter has been increased from 6 to 8.
- "PostScript Laser Printers", page 138. Replace the first paragraph with
the following:
AutoCAD 386 supports PostScript laser printers and plotters using
either a Centronics-type parallel I/O port or an RS-232C serial I/O
port. If a serial port is used, set the printer for 9600 baud, even
parity, 7 data bits, 1 stop bit, and XON/XOFF protocol (some have a
choice of XON/XOFF or DTR). See your hardware documentation for
specific installation instructions.
- "Noswfgrow1st Switch", page 170. The following should be added:
The longer you remain in AutoCAD, the larger the swap file will grow
(up to a point). If you often spend hours or days without exiting
AutoCAD, we suggest that you use the "-noswfgrow1st" switch so
you'll be less likely to run out of disk space during an editing
session.
- "Swap File Size", page 170. In the second paragraph, "-maxswfize"
should be "-maxswfsize".
AC11386RD-1 Page 15 of 18
AutoLISP Programmer's Reference corrections
-------------------------------------------
- "(fix)", page 42. If the result is outside the range of integers for
this implementation of AutoLISP, (fix) returns as a real. For instance,
if the implementation uses 16-bit integers,
(fix 32767.5) would return 32767
but
(fix 32768.5) would return 32768.0
- "(*error*)", page 76. The following should be added:
Your *error* function should NOT include any calls to (command).
- "Error Codes". The description of ERRNO code 52 on page 169 is
incorrect. It should be "Entity selection: null response".
ADS Programmer's Reference corrections
--------------------------------------
- "Common Characteristics of ADS Library Functions", page 8. Add the
following to the end of this section:
ADS user functions and data type definitions begin with the prefix
"ads_". Another prefix, "adsi_", is reserved for internal use.
- "Retrieving Extended Entity Data". At the bottom of page 78, "static
struc resbuf" should be "static struct resbuf" (add missing "t").
- "Entity Data Functions". In the example on page 71, the first argument to
ads_buildlist() should be RTDXF0 rather than 0.
- "ads_cmd", page 89. In the second paragraph, RTSTRING should be RTSTR.
- "ads_cmd" and "ads_command", pages 89-90. The following details should
be added to the descriptions:
- ADS programs can pause for user input by using ads_cmd() or
ads_command() to pass a string containing a single backslash. Since
the particular control string may change in the future, we suggest
that a preprocessor macro be used for this purpose. For example:
#define PAUSE "\\" /* a single backslash */
ads_command(RTSTR, "Zoom", RTSTR, PAUSE, RTNONE);
(In C, as in AutoLISP, two backslashes must be used to produce one
backslash in a string constant.)
- Certain AutoCAD commands (such as Trim, Extend, and Fillet) require
a "pick" point to be supplied along with the entity to be operated
upon. In order to supply such entity/point data pairs, an ADS
program must use the sequence:
AC11386RD-1 Page 16 of 18
RTLB, RTENAME, <entity>, RTPOINT, <point>, RTLE
or
RTLB, RTENAME, <entity>, RT3DPOINT, <point>, RTLE
with ads_command(). A similar chain of result buffers can also be built
using ads_buildlist()) and passed to ads_cmd(). The 2D or 3D "pick"
point must follow the entity name, and the pair must be surrounded by
RTLB/RTLE. For example, the following trims a line to a circle.
ads_point p1
ads_name first, last;
ads_command(RTSTR, "Circle", RTSTR, "5,5", RTSTR, "2", 0);
ads_command(RTSTR, "Line", RTSTR, "1,5", RTSTR, "8,5",
RTSTR, "", 0);
ads_entnext(NULL, first); /* Get circle */
ads_entlast(last); /* Get line */
p1[X] = 2.0; p1[Y] = 5.0; p1[Z] = 0.0; /* Set pick point */
ads_command(RTSTR, "Trim", RTENAME, first, RTSTR, "",
RTLB, RTENAME, last, RT3DPOINT, p1, RTLE,
RTSTR, "", 0);
- "The DOS Extender (AutoCAD 386) Environment", page 171. The supported
version of MetaWare High C 386 is 1.62 (for 32-bit systems). The Watcom
C 386 compiler is not yet supported. A Watcom environment will be
provided in a future update.
- "Avoiding Trouble", page 163. The following new topic should be added:
File Access Modes
For compatibility with the way AutoCAD and AutoLISP open files,
ADS programs should set the appropriate network file access modes
whenever opening files with the fopen() library function.
In MetaWare High C 386, this is done by #including <system.cf> and
setting a global variable just before calling the fopen() library
function. If you're opening a file for writing or appending, use:
Sharing_mode = Deny_read_write;
to prevent others from reading or writing the file while your
application is accessing it. To open a file for reading:
Sharing_mode = Deny_write;
allowing others to read the file, but not write to it. When
fopen() returns, reset Sharing_mode via:
Sharing_mode = Compatibility;
- "Symbolic Codes for On-Line Program Errors". The description of error
code OL_ENTSELNULL (value 52) on page 185 is incorrect. It should be
"Entity selection: null response".
AC11386RD-1 Page 17 of 18
AutoCAD Tutorial corrections
----------------------------
- "Creating Another Dimension Style", page 54. In the example, "dimclre"
should be "dimclrd" to change the dimension line color.
- "Plotting to Scale in Model Space Viewports", page 166. At the bottom
of the page, the ".25xp" example should read "1mm=4mm" rather than
"1mm=14mm".
- "Editing Viewports", page 170. The third paragraph should begin:
Since we no longer need the 2-foot line ...
- "Standardizing the Height of Dimension Text in Model Space", page 179.
The arithmetic should read:
.18 (size in model space drawing units)
X 1/180 (XP zoom scale factor)
--------
= .001 (size in plot units)
In the next large paragraph, "setting DIMSCALE to 96" should read
"setting DIMSCALE to 180".
- "Adding the Border and View Labels". On page 195, in the paragraph
below Figure 6-46, "8-by-10-inch border" should be "32-by-21-inch
border".
AC11386RD-1 Page 18 of 18
KEY386 is to be used for Cadkey-386 versions 3.50 through 5.00. The KEY386 program will only have to be run once. The program modifies the main Cadkey program file. You may run this program from any drive or directory, and need simply to type KEY386 at the DOS prompt. The program will ask for the complete path to the Cadkey program files. Typically you would type in C:\CADKEY if you accepted the installation defaults. If you placed your files on a different drive or directory, type in the correct path accordingly. The modification will take only seconds, and once modified, you will not have to run the program again.
MATHCAD VERSION 2.0 ON-LINE RELEASE NOTES
This file contains the most up-to-date product
information on this release of MathCAD, including
additions and corrections to the material in the MathCAD
User's Guide and printed release notes.
HOW TO CONTACT MATHSOFT INC.
If you require any assistance, please call MathSoft at
1-800-MATHCAD or (617) 577-1017. We would be pleased to help you
from 9:00 AM to 5:30 PM (Eastern Time), Monday through Friday.
We strongly encourage you to mail in your registration card.
Registered users receive the MathCAD User's Journal and the
MathCAD Applications and Games Disk. Registered users will also
receive information on future upgrades to MathCAD. Even if you
were already registered for MathCAD 1.1, please send in your
MathCAD 2.0 registration card.
If you think you have found a bug, please bring it to our
attention.
SEND US YOUR SUGGESTIONS
Help us plan for new features in future versions of MathCAD. We
appreciate your suggestions for new features, or for changes in
existing features.
MATHCAD DOCUMENTS
The MathCAD Auxiliary Disk contains many sample documents. You can
load these documents into MathCAD to see some ways to use MathCAD's
features.
See the file DIRECTRY.MCD for a list of these documents.
UNITS DOCUMENTS
The MathCAD Auxiliary Disk includes three files that contain unit
conversions.
CGS.MCD contains unit conversions in the cgs system, based on
centimeters, grams, and seconds. All units, including electrical
units, are defined in terms of these base units.
MKS.MCD contains unit conversions in the MKS system, based on
meters, kilograms, seconds, and coulombs.
USCUSTOM.MCD contains unit conversions based on the U.S. Customary
units of feet, pounds (mass), seconds, and coulombs.
You can add these conversions into files you create, or append
them to the end of your files using the MathCAD append
command.
PROGRAM NOTES
=============
REDISPLAY COMMAND
If you suspect that the MathCAD display screen is not accurately
reflecting the state of a document, or if equations on screen
have gaps or overlap one another, use the redisplay command by
pressing [Ctrl]R. This redisplays the whole screen.
Here are some actions that can cause the display to have gaps or
unreadable parts:
1. Regions that overlap one another on the screen.
2. Error messages from an equation or plot that coincide
on screen with other regions.
3. Cutting and pasting equations that overlap one another.
None of these problems can cause computational errors; they
affect the display only. When the information on the screen is
unclear, press [Ctrl]R to redisplay everything.
PRINTING DOCUMENTS
If your printer works with other programs but not with MathCAD,
MathCAD may be having difficulty communicating with your printer.
Check the following:
PARALLEL PRINTERS: Specify PRN or LPT1 as the printer device.
(Specify LPT2 if the printer is on the second parallel port.
SERIAL PRINTERS: First execute the following DOS commands:
MODE COM1: 9600,N,8,1,P (or other parameters as
appropriate for printer)
MODE LPT1:= COM1
Then, when MathCAD prompts for a printer device, specify PRN.
PLOTTERS: First execute the following DOS command:
MODE COM1: 9600,N,8,1,P (see your plotter manual to
make sure this is correct.)
Then, when MathCAD prompts for a printer device, specify COM1. DO
NOT use LPT1 or PRN, even if you have redirected them to COM1.
WHAT TO DO IF MATHCAD CANNOT PRINT
First, check that your printer is compatible with a model that
MathCAD supports. See the description of printing in the User's
Guide and the descriptions of each printer driver in the printed
Release Notes in the disk pocket of your package.
If MathCAD cannot print directly, try printing to a file as follows:
1. Print the document to a file. Type [Esc] print [Enter].
When MathCAD prompts you for a print area, press [Enter].
Then, in place of the printer device, specify a filename like
OUTPUT.PRN.
2. Save your document and exit MathCAD by pressing [Ctrl]Q.
3. At the DOS prompt, type:
COPY /B OUTPUT.PRN PRN
This sends the print file to the printer. Substitute the
filename you used in step 1 for OUTPUT.PRN and the name of
the port to which your printer is attached (for example,
LPT1 or COM1) for PRN.
REPLACE COMMAND
MathCAD will not always recalculate equations as necessary
after using the replace command ([Ctrl][F6]). After a replace
command, do a process command to ensure that the calculations in
the document are up to date.
AT & T 6300 SERIES COMPUTERS
To run in high-resolution mode (640x400 color or monochrome) on an
AT&T 6300 series computer, type:
MCAD /A
If you do not type /A, MathCAD runs in CGA-emulation mode (640x200
monochrome).
L/I/M EXPANDED MEMORY LIMITATION
In MathCAD 2.00, MathCAD uses at most 1 megabyte of available
expanded memory.
.MCD 30001 1 74
.CMD PLOTFORMAT
0 0 1 0 0
0 0 1 0 0
0 1 0 0 NO-TRACE-STRING
0 2 1 0 NO-TRACE-STRING
0 3 2 0 NO-TRACE-STRING
0 4 3 0 NO-TRACE-STRING
0 1 4 0 NO-TRACE-STRING
0 2 5 0 NO-TRACE-STRING
0 3 6 0 NO-TRACE-STRING
0 4 0 0 NO-TRACE-STRING
0 1 1 0 NO-TRACE-STRING
0 2 2 0 NO-TRACE-STRING
0 3 3 0 NO-TRACE-STRING
0 4 4 0 NO-TRACE-STRING
0 1 5 0 NO-TRACE-STRING
0 2 6 0 NO-TRACE-STRING
0 3 0 0 NO-TRACE-STRING
0 4 1 0 NO-TRACE-STRING
0 1 21 15
.CMD FORMAT rd=d ct=10 im=i et=3 zt=15 pr=3 mass length time charge
.CMD SET ORIGIN 0
.CMD SET TOL 0.001000000000000
.CMD SET PRNCOLWIDTH 8
.CMD SET PRNPRECISION 4
.CMD PRINT_SETUP 1.200000 0
.CMD DEFINE_FONTSTYLE_NAME fontID=0 name=Variables
.CMD DEFINE_FONTSTYLE_NAME fontID=1 name=Constants
.CMD DEFINE_FONTSTYLE_NAME fontID=2 name=Text
.CMD DEFINE_FONTSTYLE_NAME fontID=3 name=Greek^Variables
.CMD DEFINE_FONTSTYLE_NAME fontID=4 name=User^1
.CMD DEFINE_FONTSTYLE_NAME fontID=5 name=User^2
.CMD DEFINE_FONTSTYLE_NAME fontID=6 name=User^3
.CMD DEFINE_FONTSTYLE_NAME fontID=7 name=User^4
.CMD DEFINE_FONTSTYLE_NAME fontID=8 name=User^5
.CMD DEFINE_FONTSTYLE_NAME fontID=9 name=User^6
.CMD DEFINE_FONTSTYLE fontID=0 family=Tms^Rmn points=10 bold=0 italic=0 underline=0
.CMD DEFINE_FONTSTYLE fontID=1 family=Tms^Rmn points=10 bold=0 italic=0 underline=0
.CMD DEFINE_FONTSTYLE fontID=2 family=Helv points=10 bold=0 italic=0 underline=0
.CMD DEFINE_FONTSTYLE fontID=3 family=Symbol points=10 bold=0 italic=0 underline=0
.CMD DEFINE_FONTSTYLE fontID=4 family=Helv points=10 bold=0 italic=0 underline=0
.CMD DEFINE_FONTSTYLE fontID=5 family=Courier points=10 bold=0 italic=0 underline=0
.CMD DEFINE_FONTSTYLE fontID=6 family=System points=10 bold=0 italic=0 underline=0
.CMD DEFINE_FONTSTYLE fontID=7 family=Script points=10 bold=0 italic=0 underline=0
.CMD DEFINE_FONTSTYLE fontID=8 family=Terminal points=0 bold=0 italic=0 underline=0
.CMD DEFINE_FONTSTYLE fontID=9 family=Modern points=10 bold=0 italic=0 underline=0
.CMD UNITS U=1
.EQN 2 2 0 0
{ 67 417 0 0}{59}BM8 v ( í C |7 Ç Ç ÇÇ Ç Ç Ç ÇÇ ÇÇÇ └└└ ≡ ≡ ≡ ≡ ∙ÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖƒ ≡ ∙ÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖƒ ≡ ∙ÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖƒ ≡ ∙ÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖƒ ≡ ∙ÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖƒ ≡ ∙ÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖƒ ≡ ∙ ≡Ç Çêêêêê≈ ∙Öƒ ≡ ∙ ≡Çêêêê ≈ ∙Öƒ ≡ ∙ °êê êêÅp ∙Öƒ ≡ ∙ ° êêê p ∙Öƒ ≡ ∙ ≡êêê www ∙Öƒ ≤ 0 ∙ ≡êê www w ∙Öƒ ≡ ∙ www wp ∙Öƒ ≥ ∙ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ www wwwp ∙Öƒ ⌠U@ ∙ ≡ ≡ ≡ ≡ ≡ ≡≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡w www w ∙Öƒ ■²ô ∙ ≡ ≡ ≡ ≡ ≡≡≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡wwww ≡w ∙Öƒ ≡ ∙ ≡≡≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ww p ∙Öƒ ≈733 ∙ ≡≡≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ p ≡ p ∙Öƒ ≥ ∙ ≡ ≡ ≡ ≡ ≡≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡p wwp ∙Öƒ ≡Ö ä ∙ ≡ ≡ ≡ ≡ ≡≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡w≡ wwwp ∙Öƒ ⌡Q · ∙ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ wwwp ∙Öƒ ≡Mr ∙ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ wwwp ∙Öƒ ±PYf ∙ ≡ ≡wp ≡ ∙Öƒ ÷Si ∙ ≡ ≡ ∙Öƒ °Φÿ┐ ∙ ≡ ≡ ≡≡ ∙Öƒ ·¬╚ ∙ ≡ ≡≡ ∙Öƒ °j⌐ ∙ ≡ ≡≡ ∙Öƒ ±▒ú▄ ∙ ≡ ≡ ≡ ∙Öƒ ≡ó( ∙ ≡ ≡ ∙Öƒ ⁿ╠x╤ ∙ ≡ ≡ ≡≡ ≡ ≡≡ ∙Öƒ ≤Qô₧ ∙ ≡ ≡ ≡ ≡≡ ∙Öƒ °HPU ∙ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ∙Öƒ ∙─⌐6 ∙ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ∙Öƒ Öï° ∙ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ∙Öƒ ≥ R' ∙ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ∙Öƒ ≥éK┤ ∙ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ∙Öƒ √∙╜┌ ∙ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ∙Öƒ ∙ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ∙Öƒ ∙ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ∙Öƒ ∙ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ∙Öƒ ε ∙ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ∙Öƒ ∙ ≡ ≡ ∙Öƒ ∙ ≡ ≡ ∙Öƒ ∙ ≡ ≡ ≡ ≡ ∙Öƒ ∙ ≡ ≡ ≡ ≡ ∙Öƒ ∙ ∙Öƒ ∙ ∙Öƒ ∙ ∙Öƒ ≈ ∙ ∙Öƒ ∙ ∙Öƒ ∙ ∙Öƒ ∙ ∙Öƒ ∙ ∙Öƒ ∙ ∙Öƒ ∙ÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖƒ √╗ ∙ÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖƒ ²▀▌▌ ∩∩≡ O ⌡
.TXT 12 1 0 0
C a439,439,1378
{\rtf1\ansi \deff0
{\fonttbl
{\f0\fnil Helv;}
{\f1\fnil Courier;}
}
{\plain {This file contains up-to-date information
on the latest release of Mathcad's Mechanical
Engineering I Applications Pack, including
additions and corrections to the documentation.\par
\par }{\f0 \fs20 \b \i0 \ulnone SYSTEM REQUIREMENTS}{\par
}{To use the documents in this Applications
Pack you must have Mathcad Version 3.0
and Microsoft WIndows 3.0 or later. }{\par
\par }{\f0 \fs20 \b \i0 \ulnone USING THE
APPLICATIONS}{\par }{To load an application
file from the Applications Diskette, first
load Mathcad from your Mathcad System Diskette
or hard disk. Then insert the Applications
Diskette in drive A and choose }{\f0 \fs16
\b \i0 \ulnone Open Document}{ from the
}{\f0 \fs16 \b \i0 \ulnone File}{ menu.
In the text box of the Open Document dialog
box, type A: followed by the name of the
file you are loading. Once the file has
loaded, choose }{\f0 \fs16 \b \i0 \ulnone
Calculate Document}{ from the }{\f0 \fs16
\b \i0 \ulnone Math}{ menu to calculate
results for the sample application.\par
\par }{\f0 \fs20 \b \i0 \ulnone HELP}{\par
}{If you encounter difficulty in loading
or running the applications on this diskette,
call Technical Support at MathSoft between
9:00 }{\f0 \fs16 \b0 \i0 \ulnone AM}{ and
5:30 }{\f0 \fs16 \b0 \i0 \ulnone PM}{ Eastern
time. The number is 1-800-}{\f0 \fs16 \b0
\i0 \ulnone MATHSOFT}{. Inside Massachusetts
or outside the }{\f0 \fs16 \b0 \i0 \ulnone
USA}{, call 1-617-577-1017.}{ \par }{\par
}{ }}
}
All of the libraries on these two disks are ARCed to save space.
On Library Disk 1 is the program ARCE.COM which is used to uncompress
the files. To use ARCE:
ARCE <arc file> <which file> /R<enter>
where: <arc file> the .ARC file name (such as LIBRARY1)
<which file> name of file to unarchive (such as *.* or RF.LIB)
/R replaces the file, no prompting
example: make your current directory be your LIBRARY directory
type: A:ARCE A:LIBRARY1 *.* /R<enter>
or
make your current directory be a floppy disk (B:)
type: COPY A:ARCE.COM ARCE.COM<enter>
put the LIBRARY 2 disk into A:
type: ARCE A:LIBRARY2 VSTGATES.LIB<enter>
The contents of each ARC file are:
LIBRARY1.ARC SIZE
======================
ANALOG.LIB 22805
ASSEMBLY.LIB 18538
BIT.LIB 12846
CMOS.LIB 29718
DEVICE.LIB 72884
ECL.LIB 30005
INTEL.LIB 23827
LADDER.LIB 23696
MEMORY.LIB 20401
METER.LIB 16719
MOTO.LIB 17745
OPTOISOL.LIB 55362
POWER.LIB 38123
PSPICE.LIB 8009
RF.LIB 24656
SHAPES.LIB 32805
SPICE.LIB 4642
TILSI.LIB 13621
TTL.LIB 75943
ZILOG.LIB 2862
LIBRARY2.ARC SIZE
======================
ALTERA_M.LIB 26239
ALTERA_P.LIB 39895
INTEL_M.LIB 31383
INTEL_P.LIB 39910
PLDGATES.LIB 15706
VSTGATES.LIB 83115
VSTOTHER.LIB 3428
VSTRAM.LIB 8386
The installation program used to install OrCAD EDA Tools, INSTALL, is licensed software provided by Knowledge Dynamics Corporation, Highway Contract 4 Box 185-H, Canyon Lake, Texas 78133-3508 (USA), 1-512-964-3994. INSTALL is Copyright (c) 1987-1989 by Knowledge Dynamics Corporation which reserves all copyright protection worldwide. INSTALL is provided to you for the exclusive purpose of installing OrCAD EDA Tools.
The installation program used to install OrCAD EDA Tools, INSTALL, is licensed software provided by Knowledge Dynamics Corporation, Highway Contract 4 Box 185-H, Canyon Lake, Texas 78133-3508 (USA), 1-512-964-3994. INSTALL is Copyright (c) 1987-1989 by Knowledge Dynamics Corporation which reserves all copyright protection worldwide. INSTALL is provided to you for the exclusive purpose of installing OrCAD EDA Tools.
The installation program used to install OrCAD EDA Tools, INSTALL, is licensed software provided by Knowledge Dynamics Corporation, Highway Contract 4 Box 185-H, Canyon Lake, Texas 78133-3508 (USA), 1-512-964-3994. INSTALL is Copyright (c) 1987-1989 by Knowledge Dynamics Corporation which reserves all copyright protection worldwide. INSTALL is provided to you for the exclusive purpose of installing OrCAD EDA Tools.
1.0) Introduction
This file describes the enhancements and changes included in
the 5.0 release of PSpice.
For information regarding installation, operation,
and technical details about the package, you may purchase the
Circuit Analysis User's Guide for $50.00.
2.0) Updates and Corrections to the User's Guide
All manual modifications for this version have been marked by shading
those items.
Note: Release 5.0 of Probe, Parts, and StmEd (DOS and
DOS/16M) supports display modes VGA800 and VGA1024 on
Super VGA adapters that use one of the following chipsets:
ATI Technologies 28800
Chips & Technologies 82C451, 82C452, or 82C453
Video7/Headland Technologies HT208 or HT209
Trident TVGA8900
Tseng Labs ET4000
Western Digital WD90C00
In addition, the VESA (Video Electronics Standards
Association) standard BIOS interface for 800x600 and
1024x768 16-color modes is supported (DOS 640Kb version
only). If your adapter manufacturer also supports this
standard, a VESA BIOS extension will have been included
in the software utilities provided with your video adapter.
This will be either an installable device driver (called
VESA.SYS or something similar) or a Terminate-and-Stay-
Resident program (called VESA.COM, VESA.EXE, or something
similar). To use the VESA interface, you must install the
VESA BIOS extension prior to running Probe, Parts, or StmEd.
DIGITAL SIMULATION
The Multi-Bit Digital-to-Analog Converter switching time
model parameter default values have been modified. The
default value for TSWMN, TSWTY, and TSWMX is now 10ns
instead of 0.
Ten new one-shots have been added to the digital library: the
121, 122, and 123 TTL-7400 series parts, and the CD4098B and
CD4538B. The TTL-7400 series parts are included in the pin
list at the end of the Digital Simulation chapter of the
User's Guide, and the pin list for both the CD4098B and
CD4538B is Reset, TR_POS, TR_NEG, Q, and QBAR.
SUN (NETWORK LICENSE VERSION)
If the -q switch is used and if all copies of the program are
checked out, you are placed in a queue waiting for the next
available license.
DOS/16M (Extended-DOS VERSION)
The description on page 17 of the Circuit Analysis User's
Guide, section 2.1.1.6.5 Virtual Memory, is misleading. The
DOS16VM environment variable specifies the TOTAL size of
virtual memory, NOT the size of the swap file. Any difference
between the value set by DOS16VM and memory actually available
is made up for by the swap file. For example, if you set
DOS16VM=4000 and your PC has 3Mb of extended memory, then a
swap file of about 1Mb will be created for the duration of
the simulation, etc.
Also, you may use the suffix "M" with the DOS16VM value to
denote megabytes (1Mb = 1024Kb).
3.0) Program modifications since version 4.05.
PSPICE
1. The Probe data file name no longer defaults to PROBE.DAT.
When a PSpice simulation successfully completes and there
is a .PROBE statement in the circuit file, a Probe data
file will be generated and will have the same name as
the circuit file with a .DAT extension. For example, if
you ran PSpice with EXAMPLE1.CIR, your Probe data file
will be named EXAMPLE1.DAT. You may also override the
default data file name by listing it as the third
argument in your PSpice command statement.
This file name is stored in the file PROBEDAT.NAM.
Therefore, if Probe is executed without a data file name,
Probe will read the file name from PROBEDAT.NAM.
2. There are two new model parameters for the GaAsFET model:
VDELTA (capacitance transition voltage) and VMAX
(capacitance limiting voltage).
3. There is one new model parameter for the Inductor Coupling
(Transformer Core) model: Gamma. A, C, K, and alpha also
have some description modifications.
4. There are two new parameters for the .OPTIONS statement:
DIGMNTYSCALE and DIGTYMXSCALE.
5. Current mode Pulse-Width Modulator (PWM) models (in
SWIT_REG.LIB) are available and require both the Analog
Behavioral Modeling and Digital Simulation options.
6. Unijunction Transistor (UJT) models (in THYRISTR.LIB) are
available and require the Analog Behavioral Modeling option.
Analog
Behavioral
Modeling 1. The capability to simulate Chebyshev filters has been added
to Analog Behavioral Modeling. This allows the user to
implement a Chebyshev filter based in terms of a set of
frequency characteristics.
PROBE
1. If Probe is executed without specifying a data file name,
it will read the file name from the file PROBEDAT.NAM. If
PROBEDAT.NAM does not exist, Probe will look for PROBE.DAT,
and then PROBE.TXT. If neither PROBE.DAT or PROBE.TXT
exists, then Probe will prompt the user for the data file
name.
2. Six new display device drivers have been added: GenericVGA,
IBMVGAMono, NECHiClrMou, NECNrmMono, VGA800, and VGA1024.
3. Two new printer drivers have been added: HP_GL2-PCL and
HPLJE.
4. The capability to label the coordinates of a cursor has
been added as an option on the Cursor Menu.
5. There is now the capability of having multiple y axes. The
menu options are part of the Y Axis Menu.
6. The Performance Analysis feature containing the Goal
Functions has been added to the X Axis Menu.
Performance_analysis allows adding traces that show how a
derived value changes during multiple PSpice runs. The
derived value is extracted from one or more PSpice waveforms
by using search commands, marking points, and evaluating
expressions of marked points. For example, you could create
a plot that shows propagation delay as a function of
temperature, or pulse-width as a function of some component
value, or frequency of the output as a function of a stepped
parameter.
7. For EGA, VGA, and Super VGA displays, the colors for traces,
cursors, background, foreground, etc., can now be defined by
the user from within Probe from the Analog Plot Menu.
DIGITAL SIMULATION
1. There are 8 new parameters for the UIO model: TSWLH1,
TSWLH2, TSWLH3, TSWLH4, TSWHL1, TSWHL2, TSWHL3, and
TSWHL4.
2. There are now two types of stimulus devices: the stimulus
generator (STIM) which uses simple commands to generate a
wide variety of waveforms; and the new file stimulus
(FSTIM), which obtains the waveforms from an external file.
4) Install program for PSpice
The installation program used to install PSpice, INSTALL, is
licensed software provided by Knowledge Dynamics
Corporation, P.O. Box 1558, Canyon Lake, Texas 78130-1558
(USA). INSTALL is Copyright (c) 1987-1991 by Knowledge
Dynamics Corporation which reserves all copyright protection
worldwide. INSTALL is provided to you for the exclusive
purpose of installing PSpice. MicroSim Corporation is
exclusively responsible for the support of PSpice, including
support during the installation phase. In no event will
Knowledge Dynamics Corporation be able to provide any
technical support for PSpice.
1.0) Introduction
This file describes the enhancements and changes included in
the 5.0 release of PSpice.
2.0) Updates and Corrections to the User's Guide
All manual modifications for this version have been marked by shading
those items.
Note: Release 5.0 of Probe, Parts, and StmEd (DOS and
DOS/16M) supports display modes VGA800 and VGA1024 on
Super VGA adapters that use one of the following chipsets:
ATI Technologies 28800
Chips & Technologies 82C451, 82C452, or 82C453
Video7/Headland Technologies HT208 or HT209
Trident TVGA8900
Tseng Labs ET4000
Western Digital WD90C00
In addition, the VESA (Video Electronics Standards
Association) standard BIOS interface for 800x600 and
1024x768 16-color modes is supported (DOS 640Kb version
only). If your adapter manufacturer also supports this
standard, a VESA BIOS extension will have been included
in the software utilities provided with your video adapter.
This will be either an installable device driver (called
VESA.SYS or something similar) or a Terminate-and-Stay-
Resident program (called VESA.COM, VESA.EXE, or something
similar). To use the VESA interface, you must install the
VESA BIOS extension prior to running Probe, Parts, or StmEd.
DIGITAL SIMULATION
The Multi-Bit Digital-to-Analog Converter switching time
model parameter default values have been modified. The
default value for TSWMN, TSWTY, and TSWMX is now 10ns
instead of 0.
Ten new one-shots have been added to the digital library: the
121, 122, and 123 TTL-7400 series parts, and the CD4098B and
CD4538B. The TTL-7400 series parts are included in the pin
list at the end of the Digital Simulation chapter of the
User's Guide, and the pin list for both the CD4098B and
CD4538B is Reset, TR_POS, TR_NEG, Q, and QBAR.
SUN (NETWORK LICENSE VERSION)
If the -q switch is used and if all copies of the program are
checked out, you are placed in a queue waiting for the next
available license.
DOS/16M (Extended-DOS VERSION)
The description on page 17 of the Circuit Analysis User's
Guide, section 2.1.1.6.5 Virtual Memory, is misleading. The
DOS16VM environment variable specifies the TOTAL size of
virtual memory, NOT the size of the swap file. Any difference
between the value set by DOS16VM and memory actually available
is made up for by the swap file. For example, if you set
DOS16VM=4000 and your PC has 3Mb of extended memory, then a
swap file of about 1Mb will be created for the duration of
the simulation, etc.
Also, you may use the suffix "M" with the DOS16VM value to
denote megabytes (1Mb = 1024Kb).
3.0) Program modifications since version 4.05.
PSPICE
1. The Probe data file name no longer defaults to PROBE.DAT.
When a PSpice simulation successfully completes and there
is a .PROBE statement in the circuit file, a Probe data
file will be generated and will have the same name as
the circuit file with a .DAT extension. For example, if
you ran PSpice with EXAMPLE1.CIR, your Probe data file
will be named EXAMPLE1.DAT. You may also override the
default data file name by listing it as the third
argument in your PSpice command statement.
This file name is stored in the file PROBEDAT.NAM.
Therefore, if Probe is executed without a data file name,
Probe will read the file name from PROBEDAT.NAM.
2. There are two new model parameters for the GaAsFET model:
VDELTA (capacitance transition voltage) and VMAX
(capacitance limiting voltage).
3. There is one new model parameter for the Inductor Coupling
(Transformer Core) model: Gamma. A, C, K, and alpha also
have some description modifications.
4. There are two new parameters for the .OPTIONS statement:
DIGMNTYSCALE and DIGTYMXSCALE.
5. Current mode Pulse-Width Modulator (PWM) models (in
SWIT_REG.LIB) are available and require both the Analog
Behavioral Modeling and Digital Simulation options.
6. Unijunction Transistor (UJT) models (in THYRISTR.LIB) are
available and require the Analog Behavioral Modeling option.
Analog
Behavioral
Modeling 1. The capability to simulate Chebyshev filters has been added
to Analog Behavioral Modeling. This allows the user to
implement a Chebyshev filter based in terms of a set of
frequency characteristics.
PROBE
1. If Probe is executed without specifying a data file name,
it will read the file name from the file PROBEDAT.NAM. If
PROBEDAT.NAM does not exist, Probe will look for PROBE.DAT,
and then PROBE.TXT. If neither PROBE.DAT or PROBE.TXT
exists, then Probe will prompt the user for the data file
name.
2. Six new display device drivers have been added: GenericVGA,
IBMVGAMono, NECHiClrMou, NECNrmMono, VGA800, and VGA1024.
3. Two new printer drivers have been added: HP_GL2-PCL and
HPLJE.
4. The capability to label the coordinates of a cursor has
been added as an option on the Cursor Menu.
5. There is now the capability of having multiple y axes. The
menu options are part of the Y Axis Menu.
6. The Performance Analysis feature containing the Goal
Functions has been added to the X Axis Menu.
Performance_analysis allows adding traces that show how a
derived value changes during multiple PSpice runs. The
derived value is extracted from one or more PSpice waveforms
by using search commands, marking points, and evaluating
expressions of marked points. For example, you could create
a plot that shows propagation delay as a function of
temperature, or pulse-width as a function of some component
value, or frequency of the output as a function of a stepped
parameter.
7. For EGA, VGA, and Super VGA displays, the colors for traces,
cursors, background, foreground, etc., can now be defined by
the user from within Probe from the Analog Plot Menu.
DIGITAL SIMULATION
1. There are 8 new parameters for the UIO model: TSWLH1,
TSWLH2, TSWLH3, TSWLH4, TSWHL1, TSWHL2, TSWHL3, and
TSWHL4.
2. There are now two types of stimulus devices: the stimulus
generator (STIM) which uses simple commands to generate a
wide variety of waveforms; and the new file stimulus
(FSTIM), which obtains the waveforms from an external file.
親愛的讀者，感謝您對本書 "PADS-2000 入門與實例應用" 一書的愛護。
在本書的磁片當中有下列檔案，有的是筆者自製的應用程式。有的則是
本書中的製作範例。
\PADS\ ┬── APTER.EXE
├── FILES\ ─── TRAN.EXE
│ PADS.PRO
│ PROTEL.EXE
│ PLCC2.EXE
│ 實習工作檔 *.JOB
└── LIB\ ──── KAWA.PT
KAWA.LN
KAWA.PD
KAWA.LD
\ORCAD\ ┬───────── GO.BAT
├─ SHEET\ ──── KEY.SCH
│ LAMP.SCH
│ ROLLER.SCH
└─ LIB\ ──── KAWA.LIB
其中的 TRAN.EXE、PADS.PRO、PROTEL.EXE、以及 PLCC2.EXE 分別為
應用程式，而在 \PADS\FILES 之下的其他其他 JOB 檔則為本書當中的各
個實習範例。
在 PADS\LIB 之下的四個 KAWA.* 檔案，為本書當中所製作出來的
零件庫之內容。讀者可以在 SetUp 的 LibPath 功能之下將這個零件
區併入系統之中°
除此之外，OrCAD 的電路圖轉換也是本書以及本磁片製作的重點之一。
所以在此將各個書中所用的 OrCAD 電路圖皆放在 \ORCAD\SHEET 子目錄之下。
如果當您在 OrCAD 之下將此無法將本此片當中的各個 .SCH 檔叫出來使用的話。
一是可能您的 OrCAD 版本太過老舊；二可能是 OrCAD 找不到零件。此時
請將 KAWA.LIB 併入您的 OrCAD 系統之中。
THE DESIGN CENTER 5.1
1.0) Introduction
This file describes the new features and changes for the 5.1
release of the Design Center programs: PSpice, Probe,
Stimulus Editor, and Parts. The platforms covered in this
file include: non-windows IBM-PC and NEC-PC with DOS/16M,
Windows 3.0 IBM-PC and NEC-PC, Macintosh, Sun, DECstation,
and VAX/VMS. Most of the material in this file will direct
you to the location in the analysis manuals where detailed
information on each subject can be found.
The analysis documentation referenced in this README.DOC
consists of the following manuals:
"Analysis System Setup Manual"
"Analysis User's Guide"
"Analysis Reference Manual"
2.0) PSpice
2.1) DOS Only / Install Program for PSpice
The installation program used to install PSpice, INSTALL, is
licensed software provided by Knowledge Dynamics Corporation,
P.O. Box 1558, Canyon Lake, Texas 78130-1558 (USA). INSTALL
is Copyright (c) 1987-1992 by Knowledge Dynamics Corporation
which reserves all copyright protection worldwide. INSTALL
is provided to you for the exclusive purpose of installing
PSpice. MicroSim Corporation is exclusively responsible for
the support of PSpice, including support during the
installation phase. In no event will Knowledge Dynamics
Corporation be able to provide any technical support for
PSpice.
2.2) Table 4 on page 52 of the Analysis Reference Manual
lists two new intrinsic functions for PSpice expressions.
Please refer to the manual for detailed information regarding
the results of each expression.
The new functions are:
TABLE(x,x1,y1,x2,y2,...xn,yn)
LIMIT(x,min,max)
2.3) To link the DOS/16M version, you must use the Microsoft
segment-executable linker that comes with the Microsoft C
compiler. To link the DOS version, we recommend that you
use the Plink86plus linker (version 2.24) from Intersolve.
For more information contact:
Life Boat Distribution Services
1163 Shrewsbury Avenue
Shrewsbury, New Jersey 07702
(800) 445-7899
2.4) Fourier Analysis (.FOUR command)
The .FOUR command for Fourier analysis now allows an
argument to specify the number of harmonics you wish
to have calculated.
The general format is:
.FOUR <frequency value> [no. harmonics value] <output variable>*
For example:
.FOUR 60Hz 20 V(17)
If the number of harmonics is not specified, the DC
component, fundamental, and 2nd through 9th harmonics
are calculated by default.
Refer to Chapter Three, page 62 of the Analysis Reference
Manual for information on the .FOUR command.
2.5) Lossy Transmission Line Model
A Lossy Transmission Line model has been implemented in
version 5.1. Using the distributed model approach rather
than the the traditional lumped model approach allows you
to simulate lossy lines in a significantly reduced amount
of time.
The general format is:
T<name> <A port (+) node> <A port (-) node>
+ <B port (+) node> <B port (-) node>
+ LEN=<value> R=<value> L=<value>
+ G=<value> C=<value>
For examples refer to Chapter Four, page 127 "Transmission
Line" (T device), of the Analysis Reference Manual.
2.6) Device Libraries
2.6.1) Digital Library Additions
The new library files added to the Digital Library are:
dig_pal.lib - Programmable Array Logic devices
Note: PAL20RA10 is listed in the library list,
but is not currently available in this library.
dig_gal.lib - Generic Array Logic devices
dig_ecl.lib - Emitter Coupled Logic 10K and 100K devices
Note: 100181 is listed in the library list, but is not
currently available in this library.
The devices and their pin lists are provided in tables in the
Analysis Reference Manual. These tables can be found at the
end of Chapter Five on pages 288-292.
2.6.2) Analog Library Additions
The following libraries have been added to the 5.1 version
of PSpice:
europe.lib - European-manufactured semiconductor devices
harris.lib - RCA/GE/Harris power-transistor devices
swit_rav.lib - Averaging power supply devices
Note: The Average Power Supply Model VMSSDCM is listed in
the library list, but is not currently available in this
library.
2.6.2.1) EUROPE.LIB
Some of the devices in EUROPE.LIB and their counterparts in
the regular libraries (eg. DIODE.LIB) have identical names.
In order for PSpice to find the correct model/subcircuit
definition, you must ensure that the appropriate library is
specified first in NOM.LIB.
If EUROPE.LIB is specified before another model library
containing duplicate names, none of the duplicate devices
in the second library will be accessed. Therefore, if
D1N4148 and D1N4149 exist in both EUROPE.LIB and DIODE.LIB,
PSpice would take both the D1N4148 and D1N4149 definitions
from EUROPE.LIB which is listed before DIODE.LIB in NOM.LIB.
To avoid this from happening you can extract the specific
devices from the desired libraries and put them into a library
that is listed before any other library containing the device
with the duplicate name.
If you are using Schematics, the order of symbol libraries
specified in the [SCHEMATICS LIBS] section of msim.ini should
reflect the order of model libraries specified in NOM.LIB.
2.7) Inertial and Transport Delay
PSpice uses two different types of internal delay functions when
simulating the digital portion of the circuit: "inertial delay"
and "transport delay". The application of these concepts is
embodied within the implementation of the digital primitives
within PSpice. Therefore, they are not user-selectable.
To obtain detailed information on Inertial and Transport Delay,
please refer to the Analysis Reference Manual, Chapter Four,
Section 4.8.4.4 (pages 100-101).
2.8) Digital Worst-case Timing Simulation
With "digital worst-case timing simulation" (new for the
5.1 release), you will be able to use PSpice to evaluate
the timing behavior of your digital and mixed analog/digital
designs using a full range of component propagation delay
tolerances. In Chapter Five of the Analysis User's Guide
you will find information on digital worst-case timing
simulation, starting with Section 5.5
on page 135. The remaining sections and their subjects are:
5.5.1 Simulator Representation of Timing Ambiguity
5.5.2 Simulator Propagation of Timing Ambiguity
5.5.3 Identification of Timing Hazards
5.5.3.1 Convergence Hazard
5.5.3.2 Critical Hazard
5.5.3.3 Cumulative Ambiguity Hazard
5.5.3.4 Reconvergence Hazard
5.5.4 Glitch Suppression Due to Inertial Delay
5.5.5 Methodology
2.9) PSpice as a Native Windows 3.0 Program on the IBM-PC and NEC-PC
The general operating instructions for Windows PSpice as a
native Windows 3.0 program can be found in Chapter Two,
Section 2.3.1.2, (pages 16-20) of the Analysis Reference Manual.
Windows PSpice will run on any IBM 386 or 486 based PC, IBM-PC
compatible computers, or NEC-PC running the Design Center
package with schematic capture. This program requires a
minimum of one megabyte of memory available in the Windows
environment, plus the amount needed to run your particular
circuit files.
2.9.1) Windows PSpice Menus
To assist you in navigating through the Windows PSpice menus
here is a list of the new menus and the commands within each.
(a) HELP MENU
About PSpice...
(b) FILE MENU
Open
Terminate Simulation
Save Window Configuration
Exit to Windows
(c) FONT MENU
System
ANSI Fixed
ANSI Variable
OEM
Other Fonts...
(d) COLOR MENU
Text Color
Background Color
Error Text Color
Error Background Color
(e) DISPLAY MENU
Immediate
Fast
Slow
3.0) Probe
3.1) Analog and Digital Plots
For the 5.0 and earlier releases of Probe, you could have
0, 1, or more analog plots, and 0 or 1 digital plots.
For the 5.1 release of Probe, you can have 0, 1, or several
plots. Each plot can be analog only, digital only, or both
analog and digital. When a plot is both analog and digital,
the analog traces are displayed in the bottom part of the
plot with a dashed border, and the digital traces are
displayed in the top part of the plot with a solid border.
When you start Probe with a .dat file that has both analog and
digital data, an empty analog plot is shown. After adding
traces, the plot will have both analog and digital parts if
both analog and digital traces have been displayed.
Digital plot size is now specified as a percentage of the
overall plot size. In Probe 5.0, there was only one digital
plot and the digital plot size was specified as the number of
digital traces the digital plot could display.
3.2) Menus
The menus have been modified to improve the command flow for
displaying both analog and digital waveforms on the same plot.
The Analog Plot Menu and the Digital Plot Menu are now combined.
This new menu structure includes the digital_Trace_commands
which allow the user to move, insert, change, and scroll
digital traces.
3.3) Remove_trace
Changes have been made to allow one or more traces to be
selected for removal, before actually removing the traces
(and doing the sometimes time consuming redraw of the
display).
The traces to be removed may be selected by using either the
mouse or the arrow keys and space bar. Selected traces are
marked with a '<' to the right of the trace name
e.g. V(4)< ).
Using the mouse:
Clicking on the trace name the first time selects
the trace.
Clicking on the trace again deselects it.
Using the arrow keys and space bar:
When select is chosen, the first trace is
highlighted. The right and left arrows will
move the highlight to other trace names.
The space bar selects/deselects the trace.
Also, an Undelete command has been added. It will redisplay
the last trace(s) deleted since entering the Remove_trace menu.
Undelete only appears in the menu if traces have been deleted
since entering the Remove_trace menu.
NOTE: because of these changes, Probe command files created by
Probe 5.0 or earlier, will no longer work for deleting traces.
3.4) Add Trace
Add_trace now allows you to specify analog traces, digital
traces, or both at the same time. You cannot create an
expression that combines analog and digital nodes to create
one trace.
Digital expressions have been added, and the syntax for
specifying a bus has changed.
A digital signal can be any digital node in the data file or
a boolean expression involving digital nodes. Please see
page 312 of the Analysis Reference Manual for information
on digital signals and digital expressions.
3.5) Goal function search commands:
Limited expressions have been added for LEVEL(val),
and XVALUE(val).
In 5.0, val could be:
a floating number (e.g., 1e5, 100n, 1, ...)
a percent (eg 50%)
a marked point (e.g., x1, y1, ...)
In 5.1, val can also be:
a db value relative to max or min
max-3db or -3db => 3db below maximum range
min+3db or 3db => 3db above minimum range
a value relative to max or min
max-3 => maximum range - 3
min+3 => minimum range + 3
a relative db value
.-3db => 3db below lastvalue
.+3db => 3db above lastvalue
a relative value
.-3 => lastvalue - 3
.+3 => lastvalue + 3
where lastvalue is the x or y value found by the last search
command. For the first search command, lastvalue is the
starting point for the first search command.
Refer to page 320 of the Analysis Reference Manual for
more information on Search_commands.
3.6) Probe as a Native Windows 3.0 Program on the IBM-PC and NEC-PC
Probe running as a Windows 3.0 application, is only available
in the Design Center package with schematic capture. Windows
Probe provides similar functionality included in non-windows
Probe, implemented by utilizing pull-down menus and dialog
boxes.
To help you locate Probe functions, the following Windows
Probe main menus and their command items are provided. For
details on the command defintions see Chapter Six, Section
6.3.2.1 (page 342) of the Analysis Reference Manual.
FILE MENU ANALYSIS MENU TRACE MENU
Load AC Add
Print DC Remove
Printer Setup Transient Macro
Log Commands Symbols
Run Commands Mark Data Points
Exit
About Probe
AXIS MENU ZOOM MENU CURSOR MENU
Set Range Display Pointer Display
Add Y Normal Peak
Delete Y In Trough
Color Out Slope
Title Area Min
Y Log Scale Max
X Log Scale Search Commands
X Variable Next Transition
Restrict Data Previous Transition
Fourier
Performance Analysis
DISPLAY MENU
Digital Plot Size
Save/Restore
Copy to Clipboard
Redraw
In general, all commands are available at all times, provided
that the command makes sense. For instance, Remove in the
trace menu is enabled only when there are traces to remove.
Some options, such as Fourier, are toggles which can be
either on or off. On is denoted by a check mark next to the
command, and off is denoted by the absence of the check mark.
Some commands require some prior action before they will work.
Trace Remove: You must first select the traces to remove.
This is done by pointing at the name of the trace in the
legend and clicking the left mouse button. You may
select multiple traces by holding down the shift key while
selecting the trace names.
Zoom commands: You must enable the zoom pointer before you
zoom in or out. You may move the zoom pointer with the
mouse by clicking over a point of interest. Zooming in
and out works by a factor of two around the zoom pointer.
If you "click and drag" (press and hold the mouse button,
move the mouse, release the button), you can define an
area to zoom into using the Zoom Area command. Zoom Normal
is always available.
Cursor commands: You must display the cursors before you can
use any cursor commands. If the command has implied
direction, such as Peak, then the direction moved is the
same as the last direction moved, or right if there was no
last direction. Likewise, the cursor moved will be the same
as the last cursor moved. Next Transition and Previous
Transition are not available in the beta version.
Features not available through the menus:
Digital Scrolling: To scroll the digital plot, use the mouse
to click on the "+" signs in the digital legend. They will
only appear if there are additional digital traces not
currently displayed.
Compatibility with non-windows Probe:
Log/Command Files: These are specific to the windows version.
Macro Files (.mac): Compatible
Display Files (.dsp): Compatible
Data Files (.dat): Compatible
Data Files (.txt): CSDF data files are not available in the
beta version.
Goal Function Files (.gf): Compatible
4.0) Parts
If you are running on an NEC-PC or IBM-PC (or compatible)
then you will need 510 kilobytes of conventional memory free
to run Parts.
4.1) Non-linear Magnetic Core Model
A non-linear magnetic core model has been added and uses
a derivative of the Jiles-Atherton formulation to provide
a closed-form, analytic solution. For detailed information
please refer to Chapter Eight, page 414, of the Analysis
Reference Manual.
GST DesignWorks v1.20
=====================
To install the program, select Run... from the File menu in the
Windows program manager, then type:
A:INSTALL
and press OK. You will then have a dialog asking you in which
directory you want to install the program. The installation program
will create a group called 'GST' containing the program, and a
further README file.
You will need about 7 megabytes of free space on your hard disk for
a complete installation, but the install program does allow you to
omit some or all of the fonts or clipart. The minimum installation
needs under 2 megabytes.