2.7 KiB
LAUNCHER to P_Rec_Annot
Proven loading contract
| Stage | Evidence | Finding | Confidence |
|---|---|---|---|
| Deployment selection | All_Serv_Install/Settings.xml; download_lists/download_list_plant.xml |
P_Rec_Annot is an installer plugin catalog; its configured install file is OrthoLoader.dll. |
CONFIRMED |
| Local target | Plant configuration target | P_Rec_Annot is intended to be copied under C:\AutoCAD User Support\Applications\P_Rec_Annot. |
CONFIRMED |
| Bootstrap selection | installer Plant pattern object/arguments | All_Serv_Install invokes P_Serv_Starter.exe after install selection. |
CONFIRMED |
| Generated first load | P_Serv_Starter/Program.cs:140-174 |
For each installed DLL catalog, generated LISP emits (command "_netload" attribute). Therefore OrthoLoader.dll is loaded from the local Applications path when its catalog exists. |
CONFIRMED |
| Generated LISP activation | launcher_starter.lsp:74-96 |
It renames _app_netload.lsp, adds Applications to SupportPath and (load ...)s app_netload.lsp. |
CONFIRMED |
| Automatic LISP invocation | source comment in Program.cs:181; no installed startup file |
acaddoc.lsp is named by a comment, but its installed content and registration were not available. |
UNKNOWN |
| Secondary module load | legacy audit, OrthoLoader.Ribbon.Initialize / OrthoLoader.Initialize |
OrthoLoader reads adjacent Settings.xml and sequentially calls ._netload for 20 configured modules. |
CONFIRMED |
P_Rec_Annot-specific implication
The historic contract is not a direct network NETLOAD. It is a local synchronized application directory followed by a generated, per-session AutoLISP loader. A generated LISP includes the Plant project path in its first comment and conditionally emits loads only for existing local plugin catalogs. New code must not reproduce that behavior before deciding whether it is compatible, necessary and safe for Plant 3D 2026.
The prior legacy audit established that OrthoLoader.dll is the initial assembly for P_Rec_Annot. This launcher audit establishes how the installer/bootstrap is intended to make that assembly loadable. Neither audit proves the deployed local files existed or auto-loaded on this workstation.
Integration recommendation
Use one versioned, locally synchronized entry artifact only after a compatibility decision. The minimal pilot should retain the existing installer catalog/target contract, make the bootstrap load exactly one new entry assembly, and use an explicitly reviewed startup mechanism. Do not rely on an unproven AppLoader bundle or add new global TRUSTEDPATHS/profile mutations. The generated loader and any project-path comment are legacy behavior, not requirements for the new P_Rec_Annot until runtime validation establishes a need.