Autocad running really slow on Network

[sinc]

Just for giggles we reloaded our original "MapLandDevelopmentDesktop" and "Land Desktop" Profiles, these where custumized for network also, and presto problem solved. We have not actually found the problem, we suspect corrupted CUIs, regardless it is a simple correction for a big headache.

The only link between Profiles and the CUI is that the Profile stores links to the Main and Enterprise CUI files. If you were able to switch to different Profiles but continue using the same CUI and have no problems, then that's a strong indication that the problem is not in the CUI.

Some things that I've noticed cause problems are the "hidden" paths in OPTIONS. Well, they aren't actually "hidden", just easy to overlook - things like the "Plot to File" path, and the "Plot Stamp Settings" path, and so forth. If these are pointed to nonexistent network locations, they can cause strange slowdowns in unexpected places, even if they are disabled (greyed-out in the OPTIONS dialog).

This sort of thing usually doesn't affect new installations, unless you are using a Network install or you import a predefined Profile (.ARG file) after installation.

[Ruben]

Just out of curiosity, what virus scanner do you use? We had a user's machine infected once and the virus was apparently using that machine to send spam. The machine had Symantec anti virus installed, but the virus had been able to outsmart it. I installed, AVG Free edition temporarily on that machine and was amazed to see how AVG made short work out of the virus and the machine was freed. You never know, you might want to give it a try.

[sinc]

We use AVG. I got actively upset with Norton, which is what we had largely been using before.

[Ruben]

OK, here is another thing to check. Something in your system may be pegging your processor. I recommend that you download Process Explorer and run it in conjunction with AutoCAD to see if this is the case and what program is the culprit. You can set it to always be on the top.

http://www.microsoft.com/technet/sy...ssExplorer.mspx

If that doesn't help you, try Filemon:

http://www.microsoft.com/technet/sys...s/Filemon.mspx

With Filemon you can see every file the OS is opening, or trying to open. Of course there are a lot of them, so the way to use it is to have it start monitoring right before a suspect operation starts, and then have it stop as soon as you think you have enough data to inspect. Filemon can sometimes be very revealing.