Thanks for mentioning the key combination that you did. That is the
combination that I forgot about.
I have waited for as much as 20 or 30 seconds with the same results. I will
get the sound script that you mentioned.
Thanks for your quick response.
----- Original Message -----
From: Marvin Commerford
To: Stanley Littrell
Sent: Wednesday, February 17, 2010 7:11 AM
Subject: Re: when screen readers refuse to die
Hi. I have similar configuration but I do not have System Access. I will
use NVDA, JFW demo and primarily WE. I use ctrl-insert-f4 to close WE and
answer the prompt to close it. I also have the WE sounds script running so I
get the feedback that the dialog is working. I don't have the problem you
describe. I wonder if you're trying to switch screen readers too quickly.
Close 1 and wait a few seconds before bringing up the alternative one you want.
I've seen this with JFW as well but you really have to make sure where you are
when you start another sr.
----- Original Message -----
From: Stanley Littrell
To: [email protected]
Sent: Wednesday, February 17, 2010 8:56 AM
Subject: when screen readers refuse to die
Greetings fellow listers
I have three screen access programs on my system. I'm using windowsxpsp3
with the great scripting functionality with WindowEyes. I am also using System
Access and NVDA. I have the WindowEyes kill WinEyes script installed. When I
shut down WE it doesn't always work totally. If I use the control ult f4
conbination to try to kill WE it doesn't always go away. When I do
simultaneously use another screen reader I sometimes hear the unable to set
hook error and when I hit o.k. WE can restart. The problem happens when I stop
WE and often happens when I try to restart WE after using another screen access
program. In other words, WE sometimes refuses to die and it sometimes refuses
to start. When I try to restart we I am often told that WE is already is
running.
While I'm an unabashed supporter of WE since 1994 I do like other products
for different reasons.
I'm not sure what has changed because I haven't always had this problem.
Any help would be appreciated.
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.
GW-Info messages are archived at http://www.gwmicro.com/gwinfo. You can manage
your list subscription at http://www.gwmicro.com/listserv.
__________ Information from ESET NOD32 Antivirus, version of virus signature
database 4874 (20100217) __________
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.
GW-Info messages are archived at http://www.gwmicro.com/gwinfo. You can manage
your list subscription at http://www.gwmicro.com/listserv.
