Hello all: Saw the several messages with the subject line "WE 7.1 Stability problems." I guess the saying, "One man's trash is another's treasure" may be applicable. Under 7.01 (and pretty much every earlier version) I could count on lock-ups at least daily. Rarely would it be more frequent than 3 times a day, but 2 times was not uncommon. I had about the same experience with JFW, though I remember when I switched to WE about 15 months ago i felt more stable. NOW, since I've been using WE 7.1, I haven't crashed a single time, and that's using two separate ThinkPads and remote access using Citrix. In fact, I cannot remember ever, ever being this stable. So, what's the difference? I previously used DecTalk Access 32, not because I liked it, but because I didn't have an Eloquence option. It wasn't a big deal, but I do prefer Eloquence. It turns out that my synth.ini file was corrupted. I deleted the GW Micro folder underDocuments and Settings (and about 7 other folder and subfolder names) and then started WindowEyes fresh. Well, I lost all my settings. I thought that would be a big problem, but it really wasn't. Now, I use Eloquence, and I haven't crashed in 2 weeks. I have no idea whether this will work for anyone else or whether what I did to fix one problem even had an effect, but creating new, completely fresh set files seems to have made nothing short of a revolutionary difference for me. This is just my experience. I should think someone on the list with more expertise than me could chime in on whether this strategy could be helpful for others.
If you reply to this message it will be delivered to the original sender only. If your reply would benefit others on the list and your message is related to GW Micro, then please consider sending your message to [email protected] so the entire list will receive it. All GW-Info messages are archived at http://www.gwmicro.com/gwinfo, and can be searched through and sorted using the search form at the bottom of the page. If you wish to unsubscribe from this list, send a message to [email protected] and include leave gw-info in the body of the message.
