Assy too large to load in ProE

[dakeb]

Hi, I have 2GB ram but for a particular large assembly it always runs out of memory before loading up and crashes ProE. I only want to load it to create a step file to export. Am running WF3 on PDMLink.

Has anyone any suggestions how to get this done? To open each sub-assy to create the step is tedious, and requires re-assembly afterwards, and the pc may still run out of ram.

Thanks,

Dave

 

[seymours2571]

Here are some options:

Open it on a 64 bit machine.

Use the 3GB switch with windows 32 bit

Use simplified reps.

Steve

 

[dakeb]

Steve,

Please would you tell me where to find how to set the 3GB switch?

I can't open the assy to create the simp rep, and dont have access to a 64 bit m/c.

Thanks

Dave

 

[dakeb]

Does this mean 3GB switch is already enabled?

[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect /3gb

If so, I guess I can't load the assy.

Dave

 

[seymours2571]

It appears the 3GB switch is already enabled.

If you have access to a 64bit machine you can open it from there.

You might have to use simplified reps in order to open parts of the assembly to STEP out.

Keep in mind of the person that is going to open the STEP file on his/her side. If you make the STEP file huge, you might force them into the same memory issues you are having.

Steve

 

[dakeb]

Looks like I have a tedious job on my hands.

Thanks for the info Steve.

 

[mjcole]

If the Assembly has Sub-assemblies in it, try loading those first. If they are already loaded it will make it easier to display them because they are already in memory and all don't have to be loaded simultaneously.

Michael

 

[looslib]

The 3GB switch doesn't help unless you have 4GB of physical memory in your computer.

Also, if you use it, add /userva=1100 to the line. This will allocate 1.1GB of memory to the OS, which is what XPpro needs.

Michael's suggestion will help forloading large assemblies.

Your best option is to break the structure down into smaller sub-assemblies and do multiple exports.


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

Ben Loosli

 

[seymours2571]

Just to clarify...

"The 3GB switch doesn't help unless you have 4GB of physical memory in your computer."

Not true. Any additional memory requests that cannot be handled by the current physical ram is handled via virtual memory, which is a hidden swap file located on the root drive named "pagefile.sys". While access times to swap memory via the physical disk are *much* slower than RAM, your particular process can still access up to almost 3GB of memory.

Second, it is not recommend to set the /userva switch to such a low value as 1100. This switch limits the amount of memory accesible by the process not the OS. Microsoft recommends 2900-3030. See their link:

http://support.microsoft.com/kb/833721

You can export each sub assembly seperately or you can perform the export on a 64bit machine.

Steve