2006 crashing

[rfus]

I love spline polygon controls, loft section additions, sketch blocks, and new windows style feature manager select, but with that said....

I have crashed every day on 2006. Today it was going to the hole wizard. Yesterday it was using a midpoint selection filter with a feature. The day before it was twice, using the feature manager drag select and then when I was using offset surfaces. I have lost lots of work every time. In 2005 I didn't feel the need to save after every thing I did because it was fairly stable. I'm going to go back to 2005 cause this is costing me to much time........

and they even took away the classic unhandled error and gave us a new gui for when we crash...great...

Rx gives all checks, XP SP2, NVidia FX 3000, 3.4GHz, 2Gig RAM ... yes my temp is clean....

It appears I am the only one with 2006 issues?

 

[Theophilus]

You're probably one of the first to begin using 2006 for production tasks from the download. I've downloaded 2006 and am eager to begin using the new stuff, but I'm considering a clean break and new install when I finally make the switch--I don't think I'll keep 2005 on the same machine with 2006, since I'm getting somewhat strange behavior from 2005 lately.

I hope you backed up your files before converting to 2006.


Jeff Mowry

http://www.industrialdesignhaus.com

Reality is no respecter of good intentions.

 

[rfus]

and to make matters worse my pointer is now stuck as the zoom tool pointer....where is my arrow...weird....

 

[ctopher]

Check to see you have the latest video card driver.

Chris
Sr. Mechanical Designer, CAD
SolidWorks 05 SP3.1 / PDMWorks 05
ctopher's home site (updated 06-21-05)
FAQ559-1100
FAQ559-716

 

[rfus]

yup

 

[ctopher]

Then try Repair or reinstall.

Chris
Sr. Mechanical Designer, CAD
SolidWorks 05 SP3.1 / PDMWorks 05
ctopher's home site (updated 06-21-05)
FAQ559-1100
FAQ559-716

 

[PDMAdmin]

I had similar crashing issues when I went from SW2004 to 2005. Turned out there were several causes, but the primary culprit was that I hadn't completely uninstalled 2004. Read Scott's article about uninstalling SolidWorks in the FAQ section. In particular, what eliminated most of my crashes was the part about cleaning out the registry.

 

[CADGemini]

When you installed SW2006 did you tell it to use a seperate shared directory or did you use the shared directory that SW2005 was already using? If you used the same one then you will experience many conflicts.

Best thing is to do what PDM Admin suggested and do a clean uninstall and re-install. Then when you re-install each version make sure you point them to their own folders such as "SW2005" or "SW2006" doing this will ensure that the versions are completly seperate from each other.

Best Regards,
Jon

Challenges are what makes life interesting; overcoming them is what makes life meaningful.

Solidworks 2005 SP3.1

 

[SBaugh]

Did you install with your AV on? Someone recently told me that the message didn't appear to them to turn off their AV, so they figured it was OK to leave the AV running. That's not ture, whether it comes up or not you need to shut it down.

Did you upgrade your SW05 to SW06? I bet you did, since you obvisously don't have both running on your machine. (You can do that however, and should before going Production with a new major version). You should never do an upgrade, always do a new install of a major version.

To have 2 SW installed on the same drive you must first pick New install and then simply change the default path of the SW install to say something else: C:\Program files\Solidworks06

And if the above fails a clean uninstall and reinstall is in order.

Regards,

Scott Baugh, CSWP

http://www.scottjbaugh.com

faq731-376

 

[rfus]

AV was off, i hate AV. I ran 04 and 05 together for a while and I was having conflicts with toobox and photoworks common files, even though the paths were specified, so when I made the decision to go to 06 I wiped out 05 clean, and my 06EV, hit the regedit, and made quite certain I was good to go.

I obtained an error at the end of the 06 install, 1722- something about unable to install certain components, but after getting a hold of the var, SW told them it was something to do with network licencing, which does not apply to me, so they told me to not worry about it.

But, I just finished and 11 hour session while running two sessions of 06 on my dual monitors with no problems, so I am a little more optomistic today.

Thanks for the advice.

rfus

 

[SBaugh]

1722 can also be a admin privileges, if you don't have rights to a folder, etc... then you will get that error as well.

Scott Baugh, CSWP

http://www.scottjbaugh.com

faq731-376