Macsyma 421 on Lisp machines

Scope and evidence classes

This dossier distinguishes four kinds of evidence:

• Public source evidence covers the MIT System 46 editor integration and contemporary descriptions, later LM-3 bug and patch records, and an older public DOE Macsyma Lisp-Machine supervisor retained by the Maxima project.
• Licensed media observation covers the exact Macsyma 421 system declaration, component inventory, compiled user-interface metadata, patch directory, and Help-topic structure. No licensed implementation or Help text is reproduced here.
• Interpretation connects those implementation surfaces into a workflow. Interpretations are labelled where the exact visible effect has not been run.
• Runtime observation covers only the clean Open Genera 2.0 / Genera 8.5 world. It proves that this particular base world lacks the product; it does not test an installed Macsyma 421 system.

“Complete” in the command tables means every Macsyma-specific top-level and nested menu entry recovered from the exact 421 compiled media, plus every Macsyma-specific editor gesture found in the audited manual and compiled modules. It does not mean every inherited Genera command, every mathematical function among the 2,510 Help topics, every site extension, or an effective keymap reconstructed from a product which has not been loaded.

Release and artifact boundary

The inspected local release directory identifies Macsyma as released system 421 and latest system 421, written for Open Genera 2.0 / Genera 8.5 on 6 August 1998. Its component declaration describes experimental Macsyma 421.0 one day earlier. The patch directory reaches released patch 421.45, while one source- world header records Macsyma 421.43. These are related but different version layers: system version, patch version, and the version loaded in the world which wrote a file.

The tree contains 211 versioned compiled modules, one Lisp system declaration, one manual database, and the three system/component/patch directory records. The copyright notices identify proprietary Macsyma, Inc. material with portions originating at MIT. The directory, decoded Help, compiled modules, and raw runtime captures remain untracked. This page records facts and checksums, not recovered proprietary code or documentation.

Lineage: MIT Macsyma, CADR, LM-3, and Symbolics

Macsyma began as an MIT Project MAC symbolic-manipulation system. Richard Fateman's first-person retrospective describes its Algol-like user language, Pratt-style extensible parser, multiple mathematical representations, exact arithmetic, two-dimensional display, and the 1982 code release which became the common ancestor of the DOE and Symbolics lines. That paper is a historical and technical witness, not a description of every Symbolics 421 interface.

The Lisp-Machine port existed well before the 1998 media inspected here:

• MIT System 46 lmdoc/paper.105 says most of Macsyma had been ported and compiled for the Lisp Machine and that most facilities worked, while noting remaining exceptions. That is contemporary port status, not a product inventory.
• lmdoc/kbdpro.3 documents the Macsyma use of Control-] for a progress or elapsed-time report.
• nzwei/modes.49 supplies a Macsyma editing mode. Its presence proves editor integration, not the contents of a load band.
• LM-3 zwei/bugs.bugs and zwei/bug.zwei refer to experimental Macsyma versions in actual Lisp-Machine worlds. patch/system-99.patch-directory likewise records a source world containing Experimental Macsyma 6. Those records establish product presence in the lineage even though the maintained public System 303 source tree omits the product implementation.
• The public Maxima archive retains an older archive/src/lmsup.lisp supervisor which creates a Macsyma listener and registers it on the System and Select keys. It is valuable corroboration of the MIT/DOE interface lineage, but it is not source for Symbolics Macsyma 421. In particular, its Select-A binding must not be projected onto the later product without runtime evidence.

The practical conclusion is narrow: public CADR and LM-3 trees can document the integration points and historical presence, while the licensed Symbolics media documents the later product. They are not interchangeable source witnesses.

System architecture

The 421 declaration defines a patchable Macsyma system maintained by Macsyma, Inc. It has conditionals for Lisp Machines, CLOE, VAX/VMS, Unix/AKCL, the VLM, 36xx machines, and I-machines. The selected compiled suffix varies accordingly: .vbin for the VLM, .ibin for Ivory, and .bin on earlier Lisp Machines.

The declaration names 219 paths in total, including platform-only branches, autoloaded libraries, and commented or obsolete modules. The component directory's 167 inputs per target architecture are the authoritative installed core. Counting those installed inputs by directory gives:

This organization explains why “extracting the source from the world” is the wrong preservation model. Macsyma 421 is a loadable multi-file Genera system. Its distributed implementation is mostly compiled .vbin modules, and the world is only the live state into which they may be loaded. Compiled modules retain names, constants, calls, menus, dispatch tables, and other behaviorally meaningful structure, but not necessarily the original source syntax, comments, local names, macro forms, or file organization.

User language and listener workflow

Macsyma's top level combines a mathematical expression language with a live Lisp implementation beneath it. Input is not ordinary Common Lisp:

• a semicolon terminates an input and displays its result;
• a dollar sign terminates an input while suppressing result display;
• functions use mathematical call syntax such as factor(expression);
• assignment, lists, arrays, loops, conditionals, functions, rules, and option variables form a programmable user language;
• noun and verb forms distinguish an unevaluated operation from requesting its evaluation; and
• Lisp remains available for system extension and implementation work.

The parser and display share operator knowledge. A user-defined input operator can therefore participate in output notation as well as parsing. Internal mathematical objects are Lisp structures, but Macsyma maintains several specialized representations rather than forcing all calculations through one printed form: general expressions, rational/polynomial forms, Poisson series, Taylor series, matrices, exact integers and ratios, floating and big-float numbers, and noun forms can coexist.

Three asynchronous controls are documented for the Lisp-Machine session:

The exact disposition of partially computed state after each interrupt remains a runtime TODO for the installed 421 product.

The Genera frame

Compiled 421 metadata defines a MACSYMA-FRAME with a listener, a topic pane, a command-menu pane, and a separate plot pane/window. Mathematical input and output are presentation objects: the interface can associate a displayed subexpression or command name with the underlying Macsyma object and offer operations appropriate to it.

The topic pane has eight top-level categories:

For a topic, left selects it, middle sets related options, and right offers actions. For a command, left accepts its typed arguments; middle offers related commands or Describe; right opens an action menu which can prompt, describe, run an example, or show related commands. The product also has a keyboard menu style in which numbered items are selected with the number followed by ;.

PREFERRED_MENU_STYLE chooses mouse or keyboard menus. Mouse popups are the Symbolics implementation; the numbered keyboard form is the portable fallback. PREFERRED_GREETING_STYLE chooses a displayed, multi-font greeting or a plain printed form. These variables make the interface intentionally adaptable to workstations and terminal-like implementations.

Direct manipulation of mathematical output

Compiled gesture descriptions establish the following operations on selected displayed expressions or subexpressions:

The 421 code also contains a middle-click DLINE-IDENTITY operation on a display line. Its name suggests transferring or identifying a displayed result, but the exact visible effect is TODO until the product is run or the function is reconstructed at higher confidence. The product exposes facilities for users to add and remove Macsyma mouse commands, so this table describes the recovered core rather than a closed extension mechanism.

Mathematical capability map

The Help database is a command reference rather than a formal algorithmic specification. The following map combines the installed module families, menu surfaces, and topic summaries without promising that a particular problem is solvable or fast:

This breadth was one of Macsyma's defining achievements, but it also made global options and representation changes significant. A loaded package can alter syntax, simplification, or defaults. Reproducible historical experiments should therefore record the system and patch version, loaded files, option values, input, and whether results came from exact or approximate arithmetic.

Plotting and graphics

Macsyma 421 includes six installed plotting components plus Lisp-Machine graphics and plot-window integration. The recovered interface spans:

• ordinary 2-D function plots, parametric plots, adaptive plots, vector fields, implicit plots, graphs, and pole-zero style displays;
• 3-D surfaces, faces and data plots, contours, 3-D graphs, parametric and vector plots, and complex-function plotting;
• axes, scale, points, labels, line style, superposition, screen position, coordinate system, perspective, tessellation, and color settings;
• plot animation and a view-control dialog; and
• named plot lifecycle operations: save, load, kill, review, replot, and hardcopy.

PLOTMODE distinguishes display and Tektronix-oriented output in the documentation. The plot modules create a Lisp-Machine plot window and graphics stream rather than merely emitting a host image file. The exact appearance, default colors, menus, and hardcopy destinations in 421 are runtime TODOs.

Help and self-documentation

The local engineering-manual database is a line-oriented ASCII topic store in which & begins a topic. A structural scan found:

Summary topics cover algebra, arrays, calculus, files, floating-point numbers, geometry, integration, matrices, ordinary differential equations, plotting, quadrature, rules, statistics, strings, tensors, and trigonometry.

The main Help entry points are Primer, Describe, Usage, Example, Demo, and Apropos. A query ending with ? asks for command-line help. The compiled Lisp-Machine Help frame maintains an index, current/previous/next topics, contexts, hypertext links, and actions which launch examples or demonstrations. This is deeper integration than a flat manual viewer: Help records can lead back into executable product content.

The museum's Genera Help extractor may recover this database into ignored local output for analysis, but neither the decoded topics nor the proprietary source are committed. See On-line Help recovery for the reproducible local procedure and rights boundary.

Expression editors

Macsyma 421 contains three distinct editing routes: a linear MEDIT command, a structural Display Editor, and Zmacs buffer integration. They should not be collapsed into “the Macsyma editor.”

Files, batch work, translation, and debugging

Macsyma is both interactive and file-oriented:

• Load, Loadfile, Batch, and Batchload bring programs or command files into a session;
• Save and the obsolete-save conversion route preserve or migrate product data in product-defined formats;
• Writefile, Appendfile, Closefile, and Stringout record output;
• the file menu can merge names, search, probe, list, rename, and delete files;
• Playback revisits prior input;
• Trace, Dispfun, Fundef, and Untrace expose program structure and execution; and
• the translator and optimizer turn user-language programs or expressions into compiled Lisp-level behavior, with FORTRAN and general code-generation paths.

The Lisp substrate means ordinary Genera debugging and source tools can also be relevant after translation, but the exact handoff between a Macsyma-level error, the Macsyma break loop, and the Genera debugger must be observed in a loaded 421 session. See Tracing, stepping, breakpoints, and call analysis for the general Lisp-machine facilities.

Controlled Genera 8.5 observation

A fresh network-isolated session d42-macsyma-registration-20260718, generation 1, booted the exact museum base world on 18 July 2026. Read-only listener queries returned NIL for both MACSYMA and CLIMAX packages. An error-contained SCT:GET-SYSTEM-VERSION query for Macsyma returned NIL plus the suppressed condition, confirming that the clean world did not know the system.

No contributed module was loaded, no file service was exposed, and no Save World operation occurred. The action log contains 36 intent/outcome records and has SHA-256 31a5bd4e6287d1fd708ea4a8840a4db43fd31c05320c25a9ac8afa779edc9430. The base and private world both ended with SHA-256 a8ee5e86cc7e322f7385af3e0cd579d7650d4dcfc3ce328acbf8b25515dd0672. The VLM accepted its host shutdown confirmation and began cleanup, then hit the known bounded cleanup stall and was force-stopped. Unsaved Lisp state was discarded.

This observation establishes only absence from the base world. The purchased media's 421 component directory remains positive evidence that the product is available as an optional contributed system.

Screenshot decision

No screenshot is published for this dossier yet. The only runtime image reached was the ordinary Dynamic Lisp Listener showing the negative registration query; it does not show Macsyma and adds little visual evidence beyond the recorded result. Publishing it would not satisfy the repository's “representative visible state” goal.

TODO: stage the licensed Macsyma directory only inside a disposable ignored harness session, load the product through ordinary Genera system mechanisms without bypassing any product checks, exercise the listener, command/topic panes, Display Editor, Help frame, and representative plot, then review the smallest necessary images individually under the screenshot publication policy. Any accepted images should support analysis of interface behavior; they should not reproduce manual/Help pages, demos dominated by third-party artwork, or a decorative gallery.

Preservation implications

For meaningful preservation, retain these layers separately:

1. the licensed, unmodified 421 distribution and its system/component/patch records;
2. checksums and an evidence-only inventory which can be published safely;
3. inert tools for local compiled-object and Help analysis;
4. the Genera/VLM world and loader needed to run the product;
5. recorded loaded systems, patches, option values, and test inputs for every behavioral result; and
6. public lineage witnesses from MIT, LM-3, and DOE/Maxima without representing them as the exact Symbolics source.

Uncompiling .vbin modules can recover a behaviorally useful Lisp-like model: global definitions, constants, calls, control flow, dispatch tables, and UI data can often be reconstructed. It cannot promise the original source. The best museum description should therefore call such output reconstructed or decompiled behavior, cite the exact binary, and preserve uncertainty about lost names, macros, declarations, and comments.

Open questions

• TODO: load unmodified Macsyma 421 through supported Genera mechanisms and record the exact startup command, product checks, greeting, Select activity, frame layout, and patch version.
• TODO: run Display Editor's List Keys operation and publish the complete effective key table, distinguishing defaults, user bindings, and inherited editor operations.
• TODO: determine the exact visible behavior of middle-click DLINE-IDENTITY from runtime or high-confidence reconstruction.
• TODO: exercise one representative operation in each mathematical family and record defaults which materially affect the result; do not extrapolate algorithm coverage from one example.
• TODO: verify plot defaults, color use, view-control behavior, animation, and hardcopy destinations in the exact 421 environment.
• TODO: compare the public DOE Lisp-Machine implementation to 421 at the definition/algorithm level without copying proprietary code into the public tree.

Public sources and verification

• Richard J. Fateman, A Review of Macsyma, first written 1982–1984 and lightly revised in 2001; lineage, language, representation, display, and documentation context.
• V. Kajler and N. Soiffer, A Survey of User Interfaces for Computer Algebra Systems; historical context for the 1979 display editor and later Symbolics mouse/menu interface.
• MIT AI Laboratory, Getting Started Computing at the AI Lab, AI Working Paper 235; contemporary availability and port context.
• MIT CADR System 46, pinned public nzwei/modes.49, lmdoc/kbdpro.3, and lmdoc/paper.105, commit 8e978d7d1704096a63edd4386a3b8326a2e584af.
• Maintained LM-3 System 303, zwei/modes.lisp, zwei/bugs.bugs, zwei/bug.zwei, and patch/system-99.patch-directory, check-in 4df393c68d7f083ce42d5c377039d26043cc18a9031ace28258dc97f4137eb91.
• Maxima public source archive, archive/src/lmsup.lisp, commit 663177dac0d6d093e1b4f947fba4c81c34104f1b; local file 19,544 bytes, SHA-256 b104d42a0ba82a50ac8400520a262d4dbe0a3ae87449d79e70772ae6b4717323.

Public links and changing repositories last verified 2026-07-18. Licensed media observations were performed locally on the same date and are not redistribution links.