I had an issue like that. I was writing a message in OE using beta1, when
the keyboard stopped working. I had to log into my laptop remotely, kill
window eyes, log out, restart window eyes, to get it working again. Mind
you, this laptop has been running almost 10 weeks, so that might have
something to do with it.
Other than that, I have had 0 problems with beta1 . Nothing. I use old style
eloquence though.
----- Original Message -----
From: "James Aldrich" <[EMAIL PROTECTED]>
To: "Window-Eyes discussion list" <[email protected]>
Sent: Saturday, September 20, 2008 11:22 PM
Subject: I thought I had it made!
Hello everyone!
The subject says it all! I thought I had it made! I'm using Windows XP
home with SP3 on a laptop. I received my 7.0 disk here in Montana today
so
they got many of the disks out already I would say! Great work!
I have always felt the regular version works better than a beta! The 7.0
version is quite snappy! The new elloquence seems to work well for the
most
part!
Now to the heart of things! I'm still losing speech! I have only checked
this with the new eloquence. I'm usually reading Email in Outlook
Express.
I finish reading a particular message. I press escape to get back into
the
message list. The speech is gone! I must reboot the computer to bring
back
window eyes. I usually bring up System Access to simply finish my mail.
I
rarely lose speech with it. When I shut down System Access, it is shut
down! I can bring it back as quickly when typing its hot key! I bring up
both speech programs manually. I did once when I selected the old
eloquence
speech in System Access. I was reading mail in Outlook Express then too.
I
never have lost speech with System Access when using Dectalk. I'll need
to
check out Dectalk in Window Eyes. I also have gone into messages and they
weren't reading automatically. I turned off browse mode, went back into
message list, found the message which didn't read automatically and
clicked
on it again. This time it read.
I downloaded the Kill Wineyes and quick quit Window Eyes scripts. I liked
how quick quit worked for the most part. If I should lose speech as I did
a
bit ago, I still have to reboot. Quick Quit didn't stop the entire
program.
If it could do so, all one would need to do is type in the windoweyes hot
key and the program would be going again. This isn't the case now! I
wish
Quick Quit or kill Wineyes would bring down the whole program so a person
would need only type the hot key and it would be as good as new once again
when brought up with the hot key to load Window Eyes.
When I was using beta three, I unloaded the auto complete script. This
took
care of the loss of speech for me where it wouldn't be happening as often.
I made certain braille was off. I'll do so now with 7.0 upgrade to see if
I
get the same results. . I'll report back.
Jim
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.
