Hi Gw Micro Staff and Everyone,
I do agree with what David said here.
Mine also crashed this morning, also, on my desktop. My netbook isn't
even updating for some weird reason. Then, on my desktop, I got
confused with all these windows opened, and I couldn't remember which
scripts I had updated. Then, the last script, I attempted to update,
I can't remember which one it was, but it told me I was replacing it
with an older version, so I did not update that script.
It would be great, if Window-Eyes could say something like, "All
Scripts have been updated." I love the sound, it makes when there are
updates , but maybe it could still make that sweet sound, and then
automatically update the scripts, without having to go update each
one. This could be an option, in the Script Manager. Just a thought. <smile>
Thanks.
Pat Ferguson, always loving Window-Eyes
At 03:14 AM 5/7/2009, you wrote:
Just want to confirm, that I have had the same experience, several
times. I have a vague feeling, that it specially happens when
updates are available for the GW toolkit script; but then again,
that one is the one most frequently updated, ain't it?
There is one work around, which can be done in certain cases. That
is to unplug the internet cable of your computer, while re-booting.
Then, as soon as everything is up and running, including WE, plug in
the Internet cable again. After this, run the CTRL-WIN-I sequence,
and handle the updates 'manually'.
What I really would have loved to see, is a SILENT update function,
in WE. Even WHEN the script updating does function, with no loss and
breaks, I don't see why the user have first to accept the updating
of the script (which he has already done, by turning the automatic
update on, first hand), then see a long list of files the script
will install (which are installed from beforehand, since he is
already using the script), Then press install (useless, since he -
by turning on the automatic update - has already told the upcoming
updates to install), and - in many cases, i.e. with updates from GW
- ACCEPT the copyright screen (which also has been accepted through
all the prior updates, and even had to be accepted when the first
installation of the script was done). USELESS to go through all
these steps. Most other software would update more or less SILENTLY,
seamlessly, if ever giving info to the user, it would be a quick
message balloon, telling that the update has been done, and now is
ready. The only other compay, who sometimes have to go the LONG WAY
AROUND, when updating, is MicroSoft. And they only do it ONCE in a
while, not every single time.
GW staff, before considering WE7.1 on the market, why don't you hold
it a week or two longer, and then fix a script update function,
where things would work without all of this hazzle. If not, I agree
with the last user on this thread, simply turn off the automatic
update for all scripts. But then, why ever have such a feature, when
it only is to be left turned off?
First talikng of scripts: I wish the CD with WE, would ship with the
SCRIPT Installer script. That way, soon as the WE has installed, you
could simply press CTRL-WIN-I, and go through the list of availble
scripts. The way it is now, you first have to go to the Script
Central, to download it, and then install it manually, before you
can get the next scripts installed more smoothly. So, again GW
staff, could you have included this script on the installation cd?
----- Original Message ----- From: "Charles Adkins"
<[email protected]>
To: "GW Micro" <[email protected]>
Sent: Thursday, May 07, 2009 1:15 AM
Subject: Re: WE 7.01 crashing when script update Alert opens
I have had the same problem. For me since I have Windows sounds
killed, I go as far as the desktop I think, then script updates
begin and then the crash and I can do nothing. I have to re-boot,
and then try to stop the progress before the script updates load.
On this update today May 6, I can't tell you which update caused
the crash--we update I think--because when the update loaded speech
was killed, and when I stopped progress on next re-boot and did a
"control Windows I" approximately 5 updated scripts were ready for
my downloading.
When time permits, I'm thinking about turning off all automatic
updates until WE 7.1 if I can remember how to do that, no time now
though. This stuff always happens when I'm slammed with lots of
work, and by the time I have time I just keep putting off trying to
play Sherlock Holmes and fixing everything. If I just didn't have
to work every day!!!!!
SMILE
Chuck
----- 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.
--------------------------------------------------------------------------------
No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.5.325 / Virus Database: 270.12.21/2101 - Release Date:
05/06/09 17:58:00
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.
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.
