morozovsa/autodesk
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

audit: document launcher source architecture

Browse Source
This commit is contained in:
codex
2026-07-31 14:06:39 +03:00
parent b33351117b
commit 36178374db
15 changed files with 218 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
migration/audits/launcher-source-architecture/autocad-launch-chain.md
+38
View File
@@ -0,0 +1,38 @@
# AutoCAD/Plant launch chain
## Confirmed static chain
```text
User
-> All_Serv_Install.exe Form1
-> copy selected Plant 3D application folders to local Applications target
-> Process.Start(P_Serv_Starter.exe, five configured arguments)
-> P_Serv_Starter creates local _app_netload.lsp and copies launcher_starter.lsp
-> P_Serv_Starter starts C:\AutoCAD User Support\p3d-support\start_plant_3d.bat
-> [UNKNOWN: installed batch contents and auto-load registration]
-> Plant 3D startup
-> launcher_starter.lsp (when loaded)
-> local app_netload.lsp
-> _netload local Applications\P_Rec_Annot\OrthoLoader.dll
-> OrthoLoader Settings.xml -> sequential ._netload configured modules
```
The final two steps are confirmed by the prior P_Rec_Annot legacy audit. The activation of `launcher_starter.lsp` is not directly implemented in `P_Serv_Starter`: `Program.cs:181` comments that `acaddoc.lsp` renames the generated file, while the copied LISP itself performs the rename and `load`. No matching installed `acaddoc.lsp`, batch file, or Applications directory existed on this workstation at audit time. Therefore automatic execution is `UNKNOWN`, not asserted.
## Source evidence
| Claim | Evidence | Confidence |
|---|---|---|
| User-visible installer starts configured object | `All_Serv_Install/Form1.cs:195-230` | CONFIRMED |
| Plant pattern object is `P_Serv_Starter.exe` | `All_Serv_Install/Settings.xml`, Plant 3D pattern | CONFIRMED |
| Five arguments include product, Applications target, settings, project and working directory | `Settings.xml` Plant pattern and `P_Serv_Starter/Program.cs:12-23` | CONFIRMED |
| Bootstrap generates `_app_netload.lsp` | `P_Serv_Starter/Program.cs:58-182` | CONFIRMED |
| Generated DLL modules use AutoLISP `_netload` | `P_Serv_Starter/Program.cs:146-151` | CONFIRMED |
| Bootstrap copies LISP and starts local batch file | `P_Serv_Starter/Program.cs:202-216,49-54` | CONFIRMED |
| Generated LISP is renamed, SupportPath updated and loaded | `P_Serv_Starter/launcher_starter.lsp:74-96` | CONFIRMED |
| Actual installed batch launches a specific Plant version | no installed batch was present | UNKNOWN |
## Historical source-only alternative
`All_Serv_Load/Addins/start_plant_3d.bat` contains a direct AutoCAD 2019 command using `/product PLNT3D /language "ru-RU"`, preceded by PlantCleaner and PnPPersistentCache cleanup. It is evidence only of that project's historical script; it is not evidence that current users start Plant 3D 2026 this way. No `/ld`, profile, LISP or script argument is present in that script.