2007 crash crash crash

bob z. just installed swx2007 at home (to test before installing at work). the microsoft dot net framework failed to install and swx CTD's instantly - every time. bob z. knows this doesn't help you, but just thought he would share some of the calamity.

a reboot (or two) and a repair of existing installation AND a critical patch update for m$ dot net still has not resolved this issue.

is product activation at fault? how does good ol' bob z. go about doing the product activation? swx won't stay running long enough to find a button that says, "click me for activation!"

bob z. p.s. what do you do for money, honey? where do you get your kicks?

Someone on the SW corp forum was saying that they were getting the Runtime error in 2007 when they were using a spaceball. Unloading the drivers stopped them. Maybe 3DConnexion needs to get updated drivers for

I don't have a spaceball. nuts.

The first thing I do when trying to decipher stuff like that is to turn off all add-ins and then try loading again.

WT

I already tried that.

I got it to work for awhile by selecting a different config, but now that doesn't work.

Things are griding to a halt, lets see, if I restore my backups and lose 4 days work .... I can make it up over the holiday weekend!!!!!!!

Wayne Tiffany wrote:

You have a repeatable assy - can you send it to me with the parts and I will try it on mine. I have not seen the problem with 2007. Have you Rx'd that file and sent it to your VAR? WT

Go to the task manager and kill process Windows Search Indexer. I have had it cause SolidWorks to crash upon start.

Regards, Corey

RaceBikesOrWork wrote:

Could also be the automatic email feature if you don't use Outlook. I use Mozilla Tbird and sometimes on install the switch gets thrown, even though I tell it not to. You have to go into the registry to turn it off.

New to this game, what is a CTD? Thanks

Never mind, got it, Crash to Desktop, figures

I didn't install the desktop search thing. hmmm..... it just seems like one of those enhancements none of us needed enhanced. I didn't turn on the performance reporting thing. Is anybody using a Microsoft Sidewinder Commander with SW2007? I am going to try to uninstall that. We are gonna try uninstall/clean registry/reinstall SW2007 fresh if that doesn't work, even though that has never fixed any problem in the history of SW.

snipped-for-privacy@gmail.com wrote:

Actually it is more properly CTDT. Search the NG with Google and you will find a lot of them.

snipped-for-privacy@gmail.com wrote:

I'm not an IT guy, and just want to WORK. I have no time to or intention of studying 266 pages or 566 pages of pdfs on how to tweak, reset, edit Registries, use VM on separate partitions, etc. just to keep SolidWorks running half way OK.

Hence, to keep SWks working right w/o problems, I have had to keep my SolidWorks off the internet, and the following is what I do. It has virtually eliminated CTDT.

1. Load a fresh clean XP2 installation on a new hard drive
2. Go online behind a firewall & good malware program like Bit Defender Pro if you must get XP2 updates, and then get off & stay off.
3. I install SolidWorks and the very few utilities I need (MSOffice, SnagIT, Winzip)
4. I don't connect to my network, either, because FireWire hard drives and USB flash keys have made file transfers unnecessary.

This type of procedure means you don't screw up your prior installs or data, so you NEVER screw up existing work in progress, while you test out a new version of SolidWorks.

Sleep Easy -- Bo

RaceBikesOrWork wrote:

give it a rest, jughead, we're sick of your same old story. windows isn't as hard as you say, and mac sucks just as much, it just has less scrutiny because of its tiny market share.