RE: Closing thread unresolved: JAWS problem on new HP laptop
- From: "Chip Orange" <Corange@xxxxxxxxxxxxxxx>
- To: <jfw@xxxxxxxxxxxxx>
- Date: Thu, 17 Mar 2005 12:24:27 -0500
Yes; if it's the driver malfunctioning, and not just an unresponsive
network, I think it could end up permanently "locked up" until you
reboot.
As an experiment, I'd try a wired connection into the router for a while
to see if the hangs stop; if that's just not physically possible, I'd
try running the wifi without encryption (like wpa in particular) as I
see reports from time to time that it causes hangs (check out the news
group alt.internet.wireless). WEP is supposed to be more stable, but
less secure. I've seen some folks complain that if their WIFI 11G card
loses signal altogether, that it does indeed hang the laptop while
trying to re-acquire; if it never can, then the laptop stays hung,
that's why I think a wired link would be a good experiment.
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: Thursday, March 17, 2005 11:25 AM
> To: jfw@xxxxxxxxxxxxx
> Subject: Re: Closing thread unresolved: JAWS problem on new HP laptop
>=20
> Chip,
> Can the hanging last for over 10-15 minutes? I've never had=20
> that kind of hanging so don't know what to expect in how long=20
> to wait to see.
>=20
> This HP laptop has both a mini PCI G wireless and a 10/100=20
> Ethernet on it.=20
> The 10/100 Ethernet is disabled, but it's drivers are up to=20
> date as best I can determine according to what Microsoft or=20
> HP has. The G wireless is also similarly up to date, and is=20
> what is in use for network/internet. I've never had any=20
> wireless hang problems and I've used a wide variety of=20
> wireless products from no particular vendor.
>=20
> I don't use any software firewall; I have a Linksys WRT54G=20
> that is up to date on its firmware and have had no problems=20
> with it up to this point. Not saying there isn't something=20
> weird going on now with this updated HP system on the=20
> network, and very likely I am encountering something strange=20
> here now because I am somewhat out of date on the latest,=20
> greatest hardware. Most likely I am going to be scratching=20
> my head over this one for some time to come; it appears it is=20
> going to take dumb luck to get it solved.
> -Greg
>=20
> ----- Original Message -----
> From: "Chip Orange" <Corange@xxxxxxxxxxxxxxx>
> To: <jfw@xxxxxxxxxxxxx>
> Sent: Thursday, March 17, 2005 10:13 AM
> Subject: RE: Closing thread unresolved: JAWS problem on new HP laptop
>=20
>=20
> > Ok, it sounds like a network communications problem. Perhaps your
> > ethernet card or wifi adapter is hanging, or, if you have a software
> > firewall, perhaps it's blocking all (or some critical) traffic. The
> > network card with its driver has such a high system=20
> priority, that if
> > it's in the middle of attempting something critical, and=20
> things fail, it
> > can make it seem like your system has "locked-up".
> >
> > If you have a software firewall that you can temporarily=20
> disable, that
> > would be my next suggested experiment.
> >
> > Hth,
> >
> > Chip
> >
> >
> >
> > Chip Orange
> > Database Administrator
> > Florida Public Service Commission
> >
> > Chip.Orange@xxxxxxxxxxxxxxx
> > (850) 413-6314
> >
> > =3D20
> >
> >> -----Original Message-----
> >> From: jfw-bounce@xxxxxxxxxxxxx=3D20
> >> [mailto:jfw-bounce@xxxxxxxxxxxxx] On Behalf Of Greg Epley
> >> Sent: Thursday, March 17, 2005 10:38 AM
> >> To: jfw@xxxxxxxxxxxxx
> >> Subject: Re: Closing thread unresolved: JAWS problem on=20
> new HP laptop
> >>=3D20
> >> Nope, haven't touched anything like that.
> >> -Greg
> >>=3D20
> >> ----- Original Message -----
> >> From: "Chip Orange" <Corange@xxxxxxxxxxxxxxx>
> >> To: <jfw@xxxxxxxxxxxxx>
> >> Sent: Thursday, March 17, 2005 9:30 AM
> >> Subject: RE: Closing thread unresolved: JAWS problem on=20
> new HP laptop
> >>=3D20
> >>=3D20
> >> > Greg,
> >> >
> >> > This looks like you may have disabled the DCOM service, or=3D20
> >> some service
> >> > that it depends on, on this hp, or some other computer on=3D20
> >> your network;
> >> > is that possible? (are you the kind that's in to disabling=3D20
> >> xp services
> >> > to try and get just a little more performance out of the system)?
> >> >
> >> > Chip
> >> >
> >> >
> >> >
> >> > Chip Orange
> >> > Database Administrator
> >> > Florida Public Service Commission
> >> >
> >> > Chip.Orange@xxxxxxxxxxxxxxx
> >> > (850) 413-6314
> >> >
> >> > =3D3D20
> >> >
> >> >> -----Original Message-----
> >> >> From: jfw-bounce@xxxxxxxxxxxxx=3D3D20
> >> >> [mailto:jfw-bounce@xxxxxxxxxxxxx] On Behalf Of Greg Epley
> >> >> Sent: Thursday, March 17, 2005 10:24 AM
> >> >> To: jfw@xxxxxxxxxxxxx
> >> >> Subject: Re: Closing thread unresolved: JAWS problem on=3D20
> >> new HP laptop
> >> >>=3D3D20
> >> >> Chip (and all),
> >> >> Here is the info from the event log. I didn't pass it=20
> along=3D3D20
> >> >> before because it was sitting in a text file on the HP=20
> and at=3D3D20
> >> >> the time I'd had enough of the HP so didn't really feel=20
> like=3D3D20
> >> >> booting it up to get the file. Also, I should mention=20
> that I=3D3D20
> >> >> did look back through the event logs and don't see any=20
> error=3D3D20
> >> >> or warning around the time of the other crashes, so=3D3D20
> >> >> understand what you are seeing in this error was not =
logged=3D3D20
> >> >> before after the other crashes.=3D3D20
> >> >> Here is the info:
> >> >>=3D3D20
> >> >> 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=3D3D20
> >> >> register with DCOM within the required timeout.
> >> >>=3D3D20
> >> >> For more information, see Help and Support Center at=3D3D20
> >> >> http://go.microsoft.com/fwlink/events.asp.
> >> >>=3D3D20
> >> >> Chip, there is a reason as to why I haven't returned the =
HP=3D3D20
> >> >> for diagnostics, but I prefer not getting into that. It =
is=3D3D20
> >> >> not that the system is stolen or anything like that,=20
> but I do=3D3D20
> >> >> want to leave any returning of the system to HP as a very=3D20
> >> last resort.
> >> >>=3D3D20
> >> >> I doubt running the demo of WindowEyes in small, 30 =
minute=3D3D20
> >> >> increments would tell me anything useful. After these=20
> recent=3D3D20
> >> >> changes I made, the system showed no signs of=20
> instability for=3D3D20
> >> >> longer than it ever has, and yet late yesterday=20
> afternoon it=3D3D20
> >> >> just suddenly seized up with no warning, and I wasn't =
even=3D3D20
> >> >> typing fast or anything at the time - it just seized up =
and=3D3D20
> >> >> that was that.
> >> >>=3D3D20
> >> >> Read on to the other thread response for more.
> >> >> -Greg
> >> >>=3D3D20
> >> >> ----- 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=3D20
> >> new HP laptop
> >> >>=3D3D20
> >> >>=3D3D20
> >> >> > Greg,
> >> >> >
> >> >> > I'm sorry to hear you've hit the wall on this. I do=3D20
> >> think however
> >> >> > you've written off an HP hardware problem too soon,=3D20
> >> without any real
> >> >> > argument as to why it could not be a faulty HD say, or=3D3D20
> >> >> something like
> >> >> > that.
> >> >> >
> >> >> > Btw, we could use more info on the DCOM event you=3D20
> >> mentioned. Press
> >> >> > enter to go into it, tab to the edit box with the=20
> details, press
> >> >> > control-a and control-c to copy the details, and then=20
> paste=3D3D20
> >> >> them to the
> >> >> > list.
> >> >> >
> >> >> > I would try returning it to HP for their evaluation,=20
> or, if=3D3D20
> >> >> this is what
> >> >> > it takes to convince you, try the demo of window eyes=3D20
> >> for a while as
> >> >> > your screen reader.
> >> >> >
> >> >> > Hth,
> >> >> >
> >> >> > Chip
> >> >> >
> >> >> >
> >> >> >
> >> >> > Chip Orange
> >> >> > Database Administrator
> >> >> > Florida Public Service Commission
> >> >> >
> >> >> > Chip.Orange@xxxxxxxxxxxxxxx
> >> >> > (850) 413-6314
> >> >> >
> >> >> > =3D3D3D20
> >> >> >
> >> >> >> -----Original Message-----
> >> >> >> From: jfw-bounce@xxxxxxxxxxxxx=3D3D3D20
> >> >> >> [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=3D20
> >> HP laptop
> >> >> >>=3D3D3D20
> >> >> >> Hi,
> >> >> >> I agree with you on the software conflicts, but the=3D20
> >> reason I=3D3D3D20
> >> >> >> uninstalled all these was mainly to level the playing =3D
> > field=3D3D3D20
> >> >> >> between my Dell and the HP.=3D3D3D20
> >> >> >> It's mighty hard to troubleshoot something that's not=3D20
> >> working=3D3D3D20
> >> >> >> when you have all manner of obvious software=20
> differences=3D3D3D20
> >> >> >> between a working and non-working system.
> >> >> >>=3D3D3D20
> >> >> >> To update all who are following this thread, assuming=3D20
> >> anyone=3D3D3D20
> >> >> >> is any more: I finally had another seize up a bit after =3D
> > 4pm=3D3D3D20
> >> >> >> this afternoon; this after using the system as =3D
> > consistently=3D3D3D20
> >> >> >> as one could trying to do practical, real-world work. =3D
> > The=3D3D3D20
> >> >> >> plus side is that it did take longer for the seize=20
> up to=3D3D3D20
> >> >> >> occur, but I can't get work done wondering when my =3D
> > Russian=3D3D3D20
> >> >> >> Roulette HP computer is going to blow its head off.
> >> >> >>=3D3D3D20
> >> >> >> I let the system sit a good 15 minutes and it never=3D3D3D20
> >> >> >> recovered. The touchpad did seem to work some, but=20
> the=3D3D3D20
> >> >> >> system was definitely acting extremely sluggish. =
The=3D3D3D20
> >> >> >> keyboard on the laptop also seemed somewhat=20
> functional,=3D3D3D20
> >> >> >> though again very sluggish. I still was never able =
to=3D3D3D20
> >> >> >> successfully launch Microsoft Narrator, so have no input =3D
> > on=3D3D3D20
> >> >> >> whether that would work or not. As a result of the=3D3D3D20
> >> >> >> instability, I also had to force power down the system =3D
> > yet=3D3D3D20
> >> >> >> again, which could be affecting the event log information =3D
> > -=3D3D3D20
> >> >> >> but I have no choice there, as I can't get any sort =
of=3D3D3D20
> >> >> >> control to do a controlled shutdown.
> >> >> >>=3D3D3D20
> >> >> >> I checked the event logs, as was recommended by=3D20
> >> several, and=3D3D3D20
> >> >> >> found only 1 entry in the Application log. It was=20
> DCOM,=3D3D3D20
> >> >> >> event ID 10010, and was time and date stamped at the=3D3D3D20
> >> >> >> approximate time the system froze.
> >> >> >>=3D3D3D20
> >> >> >> I'm still waiting for FS to ship my JAWS 6.0. I have =3D
> > tried=3D3D3D20
> >> >> >> to contact them twice by email about it but no one =
has=3D3D3D20
> >> >> >> responded to me as yet. Typical.=3D3D3D20
> >> >> >> Any wonder why I have so much love for FS when I get=3D20
> >> treated=3D3D3D20
> >> >> >> this way as a customer? Downloading JAWS 6 to see=20
> if it=3D3D3D20
> >> >> >> fixes the problem isn't a resolution at this point. I=3D20
> >> notice=3D3D3D20
> >> >> >> another lister has said FS told them the drivers in JAWS =3D
> > 6=3D3D3D20
> >> >> >> would even help 4.5 run better. I don't know, I just =3D
> > think=3D3D3D20
> >> >> >> this is a lousy way to treat customers with a product=3D20
> >> that I=3D3D3D20
> >> >> >> have an over $1,000 investment in. I'm in so deep with =3D
> > FS=3D3D3D20
> >> >> >> right now that I have no choice but to stay with it, =3D
> > though=3D3D3D20
> >> >> >> how much longer I'll remain a customer is debatable.
> >> >> >>=3D3D3D20
> >> >> >> This HP is a state of the art machine. It does not=20
> have=3D3D3D20
> >> >> >> crappy components on it. Any person going out to=20
> buy a=3D3D3D20
> >> >> >> laptop any time in the near future had better heed =3D
> > warning=3D3D3D20
> >> >> >> and first run every component of the machine by FS first =3D
> > to=3D3D3D20
> >> >> >> make sure everything is "compatible" with JAWS. =3D
> > Apparently=3D3D3D20
> >> >> >> that is the only way to even come close to a pleasant=3D20
> >> experience.
> >> >> >>=3D3D3D20
> >> >> >> I certainly haven't had one. I stand by my original=3D20
> >> thinking=3D3D3D20
> >> >> >> that the crux of the problem here is JAWS. The HP=3D20
> >> laptop may=3D3D3D20
> >> >> >> have to sit in my closet for several months, waiting=3D20
> >> for JAWS=3D3D3D20
> >> >> >> to reach a stable point to work on it.=3D3D3D20
> >> >> >> Meanwhile I will continue to peck away at this or that=3D20
> >> on it=3D3D3D20
> >> >> >> and perhaps eventually get it working in a stable fashion. =
=3D
> > =3D3D3D20
> >> >> >> My Dell is going on five years old and I have been =3D
> > looking=3D3D3D20
> >> >> >> forward to this much better HP for some time. It is=3D3D3D20
> >> >> >> frustrating to the extreme to not have any "bread=3D20
> >> crumbs" to=3D3D3D20
> >> >> >> follow to fix this weird freezing problem, and everyone=3D20
> >> seems=3D3D3D20
> >> >> >> as clueless as to what's causing it as I am.
> >> >> >>=3D3D3D20
> >> >> >> I will be leaving the list again soon, and wish you all =3D
> > the=3D3D3D20
> >> >> >> best with your JAWS products. I still think it's the =3D
> > best=3D3D3D20
> >> >> >> screen reader from a usage perspective; I just think=20
> JAWS=3D3D3D20
> >> >> >> needs a lot of work done on it besides adding a bunch=3D20
> >> of new=3D3D3D20
> >> >> >> features that just add to existing bugs. You may not =3D
> > agree=3D3D3D20
> >> >> >> with my opinion of the matter, and you are welcome to=3D20
> >> yours,=3D3D3D20
> >> >> >> but please respect mine and don't blast me for feeling =3D
> > the=3D3D3D20
> >> >> >> way I do right now. I'm accustomed to being able to=20
> fix=3D3D3D20
> >> >> >> problems like this one, but it's next to impossible=20
> to do=3D3D3D20
> >> >> >> when I'm battling an unknown problem that seems to have =3D
> > no=3D3D3D20
> >> >> >> solution other than grasping at straws.
> >> >> >> -Greg
> >> >> >>=3D3D3D20
> >> >> >> ----- 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
> >> >> >>=3D3D3D20
> >> >> >>=3D3D3D20
> >> >> >> > Hi Greg,
> >> >> >> >
> >> >> >> > <snip J2RE
> >> >> >> > PL] I doubt it. This is the java virtual machine and=3D20
> >> has no=3D3D3D20
> >> >> >> connection=3D3D3D20
> >> >> >> > with
> >> >> >> > jaws. For that matter none of the softwarethe that=3D20
> >> you have=3D3D3D20
> >> >> >> uninstalled=3D3D3D20
> >> >> >> > has
> >> >> >> > any connection with jaws. even QuickTime should =
not=3D3D3D20
> >> >> >> interfere in this
> >> >> >> > manner unless you are using it to play QuickTime movies.
> >> >> >> >
> >> >> >> >
> >> >> >> > Pranav
> >> >> >> > Pranav
> >> >> >> >=3D3D3D20
> >> >> >>=20
> --------------------------------------------------------------
> >> >> >>=20
> --------------------------------------------------------------
> >> >> >> -----------
> >> >> >> > Pranav
> >> >> >> >
> >> >> >> > --
> >> >> >> > To post a message to the list, send it to jfw@xxxxxxxxxxxxx
> >> >> >> > To unsubscribe from this mailing list, send a message =3D
> > to=3D3D3D20
> >> >> >> > jfw-request@xxxxxxxxxxxxx with the word unsubscribe=3D20
> >> in the=3D3D3D20
> >> >> >> subject line.
> >> >> >> > Archives located at: //www.freelists.org/archives/jfw
> >> >> >> >
> >> >> >> > If you have any concerns about the list, post=3D20
> >> received from=3D3D3D20
> >> >> >> the list, or=3D3D3D20
> >> >> >> > the way the list is being run, do not post them to =
the=3D3D20
> >> >> list. Rather=3D3D3D20
> >> >> >> > contact the list owner at jfw-admins@xxxxxxxxxxxxxx
> >> >> >> >=3D3D3D20
> >> >> >>=3D3D3D20
> >> >> >>=3D3D3D20
> >> >> >>=3D3D3D20
> >> >> >> --
> >> >> >> To post a message to the list, send it to jfw@xxxxxxxxxxxxx
> >> >> >> To unsubscribe from this mailing list, send a=20
> message to=3D3D3D20
> >> >> >> jfw-request@xxxxxxxxxxxxx with the word unsubscribe in =3D
> > the=3D3D3D20
> >> >> >> subject line.
> >> >> >> Archives located at: //www.freelists.org/archives/jfw
> >> >> >>=3D3D3D20
> >> >> >> If you have any concerns about the list, post received =3D
> > from=3D3D3D20
> >> >> >> the list, or the way the list is being run, do not post=3D20
> >> them=3D3D3D20
> >> >> >> to the list. Rather contact the list owner at=3D3D3D20
> >> >> >> jfw-admins@xxxxxxxxxxxxxx
> >> >> >>=3D3D3D20
> >> >> >>=3D3D3D20
> >> >> > --
> >> >> > To post a message to the list, send it to jfw@xxxxxxxxxxxxx
> >> >> > To unsubscribe from this mailing list, send a message =
to=3D3D20
> >> >> > jfw-request@xxxxxxxxxxxxx with the word unsubscribe=20
> in the=3D3D20
> >> >> subject line.
> >> >> > Archives located at: //www.freelists.org/archives/jfw
> >> >> >
> >> >> > If you have any concerns about the list, post=20
> received from=3D3D20
> >> >> the list, or=3D3D20
> >> >> > the way the list is being run, do not post them to the=3D20
> >> list. Rather=3D3D20
> >> >> > contact the list owner at jfw-admins@xxxxxxxxxxxxxx
> >> >> >=3D3D20
> >> >>=3D3D20
> >> >>=3D3D20
> >> >>=3D3D20
> >> >> --
> >> >> To post a message to the list, send it to jfw@xxxxxxxxxxxxx
> >> >> To unsubscribe from this mailing list, send a message to=3D3D20
> >> >> jfw-request@xxxxxxxxxxxxx with the word unsubscribe in =
the=3D3D20
> >> >> subject line.
> >> >> Archives located at: //www.freelists.org/archives/jfw
> >> >>=3D3D20
> >> >> If you have any concerns about the list, post received =
from=3D3D20
> >> >> the list, or the way the list is being run, do not post=20
> them=3D3D20
> >> >> to the list. Rather contact the list owner at=3D3D20
> >> >> jfw-admins@xxxxxxxxxxxxxx
> >> >>=3D3D20
> >> >>=3D3D20
> >> > --
> >> > To post a message to the list, send it to jfw@xxxxxxxxxxxxx
> >> > To unsubscribe from this mailing list, send a message to=3D20
> >> > jfw-request@xxxxxxxxxxxxx with the word unsubscribe in the=3D20
> >> subject line.
> >> > Archives located at: //www.freelists.org/archives/jfw
> >> >
> >> > If you have any concerns about the list, post received from=3D20
> >> the list, or=3D20
> >> > the way the list is being run, do not post them to the=20
> list. Rather=3D20
> >> > contact the list owner at jfw-admins@xxxxxxxxxxxxxx
> >> >=3D20
> >>=3D20
> >>=3D20
> >>=3D20
> >> --
> >> To post a message to the list, send it to jfw@xxxxxxxxxxxxx
> >> To unsubscribe from this mailing list, send a message to=3D20
> >> jfw-request@xxxxxxxxxxxxx with the word unsubscribe in the=3D20
> >> subject line.
> >> Archives located at: //www.freelists.org/archives/jfw
> >>=3D20
> >> If you have any concerns about the list, post received from=3D20
> >> the list, or the way the list is being run, do not post them=3D20
> >> to the list. Rather contact the list owner at=3D20
> >> jfw-admins@xxxxxxxxxxxxxx
> >>=3D20
> >>=3D20
> > --
> > 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
Other related posts:
