SCOUG-HELP Mailing List Archives
Return to [ 16 | 
December | 
2002 ]
<< Previous Message << 
 
 
 
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.  
=====================================================  
 
Hi   
Since years my printmonbufsize looks like:  
 
PRINTMONBUFSIZE=2048,134,2048  
 
Why ?  
 
On LPT1 is the printer and   
on LPT3 is PMfax !  
 
With 2048 both of the ports are on max settings ;-)  
 
 
Also for years I used /IRQ for the PRINT01.SYS statement in the  
CONFIG.SYS.  
Since a while I am using SLPR and now it looks like:  
 
BASEDEV=PRINT01.SYS /MCP  
 
 
I do assume that the freezing of the system cannot beeing solved  
by   
settings like this !? I believe there is another problem existing  
and   
causing this freezing behaviour !?  
 
I am sorry that I am unable to assist more efectively ;-(  
Cheers, svobi   
 
 
 
 
 
 
 
 
hmotin@attglobal.net on 17.12.2002 03.19.37  
Please respond to scoug-help@scoug.com  
To:	scoug-help@scoug.com  
cc:	   
Subject:	SCOUG-Help: Re: system freeze-up during print jobs  
 
> I'm guessing that default must have changed sometime after  
WP-9, which is probably where  
> you are at.  
 
Actually, the change started with the release of Warp 3.0. May I  
suggest  
that you change the PRINT01.SYS statement back to the default of  
not  
having the /IRQ parameter. That is, use the OS/2 default of  
polling the  
printer port, instead of using interrupts.  
 
Also, if I were you, I would change the printer buffer to the  
largest  
available. If you use LPT1 as your normal printer port, then that  
would  
be:  
 
PRINTMONBUFSIZE=2048,134,134  
 
just like mine. If you use LPT2, then the line will be:  
 
PRINTMONBUFSIZE=134,2048,134  
 
If you use LPT3, it becomes:  
 
PRINTMONBUFSIZE=134,134,2048  
 
You have to have a buffer size for all three printer ports, LPT1,  
LPT2  
and LPT3. The minimum is 134, the maximum is 2048.  
 
If you make those 2 changes, you might see some improvement!  
HCM  
 
 
__________________________________________________________________  
________________________  
 
"J. R. Fox" wrote:  
>   
> > > > 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  
 
 
 
 
************************************************************  
***   >>>    Say  NO  to  HTML in Mail and News    <<<   ***  
***   ++++++++++++++++++++++++++++++++++++++++++++++++   ***  
***   >>>   AGAINST  TERROR   +++   AGAINST  WAR   <<<   ***  
************************************************************  
 
=====================================================  
 
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".  
 
=====================================================  
 
  
<< Previous Message << 
Return to [ 16 | 
December | 
2002 ] 
  
  
The Southern California OS/2 User Group
 P.O. Box 26904
 Santa Ana, CA  92799-6904, USA
Copyright 2001 the Southern California OS/2 User Group.  ALL RIGHTS 
RESERVED. 
 
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.
 
 |