Re: loosing speech
- From: "david poehlman" <david.poehlman@xxxxxxxxxxxxxxxxxxxxxxxx>
- To: <jfw@xxxxxxxxxxxxx>
- Date: Mon, 3 Jan 2005 16:09:10 -0500
Yes, i/o is usually the culpret. If you load huge messages or pages or
pages with lots of activity, this can cause jaws to seemingly go silent. If
you wait long enough in most cases, it comes back on its own. In situations
where jaws runs out of memory, it will also stop because th ememory has been
stuffed with activex controlls and the like. Take it out and clean it. In
other words, either restart the computer or restart jaws or empty the
browser cache etc. These issues have been with computer users since time
immorial and no matter how much power you have or how much hd you have or
ram, someone can foil your pc.
Johnnie Apple Seed
----- Original Message -----
From: "john r. vaughn" <jrvaughn44@xxxxxxxxxxx>
To: <jfw@xxxxxxxxxxxxx>
Sent: Monday, January 03, 2005 3:55 PM
Subject: Re: loosing speech
quite clearly, the shear size of this message along with some other problems
that someone sited might see in the message at least lets us know why Jaws
went silent in our trying to open the message.
Many times when a web site is down loading Jaws will not speak until the
page is loaded. So I suppose that is normal for jaws to stop speaking when
the computer is doing other processing and we have to live with that.
But maybe some of our more technically oriented list members can help us out
and better explain what we experienced.
John
----- Original Message -----
From: <ptusing@xxxxxxxxxxxxx>
To: <jfw@xxxxxxxxxxxxx>
Sent: Monday, January 03, 2005 3:44 PM
Subject: Re: loosing speech
> Hi,
> How would we test this as the JAWS going silent has happened before but
> not
> often.
> ----- Original Message -----
> From: "john r vaughn" <jrvaughn44@xxxxxxxxxxx>
> To: <jfw@xxxxxxxxxxxxx>
> Sent: Monday, January 03, 2005 3:25 PM
> Subject: loosing speech
>
>
>> list, the message I just sent containing the message from chip orange
>> probably locked up yur computers like it did mine.
>> In looking at chips message, it was almost 1 gig in size as it contained
>> messages fowarded along with a copy of a list digest.
>> so our problem was not jaws, just the computer and outlook downloading a
>> large message.
>> John in sunny florida
>>
>>
>> --
>> 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
--
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:
