For one, why does a project folder have a lisp routine in it?
Refer to here,
http://www.theswamp.org/index.php?topic=35330.0
Infact you are the original poster
Close all sessions of AutoCAD, and then have your IT Admin, or someone responsible using a domain account with sufficient Active Directory permissions, call this PowerShell (As Administrator?):Code - C#: [Select]
Get-ChildItem <YourProjectFolderNetworkShareRoot>\*.* -Include *.lsp | Rename-Item -NewName { $_.Name -Replace ".lsp",".lsp.blacklist" }
* Warning - This PowerShell will rename ALL *.lsp files in ALL project folders; change the resultant file extension as needed.
Close all sessions of AutoCAD, and then have your IT Admin, or someone responsible using a domain account with sufficient Active Directory permissions, call this PowerShell (As Administrator?):Code - C#: [Select]
Get-ChildItem <YourProjectFolderNetworkShareRoot>\*.* -Include *.lsp | Rename-Item -NewName { $_.Name -Replace ".lsp",".lsp.blacklist" }
* Warning - This PowerShell will rename ALL *.lsp files in ALL project folders; change the resultant file extension as needed.
Could we useCode - Auto/Visual Lisp: [Select]instead of
\*.* -Include acaddoc.lsp |Code - Auto/Visual Lisp: [Select]
\*.* -Include *.lsp |
\*.* -Include acadapq.* |
as it's the code that does most of the damage. Could be VLX, ,FAS, or .LSP
Really? You blame AutoDesk?
If you feel vulnerable to this and it's so easy, make it yourself. Most people have protocols in place to avoid this type of thing. It is easy. Just like basic virus protection, it's up to the users to implement the necessary safeguards. You cannot blame AutoDesk for not protecting us, if some of us can't protect ourselves from the maliciousness of others.
The stuff about your issues with customization are not even related to the topic at hand.
For one, why does a project folder have a lisp routine in it?
For one, why does a project folder have a lisp routine in it?
I'm on Bricscad so this isn't an issue, but I sometimes put project specific customization in a lisp in each project file folder. This allows me to add on the fly customization that doesn't affect whole office, just usable by the project team. Some of it is an override to office standards, as required by the specific job.