You aren't totally understanding because the purpose isn't trying to use
multiple screen readers at the same time. The purpose is merely trying to
alternate screen readers. When you try to close one and then open another
you get a bleeping kind of sound so you try to open another to try and
understand what is causing the problem. The fact of the matter is that you
can see different pages and different programs in a different way. Some
programs function better with one screen reader over another one.
----- Original Message -----
From: "Sunshine" <[email protected]>
To: "Stanley Littrell" <[email protected]>; "Bob Tinney"
<[email protected]>
Cc: <[email protected]>
Sent: Wednesday, February 17, 2010 7:38 AM
Subject: Re: when screen readers refuse to die
why would you want to use them at the same time anyway?
just wondering.
----- Original Message -----
From: "Stanley Littrell" <[email protected]>
To: "Bob Tinney" <[email protected]>
Cc: <[email protected]>
Sent: Wednesday, February 17, 2010 9:24 AM
Subject: Re: when screen readers refuse to die
This is the exact problem that I have.
----- Original Message -----
From: "Bob Tinney" <[email protected]>
To: "Stanley Littrell" <[email protected]>; "GW Micro"
<[email protected]>
Sent: Wednesday, February 17, 2010 7:21 AM
Subject: when screen readers refuse to die
I have W E, system access, and NVDA on my Asus netbook. I've noticed a
software conflict between SA and W E. If you try to load W E while SA is
loaded, I get a hook erryr. If I try to load SA while W E is running, SA
refuses to load. W E and SA do not llike to run together.
Bob Tinney, K8LR, [email protected]
Skype, bobtinn
Life is full of challenges, that's what makes it interesting!
----- Original Message -----
From: Stanley Littrell
To: [email protected]
Sent: Wednesday, February 17, 2010 9: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.
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.
