Topic: cant edit acad.lsp or acaddoc.lsp

[andrew..]

hello gang.
i started a new job and couldnt remember my old login so had to make a new account.
anyway. i have some custom lisp files i need to add to the acad.lsp and the acaddoc.lsp files but they are admin controlled.
how can i get my acad and acaddoc lsp files to load along side of the OOTB acad and acaddoc lsp files?

is there maybe another way to load my files on startup without editing these files?

[JohnK]

Yes, a MNL file.

[ChrisCarlson]

People still load their routines into those files? Why not load through the startup suite which is not admin controlleD?

[ronjonp]

People still load their routines into those files? Why not load through the startup suite which is not admin controlleD?

I have not used the startup suite in over a decade. Last time I remember it was sorta half baked .. but maybe it's better now?

[JohnK]

People still load their routines into those files? Why not load through the startup suite which is not admin controlleD?

Ummm...why wouldn't they *not* use an MNL file? Don't you create a custom or enterprise CUIX file? There was no way I was going to go around to everyone's computer and add files to the end users startup thing (way too many people/computers); I would have lost my job for wasting time!

...
MNL files with the same name and location as your main, enterprise, or partial customization files are loaded automatically; these files cannot be removed.

[dgorsman]

hello gang.
i started a new job and couldnt remember my old login so had to make a new account.
anyway. i have some custom lisp files i need to add to the acad.lsp and the acaddoc.lsp files but they are admin controlled.
how can i get my acad and acaddoc lsp files to load along side of the OOTB acad and acaddoc lsp files?

is there maybe another way to load my files on startup without editing these files?

You don't.  If those files are locked down there is generally a good reason.  Your customizations could end up bypassing important protocols/procedures you aren't aware of.  First, as a new employee you need to learn to do things the company way.  Then you can see if fiddling around would improve things rather than making them worse.

[ChrisCarlson]

People still load their routines into those files? Why not load through the startup suite which is not admin controlleD?

Ummm...why wouldn't they *not* use an MNL file? Don't you create a custom or enterprise CUIX file? There was no way I was going to go around to everyone's computer and add files to the end users startup thing (way too many people/computers); I would have lost my job for wasting time!

...
MNL files with the same name and location as your main, enterprise, or partial customization files are loaded automatically; these files cannot be removed.

We utilize enterprise CUIx here but the way it sounds he doesn't have access to modify the CUI file (maybe they have the same setup?) so the next step is to

A) Figure out why, maybe its a bad routine? Not vetted?
B) If he absolutely needs that routine the next best step is to add it to his start-up suite.

[BlackBox]

If using 2012+, you can always use one of the 2-3 ..\ApplicationPlugins\ folders to load a custom .bundle (which loads your own LISP, etc.) and completely bypasses all AutoCAD Security (save some 2016 changes, which user can immediately, and permanently dismiss, BTW)... See this old post for more info.


Also, doesn't CUIx support 'embedded' LISP (no need for MNL)?

About Loading an AutoLISP File with a CUIx File

...
MNL files with the same name and location as your main, enterprise, or partial customization files are loaded automatically; these files cannot be removed. Additional AutoLISP (LSP) files can be loaded with a CUIx file by adding a reference to the file under the LISP Files node displayed for a loaded CUIx file in the Customizations In pane of the Customize User Interface (CUI) Editor.

[BlackBox]

We utilize enterprise CUIx here but the way it sounds he doesn't have access to modify the CUI file (maybe they have the same setup?) so the next step is to

A) Figure out why, maybe its a bad routine? Not vetted?
B) If he absolutely needs that routine the next best step is to add it to his start-up suite.

So long as the Enterprise CUIx is not read-only, this may be of use.

I could not disagree with you more on point B - demand loading, anyone?

[JohnK]

Make your own CUIx file.

Yes, BB it does but I loaded all my "support" functions into the MNL file and anything else I used embeded. ...of course I also rolled my own loader which was in the MNL file so I never used the embeded lisps that much either so take that with a grain of salt.

[JohnK]

Would you mind sending me that lisp from RRB, BlackBox (I'm not a member there).

Also, Is RRB still active? What's he up to these days?

[ChrisCarlson]

Make your own CUIx file.

Yes, BB it does but I loaded all my "support" functions into the MNL file and anything else I used embeded. ...of course I also rolled my own loader which was in the MNL file so I never used the embeded lisps that much either so take that with a grain of salt.

Why make a new CUIx file simply for loading of local, per-user lisp routines? You can definitely do that but Confucius says "don't use a cannon to kill a mosquito".

[andrew..]

its custom block commands and ddedit and a few other general all purpose custom commands but for my custom wblock command i undefind the OOTB block command and the ddedit command and so on.
ill look into the startup suite and the mnl and determine what is easiest

if any other ideas come to mind, please post them

thanks again

[andrew..]

Make your own CUIx file.

Yes, BB it does but I loaded all my "support" functions into the MNL file and anything else I used embeded. ...of course I also rolled my own loader which was in the MNL file so I never used the embeded lisps that much either so take that with a grain of salt.

i was able to load my own menu with no issues. its the acad and the acaddoc lisp files that i need access to.
or a way to load my own code on startup

[ronjonp]

If you can load your own menu, I'd suggest the mnl route. There are plenty of example routines here for loading files from a directory.

[dgorsman]

Make your own CUIx file.

Yes, BB it does but I loaded all my "support" functions into the MNL file and anything else I used embeded. ...of course I also rolled my own loader which was in the MNL file so I never used the embeded lisps that much either so take that with a grain of salt.

Why make a new CUIx file simply for loading of local, per-user lisp routines? You can definitely do that but Confucius says "don't use a cannon to kill a mosquito".

One of the major drawbacks of the Startup Suite is loads for every AutoCAD profile.  You don't necessarily want everything loading everywhere, especially if you have potentially conflicting functions for third-party applications in each profile.

[Lee Mac]

People still load their routines into those files? Why not load through the startup suite which is not admin controlleD?

Aside from the fact that the Startup Suite is historically known to be notoriously buggy, there are several other advantages to using files such as the acaddoc.lsp to load customisations, such as distributing/updating customisations for multiple users simultaneously across a network, using project-specific acaddoc.lsp files residing in a project directory to only load customisations required by a project (since AutoCAD will only ever load one acaddoc.lsp file, and will always look in the working directory first) etc.

[BlackBox]

Would you mind sending me that lisp from RRB, BlackBox (I'm not a member there).

Source code from RRB's post directly copied here:

Code - Auto/Visual Lisp: [Select]

1. ;|
2.  
3. Edit Enterprise CUI.lsp
4.  
5. Version history
6. 1.1     2009/06/09      Added support for CUIX files.
7. 1.0     2007/12/07      Initial release.
8.  
9. Switches the enterprise CUI into the main CUI under Preferences, Files, Customization Files.
10. Allows for editing, then switches the CUI files back to the original settings.
11.  
12. Dependencies:   none
13. Usage:          Command: EditEnterprise, or Command: EC
14. Arguments:      n/a
15. Returns:        n/a
16.  
17. Copyright © 2007-2009 by Sparling, Inc.
18.  
19. Written permission must be obtained to copy, modify, and distribute this software.
20. Permission to use this software for any purpose and without fee is hereby granted,
21. provided that the above copyright notice appears in all copies and that both
22. the copyright notice and the limited warranty and restricted rights notice below
23. appear in all supporting documentation.
24.  
25. SPARLING PROVIDES THIS PROGRAM "AS IS" AND WITH ALL FAULTS.
26. SPARLING SPECIFICALLY DISCLAIMS ANY IMPLIED WARRANTY OF
27. MERCHANTABILITY OR FITNESS FOR A PARTICULAR USE.
28. SPARLING DOES NOT WARRANT THAT THE OPERATION OF THE PROGRAM
29. WILL BE UNINTERRUPTED OR ERROR FREE.
30.  
31. |;
32.  
33. (defun sinc:UpdateCUIs  (mainCUI entCUI)
34.  (vl-Load-Com)
35.  (cond ((and entCUI (findfile mainCUI) (findfile entCUI))
36.         (vla-Put-MenuFile
37.          (vla-Get-Files (vla-Get-Preferences (vlax-Get-Acad-Object)))
38.          mainCUI)
39.         (setenv "EnterpriseMenuFile" entCUI)
40.         (command "._Menu" "")
41.         'T)
42.        ((and (not entCUI) (findfile mainCUI))
43.         (setenv "EnterpriseMenuFile" "")
44.         (vla-Put-MenuFile
45.          (vla-Get-Files (vla-Get-Preferences (vlax-Get-Acad-Object)))
46.          mainCUI)
47.         (command "._Menu" "")
48.         'T)
49.        ((princ "\nOne (or both) of the cui files was not found."))))
50.  
51. (defun C:EC () (C:EditEnterprise))
52.  
53. (defun C:EditEnterprise  (/ wsNow fileExt mainNow entNow)
54.  (vl-Load-Com)
55.  (setq wsNow   (getvar "WSCurrent")
56.        fileExt (cond ((< (atoi (getvar 'AcadVer)) 18) ".cui")
57.                      (".cuix"))
58.        mainNow (strcat (vla-Get-MenuFile
59.                         (vla-Get-Files (vla-Get-Preferences (vlax-Get-Acad-Object))))
60.                        fileExt)
61.        entNow  (strcat (getenv "EnterpriseMenuFile") fileExt))
62.  (cond ((sinc:UpdateCUIs entNow nil)
63.         (command "._CUI")
64.         (sinc:UpdateCUIs mainNow entNow)))
65.  (cond ((/= wsNow "") (setvar "WSCurrent" wsNow)))
66.  (princ))
67.  

Also, Is RRB still active? What's he up to these days?

He may not be active in the forums, but he is the current AUGI President.

... You can definitely do that but Confucius says "don't use a cannon to kill a mosquito".

Sun Tzu teaches to engage the enemy with overwhelming force, if victory is your goal.

Aside from the fact that the Startup Suite is historically known to be notoriously buggy, there are several other advantages to using files such as the acaddoc.lsp to load customisations, such as distributing/updating customisations for multiple users simultaneously across a network, using project-specific acaddoc.lsp files residing in a project directory to only load customisations required by a project (since AutoCAD will only ever load one acaddoc.lsp file, and will always look in the working directory first) etc.

1+

I employ a .NET app to 'blacklist' any auto-loading Acad* code files found to be accessible (that are not our own) before the startup sequence attempts to load them, but to support project-specific code, we load a custom named, relative-path LISP, only if found within a given project... which all helps to mitigate potential 'infections' (which have happened in the past).

[andrew..]

ok now that i got that straight.. how about loading a separate acad.pgp file?
will acad load 2 different acad.pgp files?
if not any way to get another .pgp file to load up?

[Crank]

[...]
if not any way to get another .pgp file to load up?

The support paths are searched in the order as they are placed in the OPTIONS panel. So put your .PGP file in the first folder of that list (or change the order of the list).