Hi Aaron,

I think you may have taken my comment out of context. Clearly, over the
years I have taken on advice provided by GW Micro staff to assist in
diagnosing faults, including switching off scripts.

In your note you had the following:
<<<<<
* Make sure all Microsoft updates have been installed
* Make sure all running software is at the latest version
* Turn off scripting
* Try switching synthesizers
* Disable Braille (if it's enabled)
* Go through MSCONFIG, and disable every application from starting
automatically, even Window-Eyes
* Ensure that you have the appropriate amount of disk space for virtual
memory
* Try defragging your drives
* Unplug any unused USB peripherals
>>>>>

All of these steps are valid of course.
However, in a corporate environment it is not always possible to comply
with the first 2 steps as there are, in some cases, corporate rules
against it. For example, in the office I cannot upgrade from IE6. I am
therefore living with issues with IE in my environment with automatic
browse mode not working even though I have taken all of the steps
advised by GW at the time they occurred. . This has persisted over
several releases of WE.
When I don't get a WE lock-up for several days, but then get 3 in a row,
and then none again for several days the constraints of not using
Braille and having to start up every app I have stopped in MS config do
not give a good "cost benefit" case for doing them as opposed to
correcting the issue when it occurs.


On my home PC where I am running Windows 7 32-bit I have reported a
number of issues to this list. I cannot recall any feedback from GW on
the ability you have to replicate them or on the potential of them being
corrected.

I don't think I am alone in this.
A note of status of these issues would not go amiss.

Well, that being said, I am still a Window-Eyes advocate and intend to
continue as such.
  

Regards, John. 
 
John Farley 
***********************************************************************


SAIC Limited is a private limited company registered in England and Wales. 
Registered number 1396396. Registered office at Hemel One, Boundary Way, Hemel 
Hempstead, Hertfordshire, HP2 7YU. This email is subject to the following 
conditions http://www.saic.com/europe/emaildisclaimer.html
 -----Original Message-----

From: Aaron Smith [mailto:[email protected]] 
Sent: 10 December 2009 15:19
To: Farley, John [OS-IE]
Cc: [email protected]
Subject: Re: FW: window-eyes 7.11

On 12/10/2009 9:52 AM, Farley, John [OS-IE] wrote:
> It is not possible to work with the limits imposed that Aaron's note
suggest.
>    

Choosing not to try any of what I suggested means definitely not having 
the problem resolved. What's worse: running with scripts disabled for a 
day or two, or dealing with lockups for months and months?

If you write us with concerns about a problem, but then ignore the 
suggestions we offer, how are we ever going to get the problem resolved?

Aaron

-- 
To insure that you receive proper support, please include all past
correspondence (where applicable), and any relevant information
pertinent to your situation when submitting a problem report to the GW
Micro Technical Support Team.

Aaron Smith
GW Micro
Phone: 260/489-3671
Fax: 260/489-2608
WWW: http://www.gwmicro.com
FTP: ftp://ftp.gwmicro.com
Technical Support&  Web Development

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