BLIND-HAMS Archives

For blind ham radio operators

BLIND-HAMS@LISTSERV.ICORS.ORG

Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Steve Dresser <[log in to unmask]>
Reply To:
For blind ham radio operators <[log in to unmask]>
Date:
Tue, 31 Oct 2006 11:49:08 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (97 lines)
John,

I haven't seen the problems with Outlook Express, or Yahoo Messenger, 
but I don't use either of those programs.  I have seen the tab 
problems in I.E., and I suspect they happen because JAWS is having 
difficulty determining where it is on the screen, and so it loses 
focus.  This problem was reported to FS by a friend of mine back in 
July, and he never received any response from them.  Maybe we should 
all report our problems to FS and hope that they pay attention to 
numbers.  It's at least as useful as complaining to each other on this list.

Steve

On Tuesday 10/31/06 11:29 John Miller wrote:
>Well, my favorite problem is when ever I close outlook express, jaws 7.1
>goes bye bye, if I'm using a SAPI5 voice it doesn't do it but anything else
>I have does every time, I seem to have stability problems with IE, the tab
>button doesn't track with the arrow keys on web pates like it always has,
>using the tab key seems very sluggish too. It wasn't working in yahoo
>messenger hardly at all but I fixed that I think,  there was more but I
>don't remember it anymore. The outlook express issue was the biggest for me
>though, especially where a lot of people were having it before the July
>update and some still are. I can't have that, I exit out of outlook express
>when I leave the house but like to leave the computer on from when I wake up
>to when I go to bed if not round the clock some days.
>----- Original Message -----
>From: "Steve Dresser" <[log in to unmask]>
>To: <[log in to unmask]>
>Sent: Tuesday, October 31, 2006 11:04 AM
>Subject: Re: Off Topic - Jaws 7.1 Memory requirements
>
>
> > John,
> >
> > You may have already told us and I missed it, but what problems have
> > you run into with 7.1?  I know there are some, particularly with
> > Internet Explorer, and I'm sure there are some which I haven't
> > seen.  Lou makes a good point when he says none of the screen readers
> > are perfect, and you have to decide what you can or cannot live
> > with.  He's also right when he says that everyone configures Windows
> > to suit their own preferences, and that no two configurations are the
> > same.
> >
> > Steve
> >
> > On Monday 10/30/06 23:00 John Miller wrote:
> >>I've never had that problem with word XP, I just recently upgraded to
> >>2003,
> >>haven't seen it so far but I haven't used it all that much yet.
> >>----- Original Message -----
> >>From: "T Behler" <[log in to unmask]>
> >>To: <[log in to unmask]>
> >>Sent: Monday, October 30, 2006 10:41 PM
> >>Subject: Re: Off Topic - Jaws 7.1 Memory requirements
> >>
> >>
> >> >    Lou:
> >> >
> >> > Come to think of it, I have had the problem you mention here with Jaws
> >> > 7.0
> >> > when navigating  Word documents.
> >> >
> >> > I can't get it to happen consistently under a given set of conditions,
> >> > but
> >> > it does happen.
> >> >
> >> > Anyone come up with a cure for this?
> >> >
> >> > 73 from Tom Behler: KB8TYJ
> >> > .
> >> > ----- Original Message -----
> >> > From: "Louis Kim Kline" <[log in to unmask]>
> >> > To: <[log in to unmask]>
> >> > Sent: Monday, October 30, 2006 9:40 PM
> >> > Subject: Re: Off Topic - Jaws 7.1 Memory requirements
> >> >
> >> >
> >> >> Hi John.
> >> >>
> >> >> I ran into some problems on two machines where a user would be trying
> >> >> to
> >> >> edit a MS Word document and would be just arrowing around the document
> >> > when
> >> >> the cursor would abruptly move to the top of the document.  I was able
> >> >> to
> >> >> observe this repeatedly on the two machines in question, and they were
> >> > both
> >> >> running JAWS 7.0.  Upgrading the machines to JAWS 7.10 cured the
> >> >> problem
> >> > on
> >> >> both machines, and that is primarily what keeps me from being a big
> >> >> fan
> >> >> of
> >> > 7.0.
> >> >
> >

ATOM RSS1 RSS2