Hi well first off gw micro can only debug window-eyes problems.  We cannot
assume just because you lost speech here that it is a window-eyes problem.
I have seen this time and time again where a program will stop working and
there is no speech.  For example the other day while running jfw I closed
outlook 2007 and lost speech  and braille nothing I could do would bring it
back.  So I tried using the task manager to end the outlook  process  bam my
speech came back.  Today I was running window-eyes and I lost speech.  I
found after doing some research that dragon had crashed.  This is more of a
windows problem then a screen reader problem and I am really not sure what
gw micro can do about it. 

 

From: Sam bushman [mailto:[email protected]] 
Sent: Wednesday, June 10, 2009 6:16 PM
To: [email protected]
Subject: WE 7.1 Beta 1

 

Hi guys,

 

I have been running the beta with great results.

However, I just had a hard crash.

I lost speech in ie8 on winxp pro service pack 3.

I had my sighted son exit all running apps ie8 oe etc.

Then I still had no speech.

My son then tried to click on the taskbar we icon and he couldn't get it to
respond.

I tried to press ctrl-backslash so I could exit properly and no luck.

Finally even though the computer was responding to him ... I could not get
speech squared away to start talking again.

I tried to relaunch speech but, was told we was already running ... not in
speech my son was reading the screen.

Finally he just had to restart the computer.

Speech came up with the reboot of the computer.

I then tried to see if there was an error report to send to gw but, was told
no error reports.

So the upshot, we7.1 beta 1 is much more responsive and lots of things are
better.

It's more stable than any version I have had thus far.

However, the hard lockups / loss of speech with no way to provide any info
to gw or our selves is still a huge problem.

So, hard lockup on beta one with no info of value to report.

Why the crash ... I have no idea.

What app at fault ... I have again no idea.

When the computer was shutting down in the restart ... windows did say an
app was not responding and shutting down.

but, since windows didn't show what app ... again no valueable info.

 

If gw had a way to send in a report of the computers state or something like
that we may get some info but, as it is now ... this can happen over and
over and I will not be able to provide any thing else of  value.

We are right back to some of my earlier posts on these issues.

We need better ways to recover from the loss of speech ... we need better
tools to report back to gw with info that may help them resolve issues.

 

I am just greatful that I have sighted family memebers who are available to
help from time to time.

If I were alone or didn't have that help like others on the list ... I guess
the only solution would have been to yank the plug ... plug it back in and
pray speech and the computer reboots.

 

Thanks

Sam

 

 

 
 
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.


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.

Reply via email to