JordanCN
Computer
- May 26, 2006
- 3
Most of our systems are XP 32 bit with two gigs. Most users have the ATI FireMV 2200 video card and a Athlon 64 X2 4000+ or above processor right up to a new Lenovo S20 with 3 gigs and a XEON processor. All of these systems have also been upgraded from SW 2007 SP05.
Our assemblies are very small coil motors that are about 30 parts including screws, washers, etc. and are about a 2 to 8 inches long. Very low demand. Most of these XP systems perform OK, but user who have several drawings or parts open start acting as if they are slowing down then solidworks stops responding. You can minimize SW and open it back up, but it acts like it is waiting for you to click some command somewhere. Hovering over some items will show whatever pop-up should appear, but clicking anything has no affect.
This happens even more in a brand new Lenovo S20 with 6 GB RAM running Windows 7 x64 with the Xeon processor and an ATI FirePro V3700. This system has a fresh Windows 7 install and a fresh SW 2011 x64 install along with Office 2010 and not much more.
Whenever SW 2011 gets to this state there are really no error messages other than Windows telling us that the program is not responding if we start clicking all over the place. A couple of times a user just left it as it was then came back to it a while later and it started working again for a while more, but then stopped responding.
Any suggestions?
Our assemblies are very small coil motors that are about 30 parts including screws, washers, etc. and are about a 2 to 8 inches long. Very low demand. Most of these XP systems perform OK, but user who have several drawings or parts open start acting as if they are slowing down then solidworks stops responding. You can minimize SW and open it back up, but it acts like it is waiting for you to click some command somewhere. Hovering over some items will show whatever pop-up should appear, but clicking anything has no affect.
This happens even more in a brand new Lenovo S20 with 6 GB RAM running Windows 7 x64 with the Xeon processor and an ATI FirePro V3700. This system has a fresh Windows 7 install and a fresh SW 2011 x64 install along with Office 2010 and not much more.
Whenever SW 2011 gets to this state there are really no error messages other than Windows telling us that the program is not responding if we start clicking all over the place. A couple of times a user just left it as it was then came back to it a while later and it started working again for a while more, but then stopped responding.
Any suggestions?