RE: Overheating
- From: Ken Gould <gould100@xxxxxxx>
- To: jfw@xxxxxxxxxxxxx
- Date: Sun, 18 Jan 2004 12:55:37 -0500
Peter and All -
Let me be quite clear about this. While there are obviously many things,
such as poor ventilation, which can cause overheating, there is absolutely,
positively no doubt from the test I have done that JAWS 5 can cause sudden
temperature spikes in some computers. JAWS 4 does not have this problem,
but it is my recollection that 4.51 can also exhibit this problem. But I
don't remember that for sure. Please understand that this affects a
relatively small number of computers, so most people will never experience
it. We don't know what causes it to happen on certain computers, but it
can occur in Windows 98SE Windows Millenium, Windows 2000, and Windows
XP. Various people with whom I have been in communication have experienced
this problem in all of these operating systems. I no of one person for
whom this problem is so severe that it will shut down her computer after
about 15 or 20 minutes of using JAWS 5. On my own computer, the problem
can occur shortly after booting, or I can sometimes run JAWS for many hours
without experiencing it. When it does happen, I will get a sudden
temperature spike of about 20 degrees Celsius, and the side of my computer
actually gets hot to the touch. (I monitor the temperature of my CPU and
Asus mother board with a utility that comes with all Asus boards.) I'm not
going to go into detail here about all of the experiments I performed to
prove this satisfactorily to myself. I don't care if Freedom Scientific's
tech support people don't know about this problem. Others at FS certainly
do know about it. They just haven't been able to fix it yet. When it
occurs on my machine, the temperature will elevate by the 20 degrees
Celsius I mentioned, and it will stay up there permanently until and unless
I unload JAWS or reboot. Then the temperature returns to normal. Now I'm
not saying that JAWS has to be the only possible cause for the problems on
your machine, but if it is, then there's nothing you can do at this time
except to unload and reload JAWS. If that temporarily stops the problem
for you, then it's JAWS which is doing it. If unloading and reloading JAWS
makes no difference, then your problem resides elsewhere. But if your
sighted associate never experiences the problem without JAWS, then it's a
pretty good bet that JAWS is the culprit.
There's really nothing else to say on this matter. If some people don't
believe that JAWS can do this, then so be it. The problem never happened
with JAWS 4.02, it never happens when JAWS isn't running, and, when it does
happen, nothing will drop the temperature back to normal except unloading
JAWS. I mean absolutely nothing. Not stopping all background tasks, not
unloading all running programs, not stopping my virus checker,
nothing. JAWS is the source of the problem on my machine, and that's all
there is to it.
Best regards,
Ken
E-mail address: gould100@xxxxxxx
Please visit my store's home page at http://www.audionexus.com
--
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.
Other related posts:
