The GW-Info list is a discussion list, which can be very active with many messages per day. Any subscriber of the GW-Info list has the ability to post on-topic messages.
From:
"Karyn Campbell" <karyn1421@wowway.com>Subject:
RE: window-eyes quits againDate:
Fri, Sep 27, 2013 9:58:41 amIf you want any help from anyone, you MUST give system specs. Otherwise you
won't get answers and will be seen as a chronic complainer.
My husband is a developer by training and has told me that software can be
tested and tested and tested some more but invariably bugs are found once it
hits the street.
There are many things that could cause this and GW Micro cannot test in
absolutely every scenario because everyone uses WE in different situations,
with different software and under different connection scenarios.
Do I like the silence at times? No but I understand the complicated nature
of software development.
Again see my signature for an example of suggested system specs.
Karyn Campbell, Illinois USA, karyn1421@wowway.com
Using WE 8.3on Toshiba laptop running Windows 7home premium 32-bit with
Office 2007 and IE 8 as well as Acer netbook running Windows 7 home premium,
64-bit with Office 2007 and IE 9 and Microsoft Security Essentials on both
machines.
-----Original Message-----
From: Jed Barton [mailto:jedbarton@gmail.com] On Behalf Of Jed Barton
Sent: Friday, September 27, 2013 7:56 AM
To: gw-info@gwmicro.com
Subject: window-eyes quits again
Hey guys,
Yet still more problems with window-eyes very very unstable.
These random shutdowns for no reason are completely unacceptable. What
makes no sense which is very concerning is there is physically no way for me
to diagnose any of it. No viruses, no spyware, this is a clean machine.
This morning as an example, I was just arrowing through outlook messages,
when I get no speech. I arrow up to a message and speech just stops, and
the only way to get anything back is to start nvda which quite frankly seems
to be more reliable than window-eyes. It's sad to say that, but it's the
truth.
Guys, what can be done? Doesn't all this stuff get tested in beta? I know
I'm not the only person having reliability issues. Truthfully, as the new
versions come out, the worse the reliability has gotten.
Random shutdowns, no speech, etc, I could go on and on. This isn't on just
1 computer either, multiple machines.
Is there any sort of log that is kept anywhere that could help you diagnose
the problems.
I'm frustrated, cause it's costing me minutes every day dealing with this
garbage, when I could be working and being productive.
Another very odd thing that just doesn't make any sense. When window-eyes
stops speaking, I'll start nvda, and that seems to send a jumpstart command
to window-eyes cause it magically starts working again. That makes no sense
what so ever.
At that point I will exit window-eyes, and hit the command to re-start it.
Then I get the ding dong sound, and it says window-eyes is already running.
How can it be running if it just shut it down?
Any ideas guys? This is getting very old.
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
gw-info@gwmicro.com 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 gw-info@gwmicro.com 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.
won't get answers and will be seen as a chronic complainer.
My husband is a developer by training and has told me that software can be
tested and tested and tested some more but invariably bugs are found once it
hits the street.
There are many things that could cause this and GW Micro cannot test in
absolutely every scenario because everyone uses WE in different situations,
with different software and under different connection scenarios.
Do I like the silence at times? No but I understand the complicated nature
of software development.
Again see my signature for an example of suggested system specs.
Karyn Campbell, Illinois USA, karyn1421@wowway.com
Using WE 8.3on Toshiba laptop running Windows 7home premium 32-bit with
Office 2007 and IE 8 as well as Acer netbook running Windows 7 home premium,
64-bit with Office 2007 and IE 9 and Microsoft Security Essentials on both
machines.
-----Original Message-----
From: Jed Barton [mailto:jedbarton@gmail.com] On Behalf Of Jed Barton
Sent: Friday, September 27, 2013 7:56 AM
To: gw-info@gwmicro.com
Subject: window-eyes quits again
Hey guys,
Yet still more problems with window-eyes very very unstable.
These random shutdowns for no reason are completely unacceptable. What
makes no sense which is very concerning is there is physically no way for me
to diagnose any of it. No viruses, no spyware, this is a clean machine.
This morning as an example, I was just arrowing through outlook messages,
when I get no speech. I arrow up to a message and speech just stops, and
the only way to get anything back is to start nvda which quite frankly seems
to be more reliable than window-eyes. It's sad to say that, but it's the
truth.
Guys, what can be done? Doesn't all this stuff get tested in beta? I know
I'm not the only person having reliability issues. Truthfully, as the new
versions come out, the worse the reliability has gotten.
Random shutdowns, no speech, etc, I could go on and on. This isn't on just
1 computer either, multiple machines.
Is there any sort of log that is kept anywhere that could help you diagnose
the problems.
I'm frustrated, cause it's costing me minutes every day dealing with this
garbage, when I could be working and being productive.
Another very odd thing that just doesn't make any sense. When window-eyes
stops speaking, I'll start nvda, and that seems to send a jumpstart command
to window-eyes cause it magically starts working again. That makes no sense
what so ever.
At that point I will exit window-eyes, and hit the command to re-start it.
Then I get the ding dong sound, and it says window-eyes is already running.
How can it be running if it just shut it down?
Any ideas guys? This is getting very old.
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
gw-info@gwmicro.com 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 gw-info@gwmicro.com 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.
