I don't blame GW. If you read correctly, I stated I should have done a
custom install. Either way, this is a feature that would prevent people
crashing there system and so forth. Shouldn't take but, maybe 10 lines of
code.
I run 5 different screen readers.
It is either that feature, or you have it wear Window eyes don't load up
after it had detected a major error, until you resolved the issue. You take
your pick.
I am only suggesting something simple. I don't blame GW for causeing a
major crash issue. If you want to get into blame game, I blame JFW for
crashing one of my servers. Which was a Windows 2003 server. I lost over 2
Terabytes because of them. And it wasn't even a beta. I only use GW on my
server system now. I don't even allow anybody to install JFW products on
any of my servers. I have them blocked.
Matt.
-----Original Message-----
From: Stephen Clower [mailto:[EMAIL PROTECTED]
Sent: Friday, September 12, 2008 1:45 PM
To: gw-info-gwmicro.com
Subject: Re: WE 7 Beta 3 issues and priorities
I still don't see how it is GW Micro's responsibility to check for other
screen readers at startup. When installing any new piece of software,
you should read through what it will do, and how it will work. If you
know a quick install will enable Window-Eyes at startup, then either
tell Window-Eyes not to do that when it reboots, or disable the
automatic startup option of your current screen reader. Failing to read
instructions to save yourself one minute of time is frankly no excuse to
blame a company if something goes wrong due to your own oversight.
K. Matthew wrote:
One reason why I'm highly suggesting this, is the fact, I had this problem
happen to me, and I couldn't log into my computer. Well I called GW, and
see if they might have a way to by pass this problem, because when window
eyes load up and another screen reader at the same time when I logged in,
it
would crashed the whole computer. This was just after installing Window
eyes. Sure, I could have went and installed a custom install instead of
quick install and maybe be able to uncheck it from starting up
automatically. But, to call and get. You going to have to reinstall your
windows response, was not something I wanted to here.
It took me over 30 restarts to be quick enough and lucky enough to stop WE
from loading up and then be able to uninstall it. Needless to say, I
nearly
lost over 100 gigs of prodjects that I was currently working on.
And yes I know it was a beta, but, that don't mean to tell a customer oh
well you got to reinstall your windows. What if I installed it on my 3
Terabyte server? How you think I'm going to reinstall windows with that
much information on it? And this is not only happen with a Beta, it's
even
happen with 6.1 as well.
Matt.
-----Original Message-----
From: K. Matthew [mailto:[EMAIL PROTECTED]
Sent: Friday, September 12, 2008 1:23 PM
To: [email protected]
Subject: RE: WE 7 Beta 3 issues and priorities
True. Either way, having a check for screen reader before launching
shouldn't be too hard to have going. If a Low tech screen reader can do
it,
why not the higher end? I know it's different codeing, video driver and
all
that. But, to check something so simple as another screen reader product
running isn't that hard to implement. All they would have to do is a code
to check for a task running on the start up code, to see if said name of
screen reader is running.
I kno WE works with AI Square, they could exclude it from the list of
what
is running.
I'm just saying, something as simple as this could be put into the
program,
and it would help prevent one less issue with people crashing there system
on start up's or while running in windows and accidently start another
screen reader.
They could have it were it ask you to shut down any screen reader before
relaunching the program, or would you like to shut down window eyes to
allow
other screen reader control.
Matt
-----Original Message-----
From: Marvin Commerford [mailto:[EMAIL PROTECTED]
Sent: Friday, September 12, 2008 1:06 PM
To: K. Matthew
Subject: Re: WE 7 Beta 3 issues and priorities
Hi. Just because they do something in SA doesn't necessarily mean it
would
work well for all vendors. Let's say for example that they actually code
in
process names of other known screen readers. It work fine until another
product comes around. You may or may not remember the article that was on
their site a couple of years ago criticising the way FS and GW were going
about designing their products. Basically the article stated that newer
technology was being used in SA than in WE or JFW. Doug actually debunked
the article and it was quickly removed from their site. SA is what it is.
They do have some fine ideas but you have to sometimes look a bit deeper
into what's going on. There always will be programs that just won't work
with SA or NVDA and others like them because of their lack of video
intercept. SA makes portability important and that's neat. It is a give
and take though. I find that reading the items in My Computer with SA to
be
tiresome at best. Again, they have some fine ideas and it's excellent
that
they're out there doing what they do. But in the past they haven't been
above stretching the truth a bit.
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.
