Continue to Site

Eng-Tips is the largest engineering community on the Internet

Intelligent Work Forums for Engineering Professionals

  • Congratulations waross on being selected by the Eng-Tips community for having the most helpful posts in the forums last week. Way to Go!

Proe slows PC

Status
Not open for further replies.

gb433054

Aerospace
Jul 24, 2003
28
I am running Proe a P3 1.8GHZ with 256MB Ram and a 64MB graphics card. However when I run Pro my PC becomes very sluggish. Is there anything I need to set to make it run faster, such as virtual memory, network setup etc. Any help would be appreciated.

Thanks in advance
 
Replies continue below

Recommended for you

What version of Pro/E? 256M is not enough memry for this memory hog of a program!


"Wildfires are dangerous, hard to control, and economically catastrophic."

Ben Loosli
CAD/CAM System Analyst
Ingersoll-Rand
 
I am running date code 2001490. I have also noticed that a service called pglclock.exe runs in the background and runs my CPU usage up to 100%, any ideas
 
Your system is probably on the low en of what you need to run Pro. I would suggest making sure you have at least a gig for your swap file size, up your RAM to atleast 512. If your working directory is across a net, try using a local drive instead. Make sure you arent running any other "large" programs at the same time. Thats about all I can think of off the top of my head

MM

 
I'm quite happily running ProE 2001 on a P400 with 256Mb RAM and a moderate spec graphics card. I'm not doing any really heavy work though (Biggest assembly is about 50 or 60 parts, though some parts are quite detailed).

I haven't seen Wildfire run successfully on anything short of a 2GHz P4 with a half Gb RAM and a 64 Mb graphics card.
 
One of our division were running what you have. They put together their own machines on a tight budget and wanted our three dell workstations; because ... We opened the assembly in six minutes, they only had two machines that would open the same assembly and it was 26 & 32 minutes. They were not using simplified rep and every part seemed to be a family table.
We had to move swap to 1g to match 1g of ram. You can double your swap of ram ... but much more doesn't really help. Also, we have 15000rpm hard drives and are on a 100mg network.
So, check ram & swap, get smart in simplified reps & use them, and put a business case together for the big workstation.
 
I've asked PTC about pglclock.exe and was told that you cannot run without this (funny thing is: nobody could tell me what it does). This might help you getting started on biger assemblies: Create a rep called 'empty' and just put in important skeletons and the first part. This will always open easily and then once you are 'in the door', you can switch back and forth or create other reps as you need them. The advantage to starting in an empty one is if you have problems opening a subsequent one, you can always just pop back the 'empty' without having to start all over again.
Also be carefull deleting reps - if it's the one you are in you will revert back to 'Main' and that wil take a while to get to so always switch to another rep before deleting one.
Hope this helps.


 
After persisting with pglclock.exe problem I discovered that it eventually (8 mins) settles down and stops absorbing all my CPU processing capabilities. The exe is obviously still loading modules in the background when Pro starts up. Anyway, an extra 512MB of ram is on its way to me, thanks for all your help

Dave
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor