Under vista scripts do still work even when the rest of window-eyes does not. I do not believe this is true under xp.
All of your points are valid sam. Wouldn't it be more afishent to do a dump send that dump along and restart window-eyes? This way the user would never even know there was a crash. I think error reports should happen the same way. this is how many major aps are doing things these days. From: Sam bushman [mailto:[email protected]] Sent: Sunday, December 14, 2008 9:15 AM To: [email protected] Subject: Loss of Speech again! Hi all, This is a perfect example of what we have been talking about. I am in outlook express. I try to press enter on a message and loose speech completely. I wait hoping it will come back. It does not. I then try to press ctrl+ backslash and just get a beep from the computer speakers. I then try to redraw the screen insert + backslash to see if it will help ... nothing! I then fire up nvda with ctrl + alt + n. I get nvda talking. Nothing is running ... I must have closed outlook express in the process some how when I had no speech. I then use nvda to see that I am at the desktop and the computer is running perfectly. So, I look at the system tray and yes window eyes is running ... Interesting. Next I press enter on window eyes on the system tray and I hear that window eyes is not responding. So I end the program (an easy task) with speech. Then I exit nvda insert + q I then launch window eyes again ctrl + alt + w. Speech comes back and window eyes is running great again. Now I think well I need to get this info to window eyes to see if we can determin why speech was lossed and why window eyes quit responding out of the blue. I try to send an error report and was told: There are no errors to report. So I am thinking that there are two parts to this. 1. No speech ... what could I have tryed to do to see if I could make speech come back with out shutting down window eyes or rebooting the computer? Some people would say it's the computer you could not have recovered speech ... but, then why was nvda able to run no problem? Since I had nvda I was able to provide much more info ... it was not the computer and it was window eyes that was not responding. Next I was able to end the task (window eyes) with speech and not force a reboot of the machine. You guys who want to just end and relaunch we would have never been able to provide this kind of info. Scripts to do things would have not worked here unless the WE script engine still works even though window eyes is not responding. Any one know if the script part works if the app is locked up and not responding? 2. How can I provide GW with the most info possible in this case? If I had a third party (monitor) piece of software that could watch we to see if it was responding. If I could have had a utility that could take a picture (details about the state of the computer) and send this to gw micro ... we could make lots of progress. Several questions are in order here: 1. What if that utility was to use window eyes services to see if the talker could still speak? What if it asked a question ... did you here your speech say "making sure speech still works during the loss of speech? If you press y in five seconds we can log that speecdh was able to happen. If you don't do any thing we need to think you didn't get speech to respond. If we have speech through this third party app ... then we could ask several more questions. We can have the software determin if window eyes is responding or not. If not a memory dump could take place and we could interrogate the computer to see if any more info could track this down. The biggest part of this is to gather this info while we is running in the problem state. We also need the computer in the problem state in other cases where it's not window eyes. Any ideas from any one on this? thank the lord for nvda. Thanks so much for listening. Sam Bushman __________ Information from ESET NOD32 Antivirus, version of virus signature database 3690 (20081214) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com 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. 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.
