64 to 32 bit file

[ctopher]

Why would an assembly that was created in a 64 bit machine lock up on 32 bit machines?
We are having this issue on several PCs.
The 64 bit part files are a little slow to open on 32 bit, but the larger 64 bit lock up.

The product designers at our parent company use 64 bit, then send us the files for production tooling.

I have never had this issue before when we used both systems several years ago at another company.


Chris
SolidWorks 09, CATIA V5
ctopher's home
SolidWorks Legion

 

[ShaggyPE]

I use 32 bit primarily using 2006. We are tinkering with a second 64 bit machine. I have not had the problems you are experiencing. I have transferred numerous files back and forth. Though all of the files were originally created on 32 bit.

-Dustin
Professional Engineer
Certified SolidWorks Professional
Certified COSMOSWorks Designer Specialist
Certified SolidWorks Advanced Sheet Metal Specialist

 

[CorBlimeyLimey]

To my knowledge files created on x32 and x64 systems should be interchangeable.

Are the larger files simply requiring more resources than the x32 has to give?

What are the x32 system specs?

 

[ctopher]

The system specs vary among several PCs having the same problem.
On the two PCs here, the assy is requiring more resources.
But, at the site where the 64 bit assy is created, it also does not open on their other PC that is 32 bit with the same specs as the 64 bit.

It seems that once a file gets to big and is created on 64 bit, it overwhelms the 32 bit.
In this case the assy file size is 82.8 MB.

Chris
SolidWorks 09, CATIA V5
ctopher's home
SolidWorks Legion

 

[PeteDB]

Is it failing even when opened Lightweight? Can you have the people on the 64bit system suppress parts so you can unsupress only what you need to work on? Just some suggestions.

 

[rgrayclamps]

Hi, Chris:

I have been having the same issue as you have. We have about a dozen of SW seats. All of them are run on 32 bits machines except one which is 32 bits SW installed on 64 bits machine. I have the same headache every time I open SW documents from this machine. We are still using SW 2008 sp 3.1.

 

[ctopher]

I can't get far enough to open the file to make the assy lightweight. When I click on 'open', SW locks.

The last time I worked between 32 and 64 bit was on v2005 or 2006.

Chris
SolidWorks 09, CATIA V5
ctopher's home
SolidWorks Legion

 

[SincoTC]

Hi Chris,

You said "I can't get far enough to open the file to make the assy lightweight. When I click on 'open', SW locks."

I believe that in SW09, assemblies default to opening in lightweight, certainly I've found that the checbox for this in the "File open" dialog is always checked, whereas it used to be linked to "Large assembly mode". I recall reading somewhere that this was a sneaky way to fulfill the promises of faster opening times but I wouldn't dream of saying such a thing!

As these files come from another site, have you checked the references before you try and open the assembly in case it's hanging up trying to find loads of non-existant paths?

Also, as you're on 09, have you tried the "Quick view/Selective opening" option and do you know if it contains any SpeedPak Sub-Assemblies?



Trevor Clarke. (R & D) Scientific Instruments.Somerset. UK

SW2009x64 SP4.0 Intel Core i7 2.94Ghz, 12Gb Ram, NVIDIA Quadro FX3700 Driver: 6.14.11.8246
SW2009x64 SP4.0 Intel Core 2 Duo 3.17Ghz, 8Gb Ram NVIDIA Quadro FX3700 Driver: 6.14.11.8246

 

[crjones]

We have 15 seats Of SolidWorks at this location. Five are 64 bit seats. We changed over to this mix with 2007 and are currently using 2009. There have not been any file opening problems. The 32 bit machines are slower with some of our more complex assemblies.

 

[EEnd]

As a shot in the dark, try running EcoSqueeze on them and see if that helps.

Eric

 

[CorBlimeyLimey]

"But, at the site where the 64 bit assy is created, it also does not open on their other PC that is 32 bit with the same specs as the 64 bit."

Where RAM is concerned, the x32 system cannot have the same specs as the x64 system.

If the large files begin to open but just lock up after processing a while, that indicates the RAM and VM setup are simply insufficient to open that size file. They've reached the limit of the x32 systems.

 

[ctopher]

SincoTC,
I have tried both "Quick view/Selective" and "Lightweight". The file opens, but I can not do anything..it locks up either way.
EcoSqueeze did not help.

This only happens for us if the file was created in 64 bit then opened in 32 bit. The other way works good.

CBL,
You're correct, the RAM is different, but don't know the differences.
The engineers at our parent company have the same issue and they are using high-end workstations.

Chris
SolidWorks 09, CATIA V5
ctopher's home
SolidWorks Legion

 

[CorBlimeyLimey]

Then you/they have hit the wall where 32 bit systems are concerned. The file is simply too big.

Good time to press for a system upgrade.

 

[ctopher]

We have a workstation on order.

Chris
SolidWorks 09, CATIA V5
ctopher's home
SolidWorks Legion

 

[CorBlimeyLimey]

What are you getting?

 

[ctopher]

Not sure, the boss ordered it. He didn't consult with me.

Chris
SolidWorks 09, CATIA V5
ctopher's home
SolidWorks Legion

 

[CorBlimeyLimey]

Hmmm ... that doesn't sound promising. I would be doing some digging to find out. Hopefully in time to correct the choice if necessary.

 

[ctopher]

It was passed by an engineer at corporate, who blessed it. Already purchased and in process of shipment.
We'll see....

Chris
SolidWorks 09, CATIA V5
ctopher's home
SolidWorks Legion

 

[ctopher]

Interesting.
When I started here I was given a new laptop with SolidWorks 2009.
When SW was installed, it was the 32 bit version.
I did some searching this morning and found the laptop is a 64 bit system.
I assume I can reload SW as the 64 bit SW 09 version?

Chris
SolidWorks 09, CATIA V5
ctopher's home
SolidWorks Legion

 

[CorBlimeyLimey]

I imagine you would have to uninstall the x32 version first.