Update 1, the first of Autodesk’s Updates (formerly Service Packs) for AutoCAD 2010 is now out for AutoCAD and AutoCAD LT. Equivalent updates for various verticals will follow soon. The Readme contains information about what was fixed, so I won’t reproduce that here.
As always, read the readme first and exercise the usual paranoia. However, my experience of the pre-release versions of this Update has been positive.
As I mentioned in my last post, I had some reservations about the code provided by Autodesk to deal with suspect acad.vlx and logo.gif files. Based on a suggestion from Jimmy Bergmark, I have written my own, safer version which you can download here: clean_virus_safe.lsp.
The comments at the top of the clean_virus_safe.lsp file explain what to do with it, but I will reproduce some of the relevant points here.
- Purpose: Checks for existence of acad.vlx and logo.gif files, which are associated with virus AL/Logo-A, also known as ACAD/Unexplode, ACAD/Agent.A or ACM_UNEXPLODE.B. Written as a safer alternative to Autodesk’s code which deletes suspect files without prior warning. This code renames the files instead.
- Legal: Provided as-is with no warranty whatsoever, use at own risk. May be distributed freely.
- Usage: Append the contents of this file into a startup LISP file (e.g. acaddoc.lsp in your search path – … Full post
Shaan Hurley has posted some useful information about another AutoCAD-based virus that is doing the rounds, and I strongly suggest you read it. However, I have some reservations about the solution that is posted there and in the Autodesk knowledgebase.
The LISP code suggested will delete any files called acad.vlx or logo.gif that are located in the current user’s current AutoCAD search path. There are a couple of problems with that.
- The search path will change depending on the user, the profile, the startup folder and the drawing folder. That means you can’t just use the code once and expect the problem to go away; the code will need to remain in place permanently to ensure it does not recur. That may not be a huge problem, although it will have a performance penalty (particularly where the search path is long and/or includes network paths) … Full post