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:
;|
Edit Enterprise CUI.lsp
Version history
1.1 2009/06/09 Added support for CUIX files.
1.0 2007/12/07 Initial release.
Switches the enterprise CUI into the main CUI under Preferences, Files, Customization Files.
Allows for editing, then switches the CUI files back to the original settings.
Dependencies: none
Usage: Command: EditEnterprise, or Command: EC
Arguments: n/a
Returns: n/a
Copyright © 2007-2009 by Sparling, Inc.
Written permission must be obtained to copy, modify, and distribute this software.
Permission to use this software for any purpose and without fee is hereby granted,
provided that the above copyright notice appears in all copies and that both
the copyright notice and the limited warranty and restricted rights notice below
appear in all supporting documentation.
SPARLING PROVIDES THIS PROGRAM "AS IS" AND WITH ALL FAULTS.
SPARLING SPECIFICALLY DISCLAIMS ANY IMPLIED WARRANTY OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR USE.
SPARLING DOES NOT WARRANT THAT THE OPERATION OF THE PROGRAM
WILL BE UNINTERRUPTED OR ERROR FREE.
|;
(defun sinc:UpdateCUIs
(mainCUI entCUI
) mainCUI)
(setenv "EnterpriseMenuFile" entCUI
) 'T)
(setenv "EnterpriseMenuFile" "") mainCUI)
'T)
((princ "\nOne (or both) of the cui files was not found."))))
(defun C:EC
() (C:EditEnterprise
))
(defun C:EditEnterprise
(/ wsNow fileExt mainNow entNow
) (".cuix"))
fileExt)
(cond ((sinc:UpdateCUIs entNow
nil) (sinc:UpdateCUIs mainNow entNow)))
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).