Legacy ConstructiVision v3.60 Installer and Payload

This page summarizes what the ConstructiVision setup media tree suggests about the installer and the v3.60 payload.

Note

Some details may be incomplete or inaccurate because this analysis is inferred from filenames and common AutoCAD extension patterns. Where the legacy readme or installer script is explicit, that information is preferred.

1) Root media indicates a classic InstallShield installer

The presence of Setup.exe, SETUP.INI, setup.ins, CABs (data1.cab, _sys1.cab, _user1.cab), and supporting InstallShield artifacts indicates an older InstallShield-style Windows setup that unpacks components, performs configuration, and registers uninstall metadata.

2) v3.60 payload is a hybrid: AutoLISP/DCL tooling plus compiled modules

From the v3.60\ directory listing, most of the visible payload consists of:

  • Many .lsp files â-’ AutoLISP code (commands, drawing automation, data parsing)

  • Many .dcl files â-’ Dialog Control Language UI definitions (classic AutoCAD dialogs)

  • Several .scr files â-’ AutoCAD scripts (batch command sequences)

  • Classic menu artifacts (.mnu/.mnc/.mnr/.mns) â-’ legacy AutoCAD menu system

  • A compiled module present in the tree: Csv.VLX

Clarification from readme + installer script:

  • The legacy readme states the main program is:

    • Csv.arx for AutoCAD R14, or

    • Csv.vlx for AutoCAD 2000

  • It also lists compiled subprograms Pcms.arx and Pcms2.arx, and a registration manager Wincss.exe.

  • The installer script references csv.arx, pcms.arx, pcms2.arx, and csv.vlx.

This implies key compiled binaries may be delivered via CAB payloads (not necessarily visible in a flat extracted folder view), while the LSP/DCL/menu content forms the scripting/UI layer around those binaries.

3) Naming suggests a tilt-up workflow suite, not one-off macros

Even without reading the source, filenames cluster into recognizable tilt-up / concrete detailing domains.

A) Panel lifecycle + tilt-up commands

Likely âoespineâ modules include:

  • tiltup.lsp

  • panel.lsp, makepan.lsp, drawpan.lsp, finpan.lsp, renpan.lsp, Inspanel.lsp, panatt.lsp

  • opening.lsp (openings are a major panel-detail domain)

  • centgrav.lsp (center of gravity matters for lifting/picking)

  • pick.lsp and the pp* family (ppauto.lsp, ppcent.lsp, pp_dlg.*) â” likely pick-point tooling

  • brace.lsp and the bp* family (bpauto.lsp, basedim.lsp, bp_dlg.*) â” likely brace-point / brace-plan tooling

B) Concrete + connection-ish elements

  • dowels.lsp

  • bolt.lsp

  • weld.lsp, weldconn.lsp

C) Building elements / supports

  • footing.lsp

  • slab_dlg.*

  • wall_dlg.*, column.lsp

4) ThereâTMs a full project + revision + QA layer

The file set includes strong signals of production workflow management:

  • Project/variables: project.*, setvars.lsp, invar.*, updvar.lsp

  • Feature gating: feature.lsp, enable.lsp, fenable.lsp, pdisable.lsp

  • Revisions: revision.*, donerev.lsp

  • QA checks: dbchk.lsp, dirchk.lsp, chrchk.lsp, rangchck.lsp, plus centralized err.lsp / warning.*

5) The UI is dialog-driven and modular

The pervasive *_dlg.dcl + *_dlg.lsp pairing suggests the tool is operated through a suite of dialogs, with LSP handling callbacks, validation, and drawing generation.

6) Batch / plotting automation likely exists

Indicators include:

  • btch.lsp + btch_dlg.*

  • plt.lsp

  • viewpt.dcl

  • SHOW.LSP + scripts (SHOW.SCR, showstart.scr, etc.)

7) CSV export/import is a real subsystem

The CSV cluster (CSV.lsp, menu artifacts, and compiled modules) suggests data exchange used for schedules/takeoffs (panel lists, embed lists, brace/pick data, revision logs).

8) Limits of inference from a tree alone

The tree does not reveal exact command names, licensing enforcement details, or full binary inventory. For that, we need either:

  • the CAB contents/file manifests, and/or

  • the core entry-point LSP that loads the compiled modules (often csv.mnu macros or a startup LSP), plus registration manager components (Wincss.exe, registry payloads).

See also

  • installshield-cab-hdr-inventory

See also

  • installshield-stub-and-support-files