[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

7209.0. "Windows NT generic PostScript driver and VMS errors" by NECSC::HARVEY (Printserver Support- America's Zone) Thu May 22 1997 16:06

    Customer is reporting VM exhausted errors when  printing files to a 
    TurboLPS20 printer from a WNT 4.0 server. They are using an application 
    called ViewLogics that a prior version generated postscript files itself. 
    Now the latest version uses the generic postscript driver from NT 4.0 to 
    generate the code stream.
    
    	The customer has noticed that the postscript file sizes doubled 
    from the old to the new. Same drawing on B sized paper was ~1.5MB in
    size from the old version of the application. Now using the NT driver
    with the LPS20 PPD it is ~3.5MB.
    
    	I have tested the file on a Turbo20 with a postscript level I
    interpreter and it causes the VM exhausted errors. When printer to a
    Turbo20+ (level II interpreter) it will print.
    
    	The file is at NECSC::D_FSS:[harvey]bad.ps
    
    If this was a W95 or WIN3.1 client,  We would ask the customer to
    select clear memory per page and conform to Adobe specs in the WIN3.1 
    driver or Optimize for portability for W95. 
    
    For the NT driver there is not much to change under the device
    settings. Is there a clear memory per page, or Optimize the driver
    features?
    
    Renis
T.RTitleUserPersonal
Name
DateLines
7209.1REGENT::LASKOTim - Printing Systems BusinessThu May 22 1997 17:0510
    By "generic PostScript driver" do you mean the the PostScript printer
    driver that comes with Windows NT 4.0, PSCRIPT, or some other "generic"
    PostScript driver that Viewlogic added, or what? I assume that the
    "turbo PrintServer 20 v48.3" driver that comes with Windows NT was used.
    
    There are no generic panacea switches in the Windows NT driver,
    nominally because it produces better PostScript. :-)
    
    I assume that the VMOption (memory setting) has been set up to match
    the amount of memory in the customer's PrintServer.
7209.2The have lowered the VM settingNECSC::HARVEYPrintserver Support- America's ZoneThu May 22 1997 18:5918
    Tim,
    
    	Correct me if my understanding of the NT print system is wrong. :-)
    NT has the generic postscript driver PSCRIPT.DLL, PSCRIPT.UID and its
    associated help files. Our printer "drivers" are only PPD files that
    setup the correct behavior for the particular printer.
    
    	NT has other generic driver files for PCL, plotter and others.
    These generic drivers also use discriptor files to setup the behavior
    for the printer/s.
    
    	The customer said that they had worked this problem with ViewLogic
    and Viewlogic uses NTs generic driver. The customer has already tried
    the idea of lowering the memory setting. They have used it at 800KB and
    500KB with no help. Are there other items that can be modified in the 
    PPD for the printer to change the way the postscript stream is generated?
    
    Renis