Cory,
Have you tried disabling all scripts? I'm wondering if this might be
caused by something in one of the scripts you have running.
Try turning off all scripting and let it run for a while. Gradually add
scripts back into the mix until you find one which causes the problem.
Of course if you turn off scripting and it still occurs, it isn't the
scripts. <smile>
Just one thing to try.
Don
----- Original Message -----
From: "Cory Samaha" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Saturday, August 09, 2008 3:30 PM
Subject: WE 7.0 Beta 2
Hi,
Just wanted to report some findings with Beta 2. Over all I have to
say I
love it, but there are some quirks that were not there in 6.1.
First, I'm using IE 7 with Windows Vista Ultimate SP1. Browse mode
seems to
go silent at random. Many times it will happen right after I have
gone to a
new page by pressing control-o, typing in a web address and pressing
enter.
Some time while the page is loading, WE goes silent. Like I said this
doesn't happen all the time, which makes it hard to give exact steps.
When
it does happen though, I have no speech within IE7. As soon as I
alt-tab
out of IE7 to another application Window-Eyes comes back to life, but
alt-tabbing to internet explorer makes it go silent again. Closing
and
relaunching WE seems to do the trick. Note I also was having this
problem
in Beta 1 but I thought I saw that other people had reported that
issue.
Second, WE gets into a state where when I'm tabbing through links on a
web
page, it seems to want to constantly refresh the browse mode buffer.
It has
nothing to do with a dynamically changing page and as long as I'm just
arrowing through regular text it seems fine. But when I come across
links
it just wants to keep refreshing the buffer, which makes it very hard
to
just tab through the links. This problem also seems to occur totally
at
random but also happens in IE7 under Windows Vista. Again, closing
and
restarting WE seems to solve this problem as well. I really wish I
could
figure out how to reproduce these problems 100% of the time so I could
help
more, but I haven't noticed much of a pattern to when these problems
occur
but it has happened a couple times now already with Beta 2. Is anyone
else
seeing these issues?
There is actually one more slight problem that I don't consider to be
a big
deal but thought I would mention it here anyway. I still notice that
once
in a while Beta 2 will keep chatting for a few seconds after shutting
down
Window-Eyes. I'm not sure if that's really a problem or not but to me
it's
not quite as annoying as some of the other problems.
These are my findings so far. If I can help more in reproducing these
problems let me know. Hopefully it's not just something with my
machine.
--Cory
__________ Information from ESET NOD32 Antivirus, version of virus
signature
database 3342 (20080809) __________
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.
__________ NOD32 3342 (20080809) Information __________
This message was checked by NOD32 antivirus system.
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.
