[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference 7.286::postscript_printing

Title:Digital PostScript printers and their associated software
Moderator:REGENT::LASKOHER
Created:Wed Jan 24 1990
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:7230
Total number of notes:31971

7142.0. "200 pages printed on LPS17 - LIMCHK" by HGOSPS::MICKWIDLAM () Fri Apr 04 1997 03:18

    I have a customer newly purchased a PrintServer 17 with 16M memory.
    When trying to print a PS document which is around 200 pages, the error
    %LPS-W-LIMCHK was prompted and the job was ended. This happened in an
    Alpha VMS V6.2 and DCPS V1.3. In his old VMS V5.5 system, he got
    VMERROR (with CPS version not known).
    
    I passed him an article about LIMCHK. He tried to set /MaxFonCache to
    250000 and the problem seemed disappearred.
    
    My customer then has the following questions:
    
    1. he usually print report more than 1000 pages, will this problem
    happened again?
    
    2. if so, before he buy more memory, what value he can set to?
    
    3. on a PrintServer 20, he use only 12M memory and can print all his
    report without problem. Now on PrintServer 17 with 16M memory, print
    only 200 pages already got VM problem. Actually how much memory he
    should use in his new printer? His reports don't have pictures, only
    got text and some text highlight, underline and so on.
    
    Is there anyone out there have any idea of his questions?
    
    Thanks and regards,
    Mickwid.
T.RTitleUserPersonal
Name
DateLines
7142.1Buy another 8MB, its very cheap nowdaysNECSC::HARVEYPrintserver Support- America's ZoneFri Apr 04 1997 12:1318
    Mickwid,
    
    
    	The LPS17 printers were released with the minimum amount of
    physical memory, 16MB. This 16MB will provide about ~590KB of virtual
    memory. The major reason for this was when the LPS17 printer was
    released PC memory was at its peak for memory prices. 
    
    	Now the PC memory has hit rock bottom it is an easy solution to add
    more memory. By adding another 8MB this provides 24MB physical and
    ~6.5MB virtual. This additional memory solves most of the limit check,
    virtual memory problems seen with the LPS17.
    
    	I would not have the customer play with the /MaxFonCache valuse,
    just have him obtain another 8MB memory simm.
    
    
    Renis
7142.2can the customer use PC memory from other PCs?HGOSPS::MICKWIDLAMSun Apr 06 1997 22:4311
    re .1
    
    >    memory. The major reason for this was when the LPS17 printer was
    >    released PC memory was at its peak for memory prices. 
    Do you mean that LPS17 is using the memory which is similar to those of
    PC memory (simm RAM, EDO, etc.)? Can the customer use those the memory
    from their old PCs? I have to be aware on this if the customer can buy
    memory from outside.
    
    Thanks,
    Mickwid.
7142.3CSCMA::CSCMA::KOECKMon Apr 07 1997 11:335
    	The simm used on the lps17 are the same as PC simms.  You have to
    have 70 NS simm, faster won't work, and you can't use anything larger
    than 8 meg.  The lps17/300 requires parity.  The /600 dpi does not.
    
    	Tom
7142.4REGENT::POWERSMon Apr 07 1997 15:3310
Separate from the question of whether and what kind of memory to add
is the question of whether and when VM error or limit check will come back 
for print jobs of this type.
The answer to that question is that they probably will, but it can't be 
predicted from the information presented whether it will be page 201,
1000, or 9999.

The more important question is what version of LPS is in use?

- tom]
7142.5V5.1HGOSPS::MICKWIDLAMMon Apr 07 1997 22:457
    re .4
    
    >The more important question is what version of LPS is in use?
    LPS V5.1, downline load from an Alpha.
    
    Thanks,
    Mickwid.
7142.6REGENT::POWERSTue Apr 08 1997 15:4512
>    >The more important question is what version of LPS is in use?
>    LPS V5.1, downline load from an Alpha.

This means that the PostScript code is level 2, which is already the most
efficient version of the language that exists for memory management.
A file that has size-sensitive behavior in any level 2 environment will
probably always have some size sensitivity, regardless of the amount of
memory installed.  It's a sign of bad memory management in the created
PostScript code, and it will almost always be just a metter of time (or pages)
until the next level of failure occurs.

- tom]