bobsheets
Automotive
- Dec 4, 2002
- 36
I did a thread search and I hope I'm not re-hashing a subject, but we need help.
We recently updated from 2001 to AutoCAD Mechanical 2004. All is well except (1) out of (19) seats. The problem child is a Gateway P4 3 Ghz with 2 Gb of ram and a 3Dlabs Wildcat 880 Pro. This is our premier system (it's mine!) and I use it for Algor FEA as well.
I run XP Pro 2002 SP1 as a user with admin rights. Our network is a 100gb optical with a new server dedicated to our workgroup. My system just crawls in ACAD!! On all but the most rudementary commands the cursor goes away for 5 to 15 seconds (time in on your watch!!) Our IT guys are stumped.
I have worked local from C:\Temp - no diff
I have shut down AV, Quicktime anything else I could find _ no diff
I have logged in as workstation only (Novell net)- no diff
The only thing that fixes it, is to log on as Administrator (not user with admin), then it screams!! I have searched the Autodesk knowledge base and ID:TS45410 clearly identifies the problem as "permission issues" but offers no solution or work around. I'll end the post (too long) and hope to hear from somebody.
We recently updated from 2001 to AutoCAD Mechanical 2004. All is well except (1) out of (19) seats. The problem child is a Gateway P4 3 Ghz with 2 Gb of ram and a 3Dlabs Wildcat 880 Pro. This is our premier system (it's mine!) and I use it for Algor FEA as well.
I run XP Pro 2002 SP1 as a user with admin rights. Our network is a 100gb optical with a new server dedicated to our workgroup. My system just crawls in ACAD!! On all but the most rudementary commands the cursor goes away for 5 to 15 seconds (time in on your watch!!) Our IT guys are stumped.
I have worked local from C:\Temp - no diff
I have shut down AV, Quicktime anything else I could find _ no diff
I have logged in as workstation only (Novell net)- no diff
The only thing that fixes it, is to log on as Administrator (not user with admin), then it screams!! I have searched the Autodesk knowledge base and ID:TS45410 clearly identifies the problem as "permission issues" but offers no solution or work around. I'll end the post (too long) and hope to hear from somebody.