I had the same problem of a script, the windows update script to be exact,
throwing my computer into a circle in which there was no speech. Eyes using
the mouse could not extricate me. I had to power down the computer, 3 times
in all, in order to get into window eyes quickly before the update took
over, unload the update script, then window eyes stopped talking, the script
had begun and tried to finish running, and the final power down and reboot
got me back to window eyes functioning. It's nice people now have improved
Italian for the script assuming they want this, but it raised all kinds of
hell with my computer and I don't actually need my script to be able to
handle Italian. My solution was and is to permanently remove this script.
I'm sure I'll hear about updates being available here on the list.
I am particularly disquieted by the fact that the script by default
automatically checks to see if there is an update for itself even as window
eyes first loads and this time actually somehow took over and eliminated
speech. If nothing else, a delay should be built in to allow everything to
be settled before the script takes an action. One would have time to stop
the script before it gets into a loop disabling speech, and more things
should have settled on the computer reducing the chances of conflicts.
Several things happen when the computer first boots, byres checkers look for
updates, other on and off net actions are taking place, and I think that if
the computer's timing is a bit off, all kinds of problems can result.
Ron Denis
----- Original Message -----
From: "Larry" <[email protected]>
To: "GW Micro" <[email protected]>
Sent: Wednesday, May 06, 2009 6:27 PM
Subject: WE 7.01 crashing when script update Alert opens
Hello there. When it comes to my situation, I'll give all the details
that I can, but since the problem occurs as Window-Eyes launches, I am a
bit limited as to the feedback that I am receiving.
What happens is this.
1. When the computer has launched Windows I start Window-eyes.
2. The first thing I hear at this point is the sounder that indicates that
a script needs updating.
3. The next thing I hear is the sounder which indicates that something
somewhere has failed. I can't say what, because Window-eyes does not say a
word through this process.
4. I restart or reset the computer, repeat steps 1 and 2, and the above
described scenario occurs once again.
With no speech to indicate what is going on, I can't go into greater
detail. All I know is that some problem pops up when I am notified that
whatever the script in question happens to be wants to update.
Meanwhile, other screen readers are running problem free, but won't launch
after Window-eyes crashes. Any suggestions on what I might try here?
Thanks in advance for your thoughts.
Larry
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.
__________ Information from ESET NOD32 Antivirus, version of virus
signature database 4057 (20090506) __________
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.
