Recently all my office computers infected with some autocad virus. After each dwg we open, we have to correct the following system variables.1. mbuttonpan, 2. highlight, 3. zoomfactor.

Has anyone, to your knowledge, downloaded any macros, lisp or vlx files?Do you share drawings with another company located outside of your country?When did you first notice the problem?What have you done to troubleshoot the problem?Could it be nothing more than a poorly written custom lisp routine that forgets to reset certain variables?

We normally share dwgs with other contractors & consultants. There is some lisp file in all directories which norton AV detected and cleaned. But the damages are already done. It is about 10 days now. Thanks for reply.

I suppose you could include some lines of code in your acaddoc.lsp file that would reset the variables each and every time AutoCAD is started.Have you reported the problem to AutoDesk?I got to thinking about this and I'm wondering if you already have an acaddoc.lsp that is setting these variables (wrongly) for you.  It might be wise to check first.  Use the FINDFILE command to locate all instances of an acaddoc.lsp file.At the command prompt type (findfile "acaddoc.lsp) and press ENTER.  This should result in a path and file name being returned.  Use this information to retrieve the file, open it and read it.

Normal
0




false
false
false

EN-US
X-NONE
X-NONE













MicrosoftInternetExplorer4



























































































































































/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-qformat:yes;
mso-style-parent:"";
mso-padding-alt:0in 5.4pt 0in 5.4pt;
mso-para-margin-top:0in;
mso-para-margin-right:0in;
mso-para-margin-bottom:10.0pt;
mso-para-margin-left:0in;
line-height:115%;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:"Times New Roman";
mso-fareast-theme-font:minor-fareast;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;}




John Connor2011-06-24 12:38:22