Re: Closing thread unresolved: JAWS problem on new HP laptop
- From: "Greg Epley" <gregepley@xxxxxxxxxx>
- To: <jfw@xxxxxxxxxxxxx>
- Date: Thu, 17 Mar 2005 09:24:02 -0600
Chip (and all),
Here is the info from the event log. I didn't pass it along before because
it was sitting in a text file on the HP and at the time I'd had enough of
the HP so didn't really feel like booting it up to get the file. Also, I
should mention that I did look back through the event logs and don't see any
error or warning around the time of the other crashes, so understand what
you are seeing in this error was not logged before after the other crashes.
Here is the info:
Event Type: Error
Event Source: DCOM
Event Category: None
Event ID: 10010
Date: 3/16/2005
Time: 4:07:28 PM
User: GREG64N\Greg Epley
Computer: GREG64N
Description:
The server {F3A614DC-ABE0-11D2-A441-00C04F795683} did not register with DCOM
within the required timeout.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Chip, there is a reason as to why I haven't returned the HP for diagnostics,
but I prefer not getting into that. It is not that the system is stolen or
anything like that, but I do want to leave any returning of the system to HP
as a very last resort.
I doubt running the demo of WindowEyes in small, 30 minute increments would
tell me anything useful. After these recent changes I made, the system
showed no signs of instability for longer than it ever has, and yet late
yesterday afternoon it just suddenly seized up with no warning, and I wasn't
even typing fast or anything at the time - it just seized up and that was
that.
Read on to the other thread response for more.
-Greg
----- Original Message -----
From: "Chip Orange" <Corange@xxxxxxxxxxxxxxx>
To: <jfw@xxxxxxxxxxxxx>
Sent: Thursday, March 17, 2005 8:05 AM
Subject: RE: Closing thread unresolved: JAWS problem on new HP laptop
> Greg,
>
> I'm sorry to hear you've hit the wall on this. I do think however
> you've written off an HP hardware problem too soon, without any real
> argument as to why it could not be a faulty HD say, or something like
> that.
>
> Btw, we could use more info on the DCOM event you mentioned. Press
> enter to go into it, tab to the edit box with the details, press
> control-a and control-c to copy the details, and then paste them to the
> list.
>
> I would try returning it to HP for their evaluation, or, if this is what
> it takes to convince you, try the demo of window eyes for a while as
> your screen reader.
>
> 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: Wednesday, March 16, 2005 10:37 PM
>> To: jfw@xxxxxxxxxxxxx
>> Subject: Closing thread unresolved: JAWS problem on new HP laptop
>>=20
>> Hi,
>> I agree with you on the software conflicts, but the reason I=20
>> uninstalled all these was mainly to level the playing field=20
>> between my Dell and the HP.=20
>> It's mighty hard to troubleshoot something that's not working=20
>> when you have all manner of obvious software differences=20
>> between a working and non-working system.
>>=20
>> To update all who are following this thread, assuming anyone=20
>> is any more: I finally had another seize up a bit after 4pm=20
>> this afternoon; this after using the system as consistently=20
>> as one could trying to do practical, real-world work. The=20
>> plus side is that it did take longer for the seize up to=20
>> occur, but I can't get work done wondering when my Russian=20
>> Roulette HP computer is going to blow its head off.
>>=20
>> I let the system sit a good 15 minutes and it never=20
>> recovered. The touchpad did seem to work some, but the=20
>> system was definitely acting extremely sluggish. The=20
>> keyboard on the laptop also seemed somewhat functional,=20
>> though again very sluggish. I still was never able to=20
>> successfully launch Microsoft Narrator, so have no input on=20
>> whether that would work or not. As a result of the=20
>> instability, I also had to force power down the system yet=20
>> again, which could be affecting the event log information -=20
>> but I have no choice there, as I can't get any sort of=20
>> control to do a controlled shutdown.
>>=20
>> I checked the event logs, as was recommended by several, and=20
>> found only 1 entry in the Application log. It was DCOM,=20
>> event ID 10010, and was time and date stamped at the=20
>> approximate time the system froze.
>>=20
>> I'm still waiting for FS to ship my JAWS 6.0. I have tried=20
>> to contact them twice by email about it but no one has=20
>> responded to me as yet. Typical.=20
>> Any wonder why I have so much love for FS when I get treated=20
>> this way as a customer? Downloading JAWS 6 to see if it=20
>> fixes the problem isn't a resolution at this point. I notice=20
>> another lister has said FS told them the drivers in JAWS 6=20
>> would even help 4.5 run better. I don't know, I just think=20
>> this is a lousy way to treat customers with a product that I=20
>> have an over $1,000 investment in. I'm in so deep with FS=20
>> right now that I have no choice but to stay with it, though=20
>> how much longer I'll remain a customer is debatable.
>>=20
>> This HP is a state of the art machine. It does not have=20
>> crappy components on it. Any person going out to buy a=20
>> laptop any time in the near future had better heed warning=20
>> and first run every component of the machine by FS first to=20
>> make sure everything is "compatible" with JAWS. Apparently=20
>> that is the only way to even come close to a pleasant experience.
>>=20
>> I certainly haven't had one. I stand by my original thinking=20
>> that the crux of the problem here is JAWS. The HP laptop may=20
>> have to sit in my closet for several months, waiting for JAWS=20
>> to reach a stable point to work on it.=20
>> Meanwhile I will continue to peck away at this or that on it=20
>> and perhaps eventually get it working in a stable fashion. =20
>> My Dell is going on five years old and I have been looking=20
>> forward to this much better HP for some time. It is=20
>> frustrating to the extreme to not have any "bread crumbs" to=20
>> follow to fix this weird freezing problem, and everyone seems=20
>> as clueless as to what's causing it as I am.
>>=20
>> I will be leaving the list again soon, and wish you all the=20
>> best with your JAWS products. I still think it's the best=20
>> screen reader from a usage perspective; I just think JAWS=20
>> needs a lot of work done on it besides adding a bunch of new=20
>> features that just add to existing bugs. You may not agree=20
>> with my opinion of the matter, and you are welcome to yours,=20
>> but please respect mine and don't blast me for feeling the=20
>> way I do right now. I'm accustomed to being able to fix=20
>> problems like this one, but it's next to impossible to do=20
>> when I'm battling an unknown problem that seems to have no=20
>> solution other than grasping at straws.
>> -Greg
>>=20
>> ----- Original Message -----
>> From: "Pranav Lal" <pranav.lal@xxxxxxxxxxxxxxxxx>
>> To: <jfw@xxxxxxxxxxxxx>
>> Sent: Wednesday, March 16, 2005 6:48 PM
>> Subject: Re: Update: JAWS problem on new HP laptop
>>=20
>>=20
>> > Hi Greg,
>> >
>> > <snip J2RE
>> > PL] I doubt it. This is the java virtual machine and has no=20
>> connection=20
>> > with
>> > jaws. For that matter none of the softwarethe that you have=20
>> uninstalled=20
>> > has
>> > any connection with jaws. even QuickTime should not=20
>> interfere in this
>> > manner unless you are using it to play QuickTime movies.
>> >
>> >
>> > Pranav
>> > Pranav
>> >=20
>> --------------------------------------------------------------
>> --------------------------------------------------------------
>> -----------
>> > Pranav
>> >
>> > --
>> > To post a message to the list, send it to jfw@xxxxxxxxxxxxx
>> > 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
>> >
>> > If you have any concerns about the list, post received from=20
>> the list, or=20
>> > the way the list is being run, do not post them to the list. Rather=20
>> > contact the list owner at jfw-admins@xxxxxxxxxxxxxx
>> >=20
>>=20
>>=20
>>=20
>> --
>> To post a message to the list, send it to jfw@xxxxxxxxxxxxx
>> 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
>>=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
>
--
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:
