[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

7058.0. "Windows NT 4.0 and Digital Network Printing - errors" by RDVAX::LEVY (Run Like an Antelope) Fri Jan 24 1997 16:26

We're running our entire printing environment on Windows NT Server 4.0
(Service Pack 2 currently).  This server is not a domain controller, but
does participate in a Windows NT domain.  The server runs TCP/IP and
NetBEUI as protocols using a DE435 card.

PrintServer machines also have DCPS queues on a couple of VMS systems, but
the majority of printing is from Windows NT and Windows 95 clients.

We boot all of our PrintServers from NT using Digital Network Printing.

We configure and manage queues for a number of DEClaser 3500 and 5100
printers from the same NT server.

Lastly, we run 2 LSR20000+ machines with queues on the same NT server.

I'm documenting below a couple of problems we're experiencing that I
believe are related to the Digital Network Printing software.  Any
information or hints as to what is going on would be greatly appreciated.

The Application Event Log on the NT Print Server has many many STOP errors of
the following form (edited for readability here):

1/24/97	10:38:45 AM	Digital Network Printing SW	
	Error	None	1	
	N/A	CST-PRINTERS	
	Internal error in file b:\decpsmon\decpsmon.c at
	line 1540. Last error = 124. 
1/24/97	10:38:45 AM	Digital Network Printing SW	
	Error	None	1	
	N/A	CST-PRINTERS	
	Internal error in file b:\decpsmon\decpsmon.c at
	line 1540. Last error = 124. 
1/24/97	10:38:45 AM	Digital Network Printing SW	
	Error	None	1	
	N/A	CST-PRINTERS	
	Internal error in file b:\decpsmon\decpsmon.c at
	line 1540. Last error = 124. 
1/24/97	10:38:45 AM	Digital Network Printing SW	
	Error	None	1	
	N/A	CST-PRINTERS	
	Internal error in file b:\decpsmon\decpsmon.c at
	line 1540. Last error = 124. 

Interestingly, these stop abruptly at about 11:30 this morning and we see
some (but not NEARLY the same number and frequency) of these INFORMATION
messages:

1/24/97	12:12:43 PM	Digital Network Printing SW	
	Information	None	9	
	N/A	CST-PRINTERS	The description for Event ID ( 9 )
	in Source ( Digital Network Printing SW ) could not be found. 
	It contains the following insertion string(s): , , , LIBPRN.

LIBPRN is one of the DEClaser 3500 printers on the system.

Also, yesterday we had the SPOOLSS process crash on the server with the
following information:

1/23/97	8:41:44 AM	DrWatson	
	Information	None	4097	
	N/A	CST-PRINTERS	The application, exe\spoolss.dbg, generated 
	an application error The error occurred on  1/23/1997 @  8:41:41.512 
	The exception generated was c0000005 at address 77e8fcae 
	(MessageBoxExA) 

I can provide the DRWATSON.LOG if it would be useful, but it is kind of big
to post here.

Thanks in advance for any info.

	dave

T.RTitleUserPersonal
Name
DateLines
7058.1More problemsRDVAX::LEVYRun Like an AntelopeWed Jan 29 1997 07:458
    The error 1 errors have returned in the Application log.
    
    Also, we had another SPOOLSS crash yesterday.
    
    Any ideas?
    
    	dave
    
7058.216mb memory on LPS17 is not enoughRDVAX::LEVYRun Like an AntelopeWed Feb 05 1997 16:2414
Thanks to Liz Holland of the CSC, I believe this problem is resolved.

We've had 2 learnings out of this experience:

   1 - Don't try to load and configure LPS17s with less than 32mb memory
       from Windows NT.

   2 - Don't put 8mb 60ns memory into LPS17s.  They will pass the power-on
       self-test but will never actually see the additional memory.  You
       must use 70ns memory simms. 

Thanks again, Liz!

	dave
7058.3REGENT::POWERSThu Feb 06 1997 09:4814
>            <<< Note 7058.2 by RDVAX::LEVY "Run Like an Antelope" >>>
>                    -< 16mb memory on LPS17 is not enough >-
>
>   2 - Don't put 8mb 60ns memory into LPS17s.  They will pass the power-on
>       self-test but will never actually see the additional memory.  You
>       must use 70ns memory simms. 

Maybe you mean don't use 80ns memory?
60ns memory is faster than 70ns memory, and I have never heard
of a case where faster memory will fail when slower memory works.

Almost all available SIMMs today are 70ns or faster.

- tom]
7058.4Don't mix speedsRDVAX::LEVYRun Like an AntelopeThu Feb 06 1997 11:167
    No.  I mean don't use 60ns memory.  The memory on-board is 70ns and the
    8mb simm with the printer is 70ns.  When we mixed with 60ns simms for
    the additional 16mb, the printer passed self-test but never actually
    saw the memory.  Remote console would report 8 + 8.
    
    	dave
    
7058.5What is the spec for the LPS1X-UE/F memoryNECSC::HARVEYPrintserver Support- America&#039;s ZoneThu Feb 06 1997 12:0815
    I have had customers report the same thing. It must be 70nSec memory 
    or it will not work. Another issue reguarding memory came up too. A
    customer installed a 8MB memory simm and it failed to be seen. it was
    Texas Instruments TMS418160DX simm. This simm is a 1Mx16 DRAM simm vs.
    the more standard 4Mx4 simm. Customer used the memory in one of their
    PCs instaed and will order 70 nSec 8MB memory simms.
    
    So the real question is what is the spec for the LPS 17/32+ memory
    simms? Customers say that we Digital charge too much for our memory as
    compared to what is out on the market. I have seen ads out here in
    Silicon Valley (San Jose, CA.) with a 4MB stick going for $16.00 and a 
    8MB stick at $25.00.
    
    
    Renis
7058.6Still crashingRDVAX::LEVYRun Like an AntelopeWed Feb 12 1997 12:0213
    Print spooler crashed again today.  I'm not tracing anymore because I
    thought the problem was solved.  Darn it!
    
    2/12/97	8:25:55 AM	DrWatson	Information	None	
    4097
    	N/A	CST-PRINTERS
    	The application, exe\spoolss.dbg, generated an application error
    	The error occurred on  2/12/1997 @  8:25:52.709 The exception
    	generated was c0000005 at address 77e8fcae (MessageBoxExA)
    
    
           dave
    
7058.7Presence Detect?CPEEDY::YOUNGPaulFri Feb 14 1997 10:037
    Just a guess - the LN17 may require presence detect on the memory?
    
    There are a few pins on SIMMS which tell the system how many meg
    and what speed the memory is.  There is a list of the jumpers on
    http://www.pny.com/Tech/presencedetect.stm that you may find useful.
    
    				Paul
7058.8Not that unusualSHRMSG::HOWARDBenThu Feb 20 1997 16:318
    Our NT spoolers crash all the time, and we haven't even upgraded them to
    4.0.  We've working with Microsoft, but so far not much has been
    resolved.  I've never had a problem booting 16MB LPS17's from NT V3.51
    other than using PRINTSERVER 17/600.  It seems that NT spoolers don't 
    handle errors very well.  A printer that is out of paper seems to cause
    crashes or hangs.  
    
    Ben