h a l f b a k e r y
What's a nice idea like yours doing in a place like this?
add, search, annotate, link, view, overview, recent, by name, random
news, help, about, links, report a problem
or get an account
For some unknown reason, my computer will no longer run Solid Works (even after reinstalling the OS). It give me this pleasant and useless error:
sldworks.exe has generated errors and will be closed by Windows.
You will need to restart the program.
An error log is being created.
so now I know it's generated errors, and that somewhere on my 4 hard disks is a small file, with an unknown name, that presumable will tell my why my program won't work. Well, a quick search by date, followed by a rummage through all the normal error log places, reveals that my computer has just lied to me.
What I am proposing, is a program that could be run before trouble programs, and will map the memory and calls that the trouble program makes, then tells me in plain English (or whatever language you prefer):
SolidWorks is broke! It doesn't like a call made to kernel32.dll!
Or something similar. Then I would know that something I installed changed kernel32.dll and I just have to replace that file from the install disk.
I hope this is baked and someone can tell me where to find this magic program!
Moved from Goff's anotation [Katt, Oct 04 2004]
Please log in.
If you're not logged in,
you can see what this page
looks like, but you will
not be able to add anything.
Description (displayed with the short name and URL.)
||I have good and bad news for you.
Here they are. I haven't seen this
program either. So, I guess that
gets you a croissant.
||Later versions of that program
could fix the problem for you. I
think there are some programs
like conflict catcher.
||It's called Norton Crashguard (part of Norton SystemWorks), I have it on my computer at home. it intercepts crashes and stops them (sometimes) from crashing windows, as well as helping you recover.
However, it only works for Windows 98. Don't know if the functionality is built in to later Systemworks, but check out Symantec.com to find out.
||OK, I looked into SystemWorks, and it doesn't seem to follow what I want in several way:
1) It's now called GoBack and requires the program to have worked at least once since installing SystemWorks
2) I am wanting something that only needs to run while excecuting a problem program (SolidWorks uses enough system recources by itself, it doesn't need something else to help it slow my computer down)
3) SystemWorks seems to throw in a lot of things that I neither want nor need (Antivirus, Disk Checking etc.), and I have ussually found that "all-in-one" programs tend not to perform very well (if the program worked, you wouldn't need to hide it inside a bigger package).
4) If I wanted roll back features and a slow computer, I would install Windows ME or Windows XP (I would prefer Linux Mandrake, but it won't even think of running SolidWorks, even with Wine)
5) Under Win2K, most crashes don't take the whole computer down, just gives a stupid error message and then exits the program
||If I come off sounding mean, I appologize, it's not my intention (I really HATE Symantec products). I'm putting a link to Symantec so that someone may be able to correct me if I'm wrong.
||I know that I installed some peice of software that makes SolidWorks not work. I don't know what it is. That's the point of this idea. I did check the event viewer, (//followed by a rummage through all the normal error log places//) all three categories, the last entry is something about my cdrom not reading a disk from before I reinstalled SolidWorks and after I reinstalled the OS.
BTW, mine is under control panels, I'm too lazy to set it to show under programs.
||I just want an error message or a reliable log or a program to tell me exactly what isn't working so I can fix it. That's all.
||"Please, Oh great God of the computer, I sacrifice this tasty power supply in your name. Please make my computer function..."