[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

5965.0. "Data area passed to system call is too small" by LAOSS1::UDICK_ST (It can't be too easy to use ...) Wed Sep 06 1995 15:00

T.RTitleUserPersonal
Name
DateLines
5965.1REGENT::ALEEI don't like stuff that sucksMon Sep 18 1995 20:2630
5965.2Having the same problem - here's a logNPSS::BENZI'm an idiot, and I voteTue Jan 09 1996 15:5799
5965.3REGENT::ALEEI don't like stuff that sucksTue Jan 09 1996 16:3726
5965.4ping works.NPSS::BENZI'm an idiot, and I voteTue Jan 09 1996 18:0320
5965.5more attempts and failures.NPSS::BENZI'm an idiot, and I voteWed Jan 10 1996 12:0418
5965.6NPSS::BENZI'm an idiot, and I voteWed Jan 10 1996 14:4011
5965.7NPSS::BENZI'm an idiot, and I voteWed Jan 10 1996 14:445
5965.8NPSS::BENZI'm an idiot, and I voteTue Jan 16 1996 13:044
5965.9REGENT::ALEEI don't like stuff that sucksWed Jan 24 1996 10:2620
5965.10automagically, it works now.NPSS::BENZI'm an idiot, and I voteThu Feb 01 1996 11:2312
5965.11NPSS::GLASERSteve Glaser DTN 2267212 LKG1-2/E10 (G17)Fri Feb 02 1996 09:108
5965.12still brokenNPSS::GLASERSteve Glaser DTN 2267212 LKG1-2/E10 (G17)Mon Apr 08 1996 03:136
5965.13You're not alone!7283::CERNESEDan, Agglutinator, COHESION SEE EngineeringWed Jul 03 1996 15:5422
5965.14still a problem,7283::CERNESEDan, Agglutinator, COHESION SEE EngineeringMon Jul 08 1996 11:1618
5965.15REGENT::ALEEAndy Lee (I don't like stuff that sucks)Wed Aug 28 1996 19:5238
5965.16still happening NT 4.0 SP2NPSS::GLASERSteve Glaser DTN 226-7212 LKG1-2/W6 (G17)Thu Apr 17 1997 19:1926
    as an update, we are STILL getting this problem on NT 4.0 SP2
    
    I strongly disagree with the previous comment that "it's no big deal on
    a workstation".
    
    1. The message gives no indication about what's wrong or how to fix it.
    
    2. There is no indication as to whether the job is OK or should be
    killed.
    
    3. If I try to kill the job it doesn't appear to go away
    
    4. I get a dialog box possing to the top of my screen disrupting other
    work, causing keystrokes to go to the wrong applications, etc.
    
    A service SHOULD NEVER POP A DIALOG BOX.  That's what the event log is
    for.  I recognize that it's not DEC's service that's doing this mess,
    but something in our printer / network / software is aggravating a poor
    design from Microsoft.
    
    Steveg
    
    (Ian McSomethingOrOther from DEC UK Customer support left me voice mail
    this morning asking whether I was still having this problem.  That
    triggered this tirade.  Unfortunately he did't leave much of a contact
    point on voice mail.)
5965.17KERNEL::MEGARITYI remember when Rock was youngFri Apr 18 1997 05:2520
RE: .-1


>    (Ian McSomethingOrOther from DEC UK Customer support left me voice mail
>    this morning asking whether I was still having this problem.  That
>    triggered this tirade.  Unfortunately he did't leave much of a contact
>    point on voice mail.)
 

	I am the person who tried to contact you about this problem - have
	to say that I've been called a lot of things in my time, but never
	"McSomethingOrOther" ...    :-)

	Anyway, we've got an internal site in Holland who is seeing
	this problem - they are running NT4 SP2.
	Our intention is to install the latest version of the NT 
	PrintServer software ( V51-12I.EXE ) to see if that helps.


/Ian
5965.18Still happens with V51-12IRDVAX::LEVYRun Like an AntelopeFri Apr 18 1997 08:345
    From experience, I'll say that V51-12I does not cure the problem.  We
    see it mostly with DEClaser 5100s.
    
    	dave
    
5965.19I see this 10 times a day TAY2P1::HOWARDWhoever it takesFri Apr 18 1997 19:1118
    This problem is happening all over Digital sites in the Maynard area. 
    Someone mentioned TAY2 earlier, and the problem is definitely here.  If
    you leave notification turned on, the problem goes away, but then
    people get notified that some other person with the same last name has
    a job that completed.  
    
    This problem is a *major* pain.  Why can't the symbiont just wait
    forever the way VMS does?  Or just log the event and start up later. A
    printer runs out of paper, the message pops up, somebody adds paper,
    but the queue stays stopped until the SPOOLER service is stopped and
    restarted or the message is cleared.  Users complain about this problem
    daily.  We switched all all LPS printers to TCPIP on the VMS side but
    it didn't help.  It happens with any printer connected to an NT server.  
    
    If somebody wants to know NT printing isn't more popular, this is the
    reason. 
    
    Ben