SCOUG-HELP Mailing List Archives

>> Next Message >>

Date:	Tue, 25 Jun 2002 10:33:01 PST7
From:	"J. R. Fox" <jr_fox@pacbell.net >
Reply-To:	scoug-help@scoug.com
To:	scoug-help@scoug.com
Subject:	SCOUG-Help: Re: system instability

Content Type: text/plain

=====================================================
If you are responding to someone asking for help who
may not be a member of this list, be sure to use the
REPLY TO ALL feature of your email program.
=====================================================

> Sounds like you had an intermittent hardware problem. Moving boards
> around often can clean these up.

I hope that's not any indication of flakey H/W. As long as it _is_ gone and stays gone,
I'll let it go at that.

> >[I still think that W2K will raise _some_ objections to PNP being turned
> >OFF, sooner or later, and would like to have a dialogue with any of you
> >who also run that OS (off-List is fine), about some related issues.]
>
> Well, if you are that worried, you could trun it on and see what happens.
> If your traps come back, you have some information.

Yeah, if I have time to mess with it, and feel in an experimental mood that day.

> >Perhaps Steven can enlighten us as to just what it is about things like
> >the Warp Centre or a screen saver that makes them a tripwire for the kind
> >of resource / stability / CMOS problems I've been
>
> My experience does not match yours. WarpCenter does tend to hang for
> some. It's a poor implementation of a WPS object. However, keeping the
> .ini's clean is usually enough to prevent this. The only screen saver I
> use is the on built into the WPS. I've never had it cause hangs. Perhaps
> others that are more aggressive in attempting to save power may cause
> problems. None of these have caused CMOS upsets in my experience.

That was far from my normal experience. It's just that _while_ these resource &
CMOS things were going on, the Warp Center had a propensity to collide with
just about anything and crash, my screen saver would freeze and die unpredictably,
and NS could not be left running unattended for any appreciable length of time or
it would go to a black screen and die. Sometimes there would be Popuplog entries
on these events, sometimes not. I don't think these items _caused_ any problem with
CMOS, but rather were reacting erratically to one. Anyway, with the system apparently
stable again (so far), none of that is occurring. The one thing I've seen that hasn't
returned
to normal is that on some W4 boots my cordless wheelmouse driver isn't loading (but
Config.Sys isn't visibly bouncing it), so the wheel function isn't there. On other
boots it does load. *Stock* ECS seems to support this device fully, so it hasn't been
an issue there. I may have to try an alternate driver for W4, or futz with the load
order of the one I have.

> > NS Communicator I can readily imagine being a serious
> >test, since it probably stresses the system more than anything else most
>
> NS will hang if you restart it too many times. However, I believe that
> this was actually an OS/2 base defect and was fixed in one of the MCP's.

But not as of FP-15 ? In which case, I couldn't retro-fix W4 . . . .

I've discovered that the NS 4.61 that comes with ECS is a year older than the last public
release from 7/01, which seems a bit odd.

> The NS crashes that generate popuplog entries are just code defects.

Interesting, and not terribly surprising. They never managed to fix several of these in
4.61, so I just hope they'll do better maintenance on the Mozilla releases.

Jordan

=====================================================

To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-help".

For problems, contact the list owner at
"rollin@scoug.com".

=====================================================

Return to [ 25 | June | 2002 ]

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.