v3.60 install â-’ hot patch (overlay newer files)

Note: This is written for AutoCAD 2000 with ConstructiVision v3.60 installer media, where the newer build you want to run is still intended for AutoCAD 2000 (same major platform). If the newer build targets a different AutoCAD major version, stop and use a separate path.

What âoehot patchingâ means here

Hot patching is:

  1. Install v3.60 normally (so you get all installer-created pieces: folders, menu wiring, support paths, registry keys, shortcuts).

  2. Copy a newer ConstructiVision payload over the installed v3.60 files (with backups), so runtime code/data comes from the newer build while the âoeinstalled footprintâ remains v3.60.

This often works well for legacy AutoCAD toolchains because the installer mainly sets up:

  • search paths and menus,

  • a predictable folder layout,

  • optional registry/profile settings, while most âoereal behaviorâ lives in LSP/DCL/SCR and other support files.

When this has a good chance of working (heuristic)

Hot patch success tends to be higher when the newer build changes:

  • .lsp, .dcl, .scr, .mnu/.mns/.mnc, .txt, .dat, CSV templates â¦and does not introduce:

  • new DLLs/ActiveX components,

  • different VLX compiled for a different Visual LISP/AutoCAD runtime,

  • new registry keys that the installer must create.

If the newer build includes only script/UI logic changes, hot patching can be a strong first attempt.

Safety and rollback

Hot patching is safe if you do it with reversible steps:

  • Work in a VM (or a clone).

  • Take a snapshot before installing.

  • Take a snapshot after v3.60 install but before overlay.

  • Back up the entire ConstructiVision install folder before overwriting anything.

  • Keep a copy of the newer payload in a separate staging folder.

Step-by-step procedure

0) Prepare a controlled test case

Pick a âoeknown-goodâ drawing or workflow:

  • a sample tilt-up plan that exercises panels, dimensions, schedules, and any âoeEZâ macros you rely on,

  • and a checklist of âoeexpected commandsâ (e.g., custom commands in the command line, menus, dialog launches).

This becomes your pass/fail yardstick.

1) Snapshot / baseline capture

Recommended artifacts to capture before installing:

  • AutoCAD version/build info (About dialog) and where acad.exe lives.

  • Your AutoCAD support file search path (Options â-’ Files).

  • Any existing ConstructiVision folders (if this isnâTMt a clean VM).

  • A file list of the target install directory (for later diff).

If your environment allows it, also capture a registry snapshot (details in Appendix).

2) Install ConstructiVision v3.60 normally

Run the installer and confirm you can launch AutoCAD 2000 and reach a minimal ConstructiVision âoeentry pointâ:

  • menu item present,

  • command(s) recognized,

  • at least one dialog opens.

If you canâTMt validate that, hot patching is the wrong next stepâ”fix the base install first.

3) Locate the installed footprint

Identify:

  • ConstructiVision install directory (often under C:\Program Files\... or an AutoCAD support folder)

  • AutoCAD support folders that the installer wrote into

  • any *.mnu/*.mns/*.mnc entries and the primary load point (e.g., a menu load or an acaddoc.lsp hook)

Record the exact paths; youâTMll need them for the overlay.

4) Stage the newer payload

Put the newer build files in a staging folder, e.g.:

  • C:\CV_STAGE\NEW_PAYLOAD\...

Do not copy directly from removable media into the live folder; stage first so you can:

  • compare file trees,

  • compute hashes,

  • and re-run the overlay repeatably.

5) Inventory: âoeWhatâTMs different?â

Before copying, do a tree comparison between:

  • Installed v3.60 folder

  • Newer payload folder

You are looking for:

  • files that exist in newer payload but not in v3.60,

  • files that exist in both but differ (size/date/hash),

  • files in v3.60 that newer payload no longer includes (these may still be required by menus).

Practical rule: overlay and add, but avoid deleting on the first pass.

6) Perform the overlay (the actual hot patch)

Do the overlay in this order:

  1. Backup installed v3.60 folder to a timestamped archive folder.

  2. Copy newer payload files into the installed v3.60 install directory, preserving structure.

  3. If prompted to overwrite, overwrite (because that is the point).

  4. Keep a log of any conflicts you decide not to overwrite (rare).

Recommended: copy in two passes:

  • Pass A: only LSP/DCL/SCR/menu files (lowest risk).

  • Pass B: compiled assets (VLX) only if Pass A still leaves you missing critical behavior.

7) Reconcile load points (menu / startup hooks)

After overlay, verify the âoeentry pointâ still points to real files:

  • If the menu references a file name that changed between builds, you may need to add a compatibility alias file (e.g., a thin wrapper LSP that loads the new one).

  • If there is an acaddoc.lsp / acad.lsp hook, confirm it still exists and still loads what it expects.

Prefer compatibility shims over editing multiple legacy menus on the first attempt.

8) Validate in AutoCAD 2000

Start AutoCAD 2000 and test:

  • Do ConstructiVision commands resolve?

  • Do dialogs open cleanly (DCL mismatches show quickly)?

  • Do expected menus/toolbars still appear?

  • Run the known workflow drawing and confirm output.

Capture any errors:

  • AutoCAD command line error text,

  • acad.err (if present),

  • Visual LISP console output (VLIDE), if applicable.

9) If it fails: narrow the problem

Common failure buckets:

A) Pathing / missing file

  • Symptom: âoecannot find file â¦â on load.

  • Fix: missing search path or wrong file name; add shim LSP or adjust support path.

B) DCL mismatch

  • Symptom: dialog fails or throws DCL errors.

  • Fix: ensure .dcl and calling .lsp are from same build; overlay both.

C) VLX compatibility

  • Symptom: load error when calling a VLX feature, or silent failures.

  • Fix: try keeping the v3.60 VLX while overlaying only scripts; if newer build depends on newer VLX APIs, you may need to swap the VLX too.

D) Installer-created registry setting required

  • Symptom: features missing even though files exist.

  • Fix: compare registry/profile settings from a known-good install of the newer build (if you have one) and replicate.

10) Document what worked

If the hot patch works, record:

  • exactly which folders were overwritten,

  • whether VLX was swapped or kept,

  • any compatibility shim files created,

  • and a file list/hashes for the âoeworking overlay.â

This becomes your repeatable âoeupgrade recipe.â

Appendix: Registry snapshot concept (for later automation)

If you suspect installer-created keys matter, a snapshot approach helps:

  • Snapshot registry before v3.60 install

  • Snapshot after v3.60 install

  • (Optional) snapshot after overlay

Then diff to find:

  • AutoCAD profile changes,

  • ConstructiVision-specific keys,

  • support path additions, menu load settings, etc.

On Windows XP-era systems, tools like âoeRegshotâ were commonly used for this purpose. Use this only in a VM / isolated environment.