RE: JAWS problem on new HP laptop
- From: "Chip Orange" <Corange@xxxxxxxxxxxxxxx>
- To: <jfw@xxxxxxxxxxxxx>
- Date: Mon, 14 Mar 2005 17:28:44 -0500
Ok, your first and best resource is the system error log. Have a look
at it by going into control panel and choosing administrative tools. In
there, choose the event viewer (do this immediately after recovering
from one of your freezes). The event viewer gives you access to 3
different system logs, but the security one is never of any help. Check
the application and system logs for any entries (from the top downwards)
that say warning or error beside them. Go into that entry, find the
details edit box, and copy the info into an email to the list and/or FS.
Hopefully there will be something in there to look at other than
ordinary information entries.
Btw, why do you think the cause is jaws? There's probably a lot of
other software running on that pc, including some added by HP, and
perhaps anti-virus etc. added by you. Have you had a sighted person
work with it as much as you have, and had no errors when they weren't
using jaws? That would be about the only reason to really suspect jaws
as the cause.
Hth,
Chip
Chip Orange
Database Administrator
Florida Public Service Commission
Chip.Orange@xxxxxxxxxxxxxxx
(850) 413-6314
=20
> -----Original Message-----
> From: jfw-bounce@xxxxxxxxxxxxx=20
> [mailto:jfw-bounce@xxxxxxxxxxxxx] On Behalf Of Greg Epley
> Sent: Monday, March 14, 2005 2:42 PM
> To: jfw@xxxxxxxxxxxxx
> Subject: JAWS problem on new HP laptop
>=20
> Hello,
> Before I describe the problem I'm having with a new laptop=20
> system and JAWS, here is the currently working laptop system=20
> for your reference:
> JAWS 5.10.383
> Windows XP Home Edition, SP2
> Dell Inspiron 4000
> Intel Pentium III 900MHz
> 512Mb RAM
> ATI Rage Mobility M3
> ESS Maestro PCI Audio
>=20
> And here is the new laptop system that the problem is occuring on:
>=20
> JAWS 5.10.383
> Windows XP Home Edition, SP2
> HP Pavilion ZV5210US
> AMD Athlon(tm) 64 Processor 3000+
> 512Mb RAM
> NVIDIA GeForce4 440 Go 64M
> SoundMAX Digital Audio
>=20
> Again, the software above has all been running fine on the=20
> Dell mentioned above; I am also using the same speech synth=20
> on the HP as the Dell, but have tried using Elloquence and=20
> had the same problem.
>=20
> I thought perhaps someone here on the list might know of what=20
> is causing the conflict as the FS support database mentions=20
> no conflicts with the exact hardware components on the HP=20
> system, or that perhaps someone had this same system and=20
> could help me troubleshoot the issue.
>=20
> I haven't contacted FS yet about this problem because I have=20
> no control over who responds to the support request, and I=20
> need someone I can count on who can get to the crux of the=20
> problem and get it fixed rather than blindly grasping at=20
> straws, having no more idea than I do how to fix it. I don't=20
> need that; I can do plenty of that without anyone's help if I=20
> want. I want to see what sort of response I get from list=20
> members first and then proceed from there.
>=20
> The problem:
> I can be working along on the HP, when suddenly the whole=20
> system just seems to seize up. JAWS stops talking; my wife=20
> reports the mouse pointer still moves using a regular mouse=20
> or the touchpad, however, the mouse cannot be used to open=20
> the start menu or anything, and neither an external full size=20
> keyboard or the laptop keyboard will function. I therefore=20
> can't try to launch Microsoft Narrator to see if it will talk.
>=20
> The above "seize up" occurs at random times. I have kept=20
> records showing I ran these sessions:
> 1 hour 52 min.
> 49 min.
> 6 min.
> 10 min.
> 52 min.
> 25 min.=20
> 58 min.
> 1 hour 6 min.
>=20
> The last four usage sessions were run with the system being=20
> powered up from cold early in the morning and shut off around=20
> 6:30-7pm; so for the last two usage sessions for example, I=20
> ran 58 min. with no seize up, then the system just sat there=20
> until late afternoon/early evening, then I had a seize up=20
> after 1 hour 6 min.; all the other times listed, I turned the=20
> system on from cold and used it for the time listed before it=20
> seized up. =20
>=20
> I have checked the system several times and compared how hot=20
> it got compared to the Dell, and the HP system is running far=20
> cooler, even when comparing both laptops just sitting there=20
> doing nothing. So that and the random times listed would=20
> seem to indicate the problem isn't heat related.
>=20
> There is nothing in any kind of diagnostic I have run on the=20
> HP to indicate any kind of hardware failure or conflict of a=20
> hardware nature or a software driver.
>=20
> Personally I feel the problem is JAWS and not some flaw in=20
> the computer components. Perhaps it is the processor, but as=20
> Windows XP SP2 seems to have no issues otherwise, and the=20
> problem only occurs with JAWS usage, that would seem to=20
> indicate the issue is JAWS related. If it is the processor,=20
> FS had better get their act together and get this figured out=20
> and working, because anyone shopping for a system is going to=20
> start ending up with processors like this.
>=20
> Perhaps it is the SoundMax audio or the specific model NVIDIA=20
> video card. The video intercept installed fine and has=20
> reported no problems under any resolution or quality I've=20
> tried. The sound has performed fine running various=20
> applications other than the fact that I can't hear JAWS any=20
> longer once the system seizes up. Again, if the problem is=20
> due to one of these devices, FS had better get to fixing it=20
> as best they can; laptops aren't like desktops; you pretty=20
> much end up with integrated sound and video you have no choice over.
>=20
> I have an investment in the JAWS software of well over $1,000=20
> at this point, and while I understand FS can't test or force=20
> their software to work with everything, I likewise shouldn't=20
> be pinned down to only buying machines with certain=20
> processors or sound or video cards.
>=20
> The system is going nowhere. I am keeping the system, even=20
> if it takes FS several years to come up to the state of the=20
> art processor and other components in this HP laptop. =20
>=20
> I want to be very careful what I enable, disable, install or=20
> uninstall, lest I end up having to clean install a brand new=20
> laptop all because no one here on the list or at FS has any=20
> more idea than I do what is causing the problem and are just=20
> blindly grasping at straws to fix the problem. I don't need=20
> the latter; something is causing this problem and there is=20
> some way to fix it that doesn't require grasping at straws to fix.
>=20
> At this point I'd appreciate any constructive, positive=20
> feedback I can get on this seizing problem, as I'd like to=20
> begin getting full use out of my brand new laptop. No one is=20
> going to change my opinion of FS products so let's just stick=20
> to the problem at hand and leave it at that.
>=20
> Oh BTW I should add that I checked the BIOS settings and=20
> there does not appear to be anything in there that would seem=20
> to be something I could disable or change that could solve=20
> the problem. =20
>=20
> The problem also does not appear to occur while using any=20
> particular application (such as IE, Outlook Express, etc.). =20
> I do not own any competing screedn reading product, and as=20
> the trial times for Dolphin's HAL and G.W. Micro's WindowEyes=20
> are only 30 minutes long, it would take me quite a long time=20
> running 30 min. sessions to try to stumble across one of the=20
> seizes that might occur within that short time frame. =20
> Besides which, one of the things FS did a really good job on=20
> was the keyboard layout for JAWS vs. the competitors=20
> products. I think this is just a matter of isolating what is=20
> causing the problem, and perhaps FS fixing some flaw in their=20
> product that doesn't like the processor, sound card or video=20
> card on this HP laptop. =20
>=20
> The problem also doesn't appear to occur in a reproducable=20
> manner; i.e., I've had it seize up when I was really typing=20
> fast, but also when I wasn't - perhaps when I was just=20
> hitting one key after several seconds. There is just no=20
> pattern to it; it is like playing Russian roulette with my=20
> work - do something and save, do something and save, do=20
> something and BOOM - seize up without any warning.
>=20
> I haven't received my JAWS 6 shipment yet, so have no idea if=20
> JAWS 6 would resolve the problem.
>=20
> Again, please offer any constructive, positive feedback if=20
> you think you have any ideas as to what might be causing the=20
> problem. I have client work I am trying to complete so=20
> please bear with me if I don't respond back quickly; I will=20
> try suggestions as soon as I can and get back to any of you=20
> as soon as possible.
> -Greg
>=20
> --
> To post a message to the list, send it to jfw@xxxxxxxxxxxxx=20
> To unsubscribe from this mailing list, send a message to=20
> jfw-request@xxxxxxxxxxxxx with the word unsubscribe in the=20
> subject line.
> Archives located at: //www.freelists.org/archives/jfw
>=20
> If you have any concerns about the list, post received from=20
> the list, or the way the list is being run, do not post them=20
> to the list. Rather contact the list owner at=20
> jfw-admins@xxxxxxxxxxxxxx
>=20
--
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:
