Re: Jaws and Different Screen Readers
- From: "Greg Epley" <gregepley@xxxxxxxxxx>
- To: <jfw@xxxxxxxxxxxxx>
- Date: Sat, 8 May 2004 12:46:12 -0500
Hi Steve,
That's very helpful info on interaction with 4.51. I never patched my 4.51
because when I first got 5.0 and had some problems with it, I was leery of
applying a patch to 4.51 that might require completely reinstalling 4.51. I
suppose it's possible that the patched 4.51 and I think the current
WindowEyes of 4.5 may work okay together. The only reason I asked also
about 4.51 is because I like having the fairly stable older version to fall
back on for now. I also have some pre 5.0 scripts I need to maintain and so
need the 4.51 for them.
-Greg
----- Original Message -----
From: "Steve" <k8sp@xxxxxxxxxxxxx>
To: <jfw@xxxxxxxxxxxxx>
Sent: Friday, May 07, 2004 3:14 PM
Subject: Jaws and Different Screen Readers
> Greg,
>
> This isn't current and F.S. denied that there was a problem. However,
when I
> attempted to run the dem of Win Eyes 4.21 which had DCM with JFW 4.51.119,
I
> got the silent treatment when on the log-on screen for Win XP.
>
> Here is a note I sent a year ago regarding this:
>
> Currently using JFW 4.51.119 NT, in a Windows XP Home Edition 2.6GHz with
512
> DDR memory.
>
> Recently, I downloaded a demo of GWMicro Window Eyes 4.21.1 which has the
> new video chaining technology. Although I did not have Window Eyes set to
> load on startup, I lost access to the log-on screen. JFW would only read
the
> user name, it would not read *** as the password is typed in, nor would it
> read the OK, Options or other buttons in the log-on screen. In addition,
the
> Windows Narrator would not read these items as it normally does.
>
> While I have resolved this problem by uninstalling Window Eyes, it appears
> these two apps are not working well together. I have heard from others
that
> if Win Eyes is installed first, they have not had this problem, but their
OS
> was Windows 2000. While the OS are similar in some respects, I don't know
if
> that is instructive in my case or not.
>
> Later, I decided to uninstall JFW. I then
> again installed Window Eyes, and set it to load before startup. By
itself, W
> E did speak the log-on info, and allowed me to access the desktop and
> associated apps.
>
> However, when I then re-installed JFW, I again had the same problem.
>
> This time, if I had Window Eyes come up on the log on screen, Window Eyes
> would read the password and the buttons such as ok, options etc. But,
once I
> entered my password and windows opened up, Window Eyes became silent. I
> could not re-load Window Eyes nor could I load Jaws or the Windows
Narrator.
>
> At this time, I'm not sure whether Window Eyes is actually at fault, or if
JFW
> is at fault. But, they definitely aren't candidates for marriage on my
> system at this time. That's too bad, as there are some interesting things
> which Window Eyes offers.
>
>
> Again, Greg, all that was a year ago with WE 4.21 and JFW 4.51.119.
Others
> have apparently not had the same problem.
>
> Steve Pollo
> Lansing, MI
>
>
>
> --
> To post a message to the list, send it to jfw@xxxxxxxxxxxxx
> To unsubscribe from this mailing list, send a message to
jfw-request@xxxxxxxxxxxxx with the word unsubscribe in the subject line.
> Archives located at: //www.freelists.org/archives/jfw
>
> If you have any concerns about the list, post received from the list, or
the way the list is being run, do not post them to the list. Rather contact
the list owner at jfw-admins@xxxxxxxxxxxxxx
>
--
To post a message to the list, send it to jfw@xxxxxxxxxxxxx
To unsubscribe from this mailing list, send a message to
jfw-request@xxxxxxxxxxxxx with the word unsubscribe in the subject line.
Archives located at: //www.freelists.org/archives/jfw
If you have any concerns about the list, post received from the list, or the
way the list is being run, do not post them to the list. Rather contact the
list owner at jfw-admins@xxxxxxxxxxxxxx
Other related posts:
