Cliff, and others who might be following Cliff's method. I am sorry
to say that it has nothing to do with outlook 2007 as I do not have it
installed on here and get the error I have described. So hopefully that
saves you a headache or 12. I wonder what the root cause of this is? To
the person who mentioned audio drivers being held up, forgive me I've
forgotten who that was specifically, you are correct in that I have to
shut down the computer with the power button to get any speech back. God
help me if I'm writing a document and we freezes.
Dave c. bahr
On 12/10/2011 6:07 AM, Cliff Fry wrote:
Hi Dave,
I have had this on a random basis as well. It seems to happen in
conjunction with Outlook 2007. I think it has something to do with
the new UI interface. When this happens, there seems to be some kind
of line across the bottom of the screen. At least that is what my
wife says. I have not reported it because I don't know how to explain it.
What I have done to fix it is to delete the Outlook folder which is
under user\cliff fry\appdata\roaming\microsoft. Then when I restart
Outlook I must change it so it does not get new messages. I usually
go in to computer, select my local drive C, and run disk cleanup
getting rid of the unnecessary files. Then I re-boot the computer.
The line goes away from the bottom of the screen and all works again.
I don't know if I need to do all of that but it works.
Cliff
*From:*Dave Bahr [mailto:[email protected]]
*Sent:* Saturday, December 10, 2011 12:21 AM
*To:* gw-info
*Subject:* Re: we is not exiting fully
Hmm, that was weird, I don't recall sending that message. Well,
consider this take 2 of the pervious message which ended rather abruptly.
Occasionally, when I exit window-eyes either by closing the window
itself of the control pannel or using the quickquit.vbs script,
window-eyes will say that it's already running if I try to relaunch
it. I have tried a manual start of the gwtoolkit, and the
homersharedobject aps and then combinations of the relaunch we and
quickquit aps. Well, it's like when you take your car to the mechanic
and whatever was wrong in the garage is perfectly fine in the shop; we
worked flawlessly through all tests. But wait! don't close the message
just yet! thanks. Is anyone else seeing the same issue? When it
happens, I have to use the kill wineyes script and then launch we
again, which necessitates a relaunch of we so that items in list and
tree views can read properly, and then the cycle perpetuates. I always
ask this but, am I explaining this properly? Help? Please?
Dave c. bahr
On 12/9/2011 10:08 PM, Dave Bahr wrote:
> Hi gang,
>
> This is a problem I've been having for a bit now, since 7.5.0
I
> think. When I close window-eyes via the control insert
>
> --
>
>
> Dave c. bahr
>
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.
