I am going to explain my purpose for a final time. The purpose isn't using
two screen readers at the same time. When you close one screen reader and
then try to open an alternative because that alternative sees something in a
better way and you get the bleeping sound you want to understand what is
causing the problem. You just know that there is some sort of problem that
is prohibiting you from performing a certain task. There are things that
are easier to do with one screen reader over another. Once again, we aren't
trying to run two screen readers at the same time. We are just trying to
get auditory feed back to understand what is going on.
----- Original Message -----
From: "Donald E. Bowen, Jr." <[email protected]>
To: "'Sunshine'" <[email protected]>
Cc: "GW Micro Support List" <[email protected]>
Sent: Wednesday, February 17, 2010 7:47 AM
Subject: RE: when screen readers refuse to die
I too have to wonder about the logic here. I can appreciate a backup in
case WE stops functioning properly and you can not afford a hard boot due
to
failure to follow the old rule of save early and save often, something I
am
frequently guilty of myself, . Other than that, scenario described at the
start of this thread makes no sense and seems to be begging for trouble.
Keep in mind the wise old acronym
K I S S
Good luck!
Donald E. Bowen, Jr.
Music for Sight
-----Original Message-----
From: Sunshine [mailto:[email protected]]
Sent: Wednesday, February 17, 2010 10:38 AM
To: Stanley Littrell; Bob Tinney
Cc: [email protected]
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.
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.
