Search the Community

some persons sent me CAD files , when i tried to open them , at once AutoCAD crashed and an error message appeared ... Autocad 2012 is there a way to check if the CAD file contains virus or not ?? - Repairing didn't work !! , only unistalling solved the problem , but when tried to open the file again , the program crashed

Hi everyone, I'm a noob to this forum and to 2013... I was using 2006 for too long, and now have finally made the switch to 2013 (yay?) So I (and some colleagues as well) have been having a problem with our blocks. Upon opening some of our files, we have noticed that the blocks in the file have duplicated themselves, also renaming themselves with the extension "-flat-1", "-flat-2", and so on, for as many instances of that block that exist in the drawing. Also, the block layer has changed to 0, and the linework layers within the block have changed to the layer that block was on previously! This is EXTREMELY annoying and problematic for our workflow, obviously, as it essentially removes the convenience of blocks! Recently this happened with a file that was very "clean" to start, and with extremely "clean" blocks... with the exception of having some xrefs from an international client (Turkey). We're trying to replicate this occurence intentionally to try to troubleshoot, without any luck. Is this something we're doing unintentionally, or could it be something viral from our "dirty" xrefs?? ps... my colleagues are using 2010 and 2012. **fingers crossed that someone has an answer!!** Thanks! multipule block error.pdf

All, Could you anyone help me to sort my problems, whenever I am open to any drawings, which getting autocad message with unknown script showing, In the drawing folder there was one LSP file creating automatically, the name was the lsp file was "acaddoc" screen shot attached for your reference, anyone have any experienced this before, I am working in a network shared drive, this is happened before yesterday, It would be great if someone would give the solution to sort-out this issue, Many thanks Shan