Welcome to Autodesk’s Installation and Licensing Forums. Share your knowledge, ask questions, and explore popular Download, Installation, and Licensing topics.
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Show only
|
Search instead for
Did you mean:
This page has been translated for your convenience with an automatic translation service. This is not an official translation and may contain errors and inaccurate translations. Autodesk does not warrant, either expressly or implied, the accuracy, reliability or completeness of the information translated by the machine translation service and will not be liable for damages or losses caused by the trust placed in the translation service.Translate
Whenever I open a drawing from a network drive, AutoCAD will get very slow.
Mostly this takes affect when calling commands opening a dialog box.
Network is WINNT, 100Mps, NTFS File System.
As there are about 1500 files in the directory, I think the problem is that ACAD searches the DCL first in the drawing directory, then in Supportdir.
When I open a drawing in a networkdrive containing only a few files, it works proberly.
Does anyone know a workaround?
(Splitting the directory is not usefull for me)
Whenever
I open a drawing from a network drive, AutoCAD will get very slow. Mostly
this takes affect when calling commands opening a dialog box. Network is
WINNT, 100Mps, NTFS File System. As there are about 1500 files in the
directory, I think the problem is that ACAD searches the DCL first in the
drawing directory, then in Supportdir. When I open a drawing in a
networkdrive containing only a few files, it works proberly. Does anyone
know a workaround? (Splitting the directory is not usefull for
me)
I found a workaround:
I structured by directories for my applicaction, one for Lisp and dcl files, one for DVBs, one for systemblocks.
Than I modified all my programs (lisp and VBA), for example:
In acaddoc.lsp I set the directories:
(setq lspdir "C:\\myapp\\lisp\\")
(setq vbadir "C:\\myapp\\vba\\")
(setq blockdir "C:\\myapp\\blocks\\")
(setvar "USERS1" vbadir) ;to get the vbadir in VBA
Defun a new load for the lisps:
(defun my_load (mylisp /) (load (strcat lspdir mylisp)))
I found a workaround: I structured by directories for my applicaction,
one for Lisp and dcl files, one for DVBs, one for systemblocks. Than I
modified all my programs (lisp and VBA), for example: In acaddoc.lsp I set
the directories: (setq lspdir "C:\\myapp\\lisp\\") (setq vbadir
"C:\\myapp\\vba\\") (setq blockdir "C:\\myapp\\blocks\\") (setvar
"USERS1" vbadir) ;to get the vbadir in VBA Defun a new load for the lisps:
We have the same problem. I've tried the workaround Grauth provided, but to no avail.
I've made some interesting observations (at least on our LAN).
The slow down affects drawings on network drives. The delay is directly proportional to the number of files in the directory. Many files=longer delay in showing dialog boxes and other commands. The delay can be very substantial...its very distracting and unacceptable.
I can prevent the 'slowness' by doing the following:
Start AutoCAD from its icon, but DO NOT open drawings through the File Open dialog. Instead, launch drawings from Windows Explorer. On our network, performance in drawings opened this way is far better. I know this sounds very strange, but please try it and let me know what you see. (repeat: AutoCAD must already be running when you launch the drawings for this effect to be noticed.)
