Sorry for the heading, but it is quite describing for my last half-hour
experience. The screen reader really is far to unstabil lately. For
several days, it crashes when I try to run certain apps, like the
Polyglot. It gives me errors randomly in GWToolket and HomerShared. OK,
I have checked for updates to all my apps, re-downloaded and installed
the two above mentioned apps, but still the screen reader decides to
hang every now and then. More like ten times a day.
This afternoon it reaches its climax. I experienced another unstability
and decided to close down WE, before it would crash on me. Better to do
things controlled, I figured. Yes, it closed down and the closing jingle
played. I gave it something like ten seconds, which used to be enough
for my closing things down in the past.
After the ten second wait, I pressed the hotkey to reload Window-Eyes.
And received an error about it not being able to hook with Explorer,
blah-blah-blah. And, of course, the screen reader hung here, so how
would I know, if not it was thanks to NVDA.
Pressing OK on the error (nope, I did not find it OK but there was no
other button to press) :) I finally got the screen reader up running. I
figured that since the error had shown up at the startup, I would try
another controlled close-down reload procedure. So again, closed it down
and everything seemed fine. Then after a few seconds, pressed the hotkey
to reload.
Again, had I not have NVDA installed, I would have been lost. Because
all I got now, was the error telling that WE is already running. Silly,
foolish and blurby stuff. It had just jingled to me, that it was
closing, and after the last few seconds waiting, it should by all means
be closed down and unloaded - at least had it worked properly like any
profesional software. Never seen such behavior from other software. Does
it claim to be unloaded, how come it now tells me it is already running?
NVDA helped me in the TaskManager, and here all I could find running
from GW was the Wilie or whatever it is called. Both the 32 and 64bit
version was running, since this is a 64bit machine and OS. I tried to
kill those two processes, and it showed up to be gone in the TaskManager.
Now, back to the reloading of the screen reader. Hit the hotkey, and
what do I get? You all may think I am funny, or at least the screen
reader thinks it is playing time, telling the bad jokes of its own
choice. I got the following error message, and not until I hit the OK
button the screen reader would load. Now I don't want to spend more time
in fooling around unless I have to face another craziness from this
"rock solid" screen reader. Sorry, b ut this is simply not acceptable. I
am on Win7 Pro, an OS that has been around for more than a handful
years. Things like this should be sorted out by now. Don't tell me the
next version may happen to solve things. I have heard that pop-song
before. It does not help me to know things may eventually get fixed next
year or decade. I need perform my computing now.
I have run a full scan with MS Essentials, MalwareBtes and CCleaner.
None of it has proven helpful in solving things Any more things to try?
Am I really the only one facing this kind of time-wasting silliness?
Really don't believe so, due to the feedback seen lately on the list.
GW, please, have a fix out that door, and get back on the rock.
Here is the error message I get at startup. Sometimes it complains about
Explorer, sometimes about Notepad, sometimes about who knows what, and
once in a while you won''t believe it but it may happen to start with no
complains (congratulations). :)
---------------------------
Window-Eyes Error
---------------------------
Unable to set hook in process notepad DrawFocusRect at address 76beef20
Bytes: e9 13 11 fd ff 8b 05 4d 33 07
---------------------------
OK
---------------------------
--
David
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.
GW-Info messages are archived at http://www.gwmicro.com/gwinfo. You can manage
your list subscription at http://www.gwmicro.com/listserv.
