SCOUG-HELP Mailing List Archives

<< Previous Message << >> Next Message >>

Date:	Mon, 16 Dec 2002 11:21:59 PST8
From:	"J. R. Fox" <jr_fox@pacbell.net >
Reply-To:	scoug-help@scoug.com
To:	scoug-help@scoug.com
Subject:	SCOUG-Help: Re: system freeze-up during print jobs

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.
=====================================================

> > > Do you have the /IRQ parameter on your PRINT01.SYS statement in CONFIG.SYS?
> >
> > Always had that one, in every OS/2 installation.

Peter said:

> If I remember correctly, the Warp Center cpu meter hits 100% when you
> don't have /IRQ. Jordan, what does your Warp Center cpu meter do when
> this happens?

I seldom pay much attention to the Warp Center cpu meter. Instead, I've been relying on
the cpu meter built into the C-A-D Cmdr. status bar (which is optional for C-A-D users).
It rarely ventures anywhere in the vicinity of 100 % -- usually when certain particular
websites do something funky that NS 4.61 can't well cope with. (Not sure yet if Mozilla
successfully avoids this, in the same situation. I only have Mozilla on the eCS partition,
and only NS 4.61 on the W4 / FP-9 partition. I expect this will gradually change, but so
far I continue to spend the majority of my time on the latter.)

By the way and unrelated, a few weeks back, I tried Steven's idea of using one of those
system analysis util.s to try and uncover why 5 % to 8 % cpu utilization seems to be the
"resting state" (no app.s running, apart from C-A-D itself) in my eCS, whereas it is 0 % in
W4. I had already banished the eCS Clock program, so *something* is still siphoning off
cpu cycles in eCS. I found a couple of _apparent_ culprits, wrote them down, and now
cannot find that piece of paper ! It seemed to me they might have been items that run in
W4 also, but maybe not. I may have to run that test again.

Subsequently, Harry added:

> Interesting! I don't have this parameter in my config.sys. I stopped
> using it, when Warp went from the IRQ to the polling method as the
> default for parallel ports. I haven't had any problems without the IRQ
> parameter. In fact, one of the things I like best about Warp is that my
> stuff goes to the printer really fast. And while the printer is
> outputting, I can continue using Warp. That contrasts markedly with
> Windoze, where I have to wait for the printer to finish, or nearly
> finish, before I can use the system again.

I'm guessing that default must have changed sometime after WP-9, which is probably where
you are at.

> On the other hand, I have the following line for the LPT1, LPT2 and LPT3
> buffer size:
>
> PRINTMONBUFSIZE=2048,134,134

Mine = 134,134,134 for eCS, and = 1024,1024,1024 for W4.

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 [ 16 | December | 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.