How to prepare a loading sequence at startup

[densan]

Hello forum, I was not sure if my question should go here or in the CAD management area.

 

We have CAD operators and designers using C3D, Plain AutoCAD, Plant 3D, and others. And I am looking for advice on how to organize and prepare a loading sequence at startup to meet these requirements:

Step 1 – Specify common settings at startup for ALL CAD users.

    ;;; I want to specify common settings for all users running
    ;;; the AutoCAD engine at startup.
    ;;; Defining settings at every startup is overkill, but this is only a test for now
    (defun c:1percadsession (/)
    (command "-PLOTSTAMP" "l" "n" "none" "off" "")
    (setvar "pdfshx" 0)
    (setvar "backgroundplot" 0)
    (and others......)
        (princ)
    )

 

Step 2 – Load and run a program every time an operator opens a CAD file.

    ;;; Load and run a required company lisp
    ;;; every time a user opens a drawing
    (defun c:themanismakingmerunoneachdwg (/)
     …………
    (princ)
    )

 

Step 3 – Make lisp available for a specific product or department.

    ;;; How to manage programs for a specific department or product?
    ;;; Should I breakdown lisps by product/department, P3Dcustom.lsp, CivilCustom.lsp?
    ;;; How to avoid loading unnecessary lisp for each department or product?
    (defun c:c3duserneeds01 (/)
     …………
    (princ)
    )
    ;;;
    (defun c:p&iduserneeds01 (/)
     …………
    (princ)
    )

 

Here are some of my questions:

If I create a folder (\\\\server\\CAD_Support\\Startup\\) and add the path to the support path under options.

    What lisp files should go in my network copies of acad.lsp or acaddoc.lsp?

    What files should be (load “name.lsp”) vs. (autoload “name.lsp”)

    Do I have to add them to the trusted locations section as a precaution?

    Do my custom acad.lsp or acaddoc.lsp files create a conflict with originals from AutoCAD?

Sorry for the long post, but I feel like I have all the pieces and now I need help putting the big messy puzzle together.

Thank you very much for any suggestions to my problem,

 

[BIGAL]

I dont uses acad.lsp etc but rather a custom lisp that is loaded on startup Appload, Start up Suite, been using it for years. It and the programs, CUIX & mnu, slb, were on the server, also have a setup.lsp that you run once and sets all the paths etc would normally run this after a new install. As well as a script that had the operators toolbar choices. 

 

Step 3 – Make lisp available for a specific product or department. So for me yes load the correct custom lisps, on the user PC, much easier than trying to do some form of load this or not from a program sense. Not sure in the autoload if you can  do (if saycorrectversion "load custom1") 

 

You can search the registry keys for software versions etc.

 

 

 

Edited March 21, 2022 by BIGAL