Fix to Constant Crashing in CS4

Question

After reading the scores, if not hundred's of posts about this problem and doing quite a bit of research, I've found the fix.
You need to switch to another product. I'm not being facetious.  Adobe has made it abundantly clear that they have no interest in fixing tough problems like this. I've been in the IT field for 25 years, 10 years with one of the big software/hardware manufacturers and 10 years running my own software development shop. Like Adobe, I don't give away support. But if reports come in that one of my products is crashing, I fix it. It's as simple as that. Since I'm not paid hourly and I have to produce results or I starve, suggestions like; "Reinstall Windows" or "Reformat you hard disk" are not solutions.
Anybody who posts suggestions like "Reinstall Windows" or "Reformat you hard disk" has never had to support themselves by by producing results, could earn a better living or they are simply telling you to go away.
After you done flaming me, and if Adobe allows this post to remain on the forum.  Please respond with your suggestions on what you've found as a good replacement for Dreamweaver CS4.  You can even respond with Dreamweaver CS5, that is if you've beaten it up a lot and find that it is more stable than CS4.
Cheers

Answer 1

Yeah, I'm sure you guys are right.  I fixed it, it only took 4 hours out my workday.  It was a(nother) corrupted file.  It was in one of the Dreamweaver directories, a file that Dreamweaver created and maintains.  I'd tell you which one, but I zapped a whole lot of Dreamweaver private files in several tranches to get at it quickly so I don't know which one it was.
Sorry for not taking the time to describe my environment and all the steps I previously took.  I wasn't looking for an answer, just venting frustration at a vendor who doesn't seem to stand behind their product.
It just sort of ticks me off, that Dreamweaver has a bug that corrupts one of their own files and they don't want to address it.  Oh yeah, they'll step me through trouble shooting after charging me $39 for the privilege.  And before you ask, I'm on a redundant RAID array, UPS with a fresh battery installed 2 weeks ago.  None of the Event Viewer files show any hint of trouble in the OS.  Log files for IIS and SQL Server were all clean also, not that that should have any effect on a code editor.
There are probably thousands of users who haven't had a Dreamweaver corruption problem vs. the few scores who have.  That's too many, but I guess that's just my opinion.
I also guess I'm an impatient b*tch who doesn't believe I should charge my customers to fix my errors and I sort of assumed the folks at Adobe felt the same way.
The ANSWER to the crashing problem is start deleting Dreamweaver config and state files.  Try to guess which ones may store important preferences and vital settings, save them for last and cross your fingers.  Maybe Adobe could see their way clear to publishing a list of what all their config files do so these few scores of unfortunate souls would at least have a roadmap.