Comments on: SolidWorks Crashes & Slowdowns: It’s Your Fault http://www.jeffmirisola.com/2009/04/solidworks-crashes-slowdowns-its-your-fault/ SolidWorks Tips, Tricks and Partner Reviews Thu, 15 Dec 2011 02:20:17 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: JeffMirisola http://www.jeffmirisola.com/2009/04/solidworks-crashes-slowdowns-its-your-fault/comment-page-1/#comment-624 JeffMirisola Fri, 25 Dec 2009 19:23:20 +0000 http://www.jeffmirisola.com/?p=329#comment-624 I'm guessing that you're less than satisfied, Ed. With regards to your video card, while it's approved, is the driver? If you're using a branded system (Dell, HP, etc), you'll need to choose the the brand as the manufacturer versus nVidia. When replacing the video driver, be sure to uninstall the old one before installing the new one. <br>You don't go into any specifics about your other problems. If you'd like some help, feel free to post them. <br>I completely appreciate your stand on maintenance fees. It's been a point of contention for years. I would assume that the reseller you purchased from informed you that you wouldn't be eligible for service packs if you chose not to get maintenance. They should also have informed you that you are eligible for an SP if it fixes a critical error in the software.<br>I hope things take a turn for the better, Ed. <br><br>Jeff <br><br>-----<br>Sent from mBox Mail<br>Hotmail for iPhone and iPod Touch<br><a href="http://www.fluentfactory.com/mboxmail" rel="nofollow">http://www.fluentfactory.com/mboxmail</a><br><br>________________________ I'm guessing that you're less than satisfied, Ed. With regards to your video card, while it's approved, is the driver? If you're using a branded system (Dell, HP, etc), you'll need to choose the the brand as the manufacturer versus nVidia. When replacing the video driver, be sure to uninstall the old one before installing the new one.
You don't go into any specifics about your other problems. If you'd like some help, feel free to post them.
I completely appreciate your stand on maintenance fees. It's been a point of contention for years. I would assume that the reseller you purchased from informed you that you wouldn't be eligible for service packs if you chose not to get maintenance. They should also have informed you that you are eligible for an SP if it fixes a critical error in the software.
I hope things take a turn for the better, Ed.

Jeff

—–
Sent from mBox Mail
Hotmail for iPhone and iPod Touch
http://www.fluentfactory.com/mboxmail

________________________

]]> By: edlindsley http://www.jeffmirisola.com/2009/04/solidworks-crashes-slowdowns-its-your-fault/comment-page-1/#comment-623 edlindsley Fri, 25 Dec 2009 09:47:51 +0000 http://www.jeffmirisola.com/?p=329#comment-623 I became a new customer early in 2009, spending $7000 on SolidWorks Premium. I received the Service Pack 1 version – buggy but tolerable. Time passed and SP2 was announced. Perhaps now my SolidWorks-approved Quadro graphics card will be usable and I will not be crashing every few hours!

I proceeded with great expectation to the SolidWorks Customer Portal, my valid serial number in hand. Alas my serial number was not recognized. It seems I don’t really exist as a customer from the Dassault Systemes perspective – sorry, subscribers only.

Ah, corporate greed at work again! This marketing coercion is very clever: Subscribe or face perpetual software bugs and permanent SolidWorks community rejection! With licensing that precludes selling my SolidWorks copy in disgust, the only sane decision should be to send Dassault another $2000 for the subscription. And I have been pondering that sane decision as the months slipped by.

At this point late in 2009 I am facing a moral and practical dilemma: bow to their superior guile and send Dassault $2500 for a subscription – the extra $500 being a punishment for my prior failure to subscribe – or continue to endure SP1 in software OpenGL mode.

I will admit to seriously considering the $7000 in SolidWorks Premium a bad investment, chucking the SP1 media in the can, and going back to Inventor and its free service packs. At least Autodesk accepts financial responsibility for their software bugs rather than placing that burden upon their customers.

And since I am – at least legally – a SolidWorks customer in good standing, I can purchase an Autodesk competitive trade up to Inventor Professional Suite 2010 – with subscription included – for $5790. It just might be worth the money.

]]> By: SolidWorks blog » Píše Jeff Mirisola “Padá vám Solidworks?” (série ?lánk?) http://www.jeffmirisola.com/2009/04/solidworks-crashes-slowdowns-its-your-fault/comment-page-1/#comment-496 SolidWorks blog » Píše Jeff Mirisola “Padá vám Solidworks?” (série ?lánk?) Fri, 17 Jul 2009 13:35:11 +0000 http://www.jeffmirisola.com/?p=329#comment-496 [...] Úvod [...]

]]> By: Teo http://www.jeffmirisola.com/2009/04/solidworks-crashes-slowdowns-its-your-fault/comment-page-1/#comment-571 Teo Tue, 23 Jun 2009 22:54:54 +0000 http://www.jeffmirisola.com/?p=329#comment-571 Solidworks Rx has a system maintenance option that alows the user to clean out temp. files and defrag. the disc. running the system maintenance weekl seems to be the best way to prevent the weekly/daily crashes that i experince. Solidworks Rx has a system maintenance option that alows the user to clean out temp. files and defrag. the disc. running the system maintenance weekl seems to be the best way to prevent the weekly/daily crashes that i experince.

]]> By: Teo http://www.jeffmirisola.com/2009/04/solidworks-crashes-slowdowns-its-your-fault/comment-page-1/#comment-483 Teo Tue, 23 Jun 2009 15:54:54 +0000 http://www.jeffmirisola.com/?p=329#comment-483 Solidworks Rx has a system maintenance option that alows the user to clean out temp. files and defrag. the disc. running the system maintenance weekl seems to be the best way to prevent the weekly/daily crashes that i experince. Solidworks Rx has a system maintenance option that alows the user to clean out temp. files and defrag. the disc. running the system maintenance weekl seems to be the best way to prevent the weekly/daily crashes that i experince.

]]> By: JeffMirisola http://www.jeffmirisola.com/2009/04/solidworks-crashes-slowdowns-its-your-fault/comment-page-1/#comment-417 JeffMirisola Mon, 01 Jun 2009 15:47:48 +0000 http://www.jeffmirisola.com/?p=329#comment-417 Thanks, Brian.<br>Yeah, I've received a bit of flak, but it's no big deal. People seem to have the unrealistic expectation that 3D CAD should be perfect in every way. It never ceases to amaze me how they can deny it might actually be user error in one way or another, even when presented with facts and data. <br><br>Jeff Thanks, Brian.
Yeah, I've received a bit of flak, but it's no big deal. People seem to have the unrealistic expectation that 3D CAD should be perfect in every way. It never ceases to amaze me how they can deny it might actually be user error in one way or another, even when presented with facts and data.

Jeff

]]> By: Brian http://www.jeffmirisola.com/2009/04/solidworks-crashes-slowdowns-its-your-fault/comment-page-1/#comment-416 Brian Mon, 01 Jun 2009 15:26:24 +0000 http://www.jeffmirisola.com/?p=329#comment-416 This is a great series, Jeff. It looks like you are catching a lot of flak for it from folks who have gotten their feelings hurt, but as the old saying goes, "the truth hurts".<br><br>Based on my experience working as an engineer and CAD admin (with SolidWorks AND Inventor/AutoCAD), I can personally say that a LOT of problems folks have with the software is definitely based on their computer configuration, implementation, and/or modeling practices.<br><br>Keep 'em coming!<br><br>-b This is a great series, Jeff. It looks like you are catching a lot of flak for it from folks who have gotten their feelings hurt, but as the old saying goes, “the truth hurts”.

Based on my experience working as an engineer and CAD admin (with SolidWorks AND Inventor/AutoCAD), I can personally say that a LOT of problems folks have with the software is definitely based on their computer configuration, implementation, and/or modeling practices.

Keep 'em coming!

-b

]]> By: JeffMirisola http://www.jeffmirisola.com/2009/04/solidworks-crashes-slowdowns-its-your-fault/comment-page-1/#comment-413 JeffMirisola Thu, 28 May 2009 11:27:18 +0000 http://www.jeffmirisola.com/?p=329#comment-413 Bob,<br>Believe me, I appreciate your frustration. Just for the record, I'm not affiliated with SolidWorks, I just write a blog that deals with the software.<br>As the software has matured, so have computers and their related hardware. For SolidWorks to be able to document "correct installation" for every possible combination of hardware and software would be impossible. That's why others, like me, write about "best practices". For every user who experienced major problems, there were numerous users who didn't. While some of the problems do prove out to be bugs, many are environmental variables. <br>I seem to have offended some people with the title of this series, which wasn't my intention. Bob,
Believe me, I appreciate your frustration. Just for the record, I'm not affiliated with SolidWorks, I just write a blog that deals with the software.
As the software has matured, so have computers and their related hardware. For SolidWorks to be able to document “correct installation” for every possible combination of hardware and software would be impossible. That's why others, like me, write about “best practices”. For every user who experienced major problems, there were numerous users who didn't. While some of the problems do prove out to be bugs, many are environmental variables.
I seem to have offended some people with the title of this series, which wasn't my intention.

]]> By: bob http://www.jeffmirisola.com/2009/04/solidworks-crashes-slowdowns-its-your-fault/comment-page-1/#comment-411 bob Wed, 27 May 2009 19:59:23 +0000 http://www.jeffmirisola.com/?p=329#comment-411 Surely as the paying customer the software should be stable and usable. All information for correct installation should be state by solidworks and not blamed on the customer that has little knowledge of software that conflicts, .net ect. We are designer not computer experts.<br><br>I have experienced major problem with 08 before SP4 and similar problems with 09 before SP3. This would suggested that it is bugs in the software and not user error that is causing the problem. We all use the program for commercial use and the key functionality is to obtain a 3d model for manufacture or a drawing. Therefore i think you guys need to seriously consider the use of the software. Improvement to the functionality is great but at the end of the day the software does the same as it did 5 years ago. As designers working on large projects with tight time scale. First a foremost we require stabilty!!!!!!!!!!! Surely as the paying customer the software should be stable and usable. All information for correct installation should be state by solidworks and not blamed on the customer that has little knowledge of software that conflicts, .net ect. We are designer not computer experts.

I have experienced major problem with 08 before SP4 and similar problems with 09 before SP3. This would suggested that it is bugs in the software and not user error that is causing the problem. We all use the program for commercial use and the key functionality is to obtain a 3d model for manufacture or a drawing. Therefore i think you guys need to seriously consider the use of the software. Improvement to the functionality is great but at the end of the day the software does the same as it did 5 years ago. As designers working on large projects with tight time scale. First a foremost we require stabilty!!!!!!!!!!!

]]> By: Jeff Mirisola http://www.jeffmirisola.com/2009/04/solidworks-crashes-slowdowns-its-your-fault/comment-page-1/#comment-406 Jeff Mirisola Tue, 26 May 2009 15:55:22 +0000 http://www.jeffmirisola.com/?p=329#comment-406 Colin, By "working across the network", I meant opening and closing part assembly files across the network, especially assembly files. However, it's been pointed out to me by Anna Wood that it's not as much of an issue as it used to be. While I still refrain from it, it can be done if your network is robust enough. I'd still refrain from recommending it. Pinging the network, while having the multi-user environment enabled, isn't nearly as taxing on your system as actually working across the network. One thing to note: The stuff I talk about in <em>SolidWorks Crashes & Slowdowns</em> are more guidelines than hard and fast rules. Colin,
By “working across the network”, I meant opening and closing part assembly files across the network, especially assembly files. However, it’s been pointed out to me by Anna Wood that it’s not as much of an issue as it used to be. While I still refrain from it, it can be done if your network is robust enough. I’d still refrain from recommending it.
Pinging the network, while having the multi-user environment enabled, isn’t nearly as taxing on your system as actually working across the network.
One thing to note: The stuff I talk about in SolidWorks Crashes & Slowdowns are more guidelines than hard and fast rules.

]]>