Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!rochester!uhura.cc.rochester.edu!ur-valhalla!dela
From: dela@ee.rochester.edu (Del Armstrong)
Newsgroups: comp.sys.next
Subject: Re: printer "not connected"
Message-ID: <1989Sep29.131542.5142@ee.rochester.edu>
Date: 29 Sep 89 13:15:42 GMT
References: <2187@sjuvax.UUCP> <6903@pixar.UUCP> <5384@umd5.umd.edu>
Reply-To: dela@ee.rochester.edu (Del Armstrong)
Organization: University of Rochester Department of Electrical Engineering
Lines: 35

In article <5384@umd5.umd.edu> feldman@umd5.umd.edu (Mark Feldman) writes:
> [...]
>David's problem, however, may not be hardware related.  Yesterday, or maybe
>it was the day before, two of our NeXTs forgot that they had printers.
>Things were working just fine, then they just forgot.  Trying to print from
>WriteNow would cause a PostScript PrinterDevice (or some such) error.  And
>yes, the correct printer (the only printer) was chosen.  One of the NeXTs
>magically started to see its printer again without any intervention, and the
>other NeXT was brought back to reality by a reboot.  
>
>Strange, eh?
>
>	Mark

We're having the same problem. It only started after we upgraded to 
1.0. Now, magically, the print server will start complaining about 
"malformed postscript" (something about PrinterDevice), or printers 
will suddenly cease to exist. 

Anybody know what's going on?

	Del Armstrong

	Internet    : dela@ee.rochester.edu
	UUCP        :     ...allegra!rochester!ur-valhalla!dela
	Twisted pair: (716) 275-5342
	Last resort : Hopeman 407
		      Electrical Engineering
		      University of Rochester
		      Rochester, N.Y.  14627

    +---------------------------------------------------------------------+
    | Like all black boxes, NeXT workstations are great when they work    |
    | and utterly impossible when there's a problem.                      |
    +---------------------------------------------------------------------+