New Computer UpgradeToday, Yeah! Oh No Got a Problem!

[AeroNucDef]

Hi all,

I finally got my new PC and new SW installation.

Here's the spec:

i7 950 64 bit chip
12Gb RAM
Quadro FX5500 card
New install of Solidworks from 32 to 64 bit.

Just got a few problems, hopefully someone can give me some advice.

I have a assembly that I've been working on (approx 1250 parts), but when I opened the assembly for the first time on the new PC, it came up will loads of errors and warnings for missing parts and mates. The thing is that the assembly was prefectly fine before this new PC and new install of SW64.
I thought because all the parts, assemblies, drawings are saved on a server and not saved on my PC, that the assembly would be fine.

Has anyone got any idea why this has happened.

 

[SnowCrash]

You might need to set up your document paths under tools, options. Did you save your old command configuration and reload it with the copy settings wizard?

--
Hardie "Crashj" Johnson
SW 2010 SP 4.0
HP Pavillion Elite HPE
W7 Pro, Nvidia Quaddro FX580

 

[DesignerGuy16]

Were they opened from a map drive or directly from the server? If they were linked to a map drive before, the links to the files will not be able to find the end location.

Also, did you have reference file locations setup on the old PC?

James Spisich
Design Engineer, CSWP

 

[AeroNucDef]

SnowCrash,

I haven't setup the documents path, or saved my command config.
All I did was to do a "Pack and GO", so if things went a bit cockeyed, then I would have all my files in one place.
Unfortunatly I have also opened the model from the Pack and Go, and that came up with errors as well.

Jspisich,

Not sure what a map drive is, but the files were opened directly from the server. I don't think I had Reference File locations setup.


thanks for your replies.

 

[macduff]

what does you "references" filepaths read when you open the assembly? you might need to reset the path to the server.

Colin Fitzpatrick (aka Macduff)
Mechanical Designer
Solidworks 2010 SP 3.1
Dell 490 XP Pro SP 2
Xeon CPU 3.00 GHz 3.00 GB of RAM
nVida Quadro FX 3450 512 MB
3D Connexion-SpaceExplorer

 

[macduff]

pack-n-go can be a bit dangerous sometimes. if it was done while the files were set at lightweight, you could have issues.

Colin Fitzpatrick (aka Macduff)
Mechanical Designer
Solidworks 2010 SP 3.1
Dell 490 XP Pro SP 2
Xeon CPU 3.00 GHz 3.00 GB of RAM
nVida Quadro FX 3450 512 MB
3D Connexion-SpaceExplorer

 

[AeroNucDef]

Macduff,
Just had a look and the name of the server has been changed,
It is now called "compA", were before it was just "Drive E"

 

[macduff]

they renamed the server on you?

Colin Fitzpatrick (aka Macduff)
Mechanical Designer
Solidworks 2010 SP 3.1
Dell 490 XP Pro SP 2
Xeon CPU 3.00 GHz 3.00 GB of RAM
nVida Quadro FX 3450 512 MB
3D Connexion-SpaceExplorer

 

[AeroNucDef]

It seems so, the IT guy who changed over the PC must have given the server a new name.

 

[Updraft]

I'll bet you've got a new name for him, too!

- - -Updraft

 

[macduff]

wait, how many folks work at your company and how many SW users are there?

Colin Fitzpatrick (aka Macduff)
Mechanical Designer
Solidworks 2010 SP 3.1
Dell 490 XP Pro SP 2
Xeon CPU 3.00 GHz 3.00 GB of RAM
nVida Quadro FX 3450 512 MB
3D Connexion-SpaceExplorer

 

[AeroNucDef]

There's only me who uses SW, the rest use Auctocad.

One of my work mates has SW installed on his PC, so I checked to see if I cold open the model with his machine, but I still came up with errors. It looks like I'm going to have to spend some time fix all of the problems.

PS. Is there an easy way of detecting which part or mate may be causing the problems. What I mean is that it can be one mate that makes the assembly come up with loads of errors.

 

[SnowCrash]

The first step is to map 'compA' to be drive 'E' To do this, in Windows explorer, right click on the folder on the server that contains your files, select 'map network drive . . .' and pick the 'E:' option and select 'reconnect at startup'
Then be sure E: is in your search path in SW.

--
Hardie "Crashj" Johnson
SW 2010 SP 4.0
HP Pavillion Elite HPE
W7 Pro, Nvidia Quaddro FX580

 

[ctopher]

I have only seen some issues opening 64 bit files on a 32 bit. Over time they were worked out.

Chris
SolidWorks 10 SP4.0
ctopher's home
SolidWorks Legion

 

[macduff]

have the IT guy change the server back to the way it was. it will take forever to fix all your assemblies, parts and drawings.

if not, try this.......

resolve all your parts first before you try fixing your mates. your mate errors might fix themseleves when you resolve your parts.

make sense?

Colin Fitzpatrick (aka Macduff)
Mechanical Designer
Solidworks 2010 SP 3.1
Dell 490 XP Pro SP 2
Xeon CPU 3.00 GHz 3.00 GB of RAM
nVida Quadro FX 3450 512 MB
3D Connexion-SpaceExplorer

 

[SnowCrash]

Colin,
The IT guy did not do anything to him, his folder is just not mapped because it is a new installation. Mapping the drive may fix it.
I run into this because I have also used files from the server.

--
Hardie "Crashj" Johnson
SW 2010 SP 4.0
HP Pavillion Elite HPE
W7 Pro, Nvidia Quaddro FX580

 

[macduff]

got it

Colin Fitzpatrick (aka Macduff)
Mechanical Designer
Solidworks 2010 SP 3.1
Dell 490 XP Pro SP 2
Xeon CPU 3.00 GHz 3.00 GB of RAM
nVida Quadro FX 3450 512 MB
3D Connexion-SpaceExplorer

 

[macduff]

Snowcrash,
Sorry, I get a little defensive when it comes to IT messing with eng stuff. My supervisor finally got a new computer i7, windows 7, 64 bit with 8 gig of memory. Well I found out our IT dept striped off all the software and re formatted it with Windows XP & with a 32 bit system. So you can see why I’m not a big fan of IT depts.

Best,


Colin Fitzpatrick (aka Macduff)
Mechanical Designer
Solidworks 2010 SP 3.1
Dell 490 XP Pro SP 2
Xeon CPU 3.00 GHz 3.00 GB of RAM
nVida Quadro FX 3450 512 MB
3D Connexion-SpaceExplorer

 

[SnowCrash]

Colin, no problemo.

--
Hardie "Crashj" Johnson
SW 2010 SP 4.0
HP Pavillion Elite HPE
W7 Pro, Nvidia Quaddro FX580

 

[Theophilus]

I've had a few assemblies go all FUBAR on my new Win 7 (x64) system when updating from v2007 to v2009 or v2010--but it sounds like you're seeing some different things happening. Did you confirm that all parts were non-lightweight when doing the Pack and Go? How did you use that tool? (Whatever it's worth, I use File > Find References > Copy Files whenever I bump up a top-level assembly/project to a new revision, and copy all the related parts (and drawings) to a new directory. I've never had a problem with exactly this method.)

OT:
SnowCrash, just following up on an unrelated hunch--but do you live in Southern Colorado? Perhaps outside Pueblo? Just wondering.



Jeff Mowry

http://www.industrialdesignhaus.com

A people governed by fear cannot value freedom.