Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!purdue!haven!umd5!feldman From: feldman@umd5.umd.edu (Mark Feldman) Newsgroups: comp.sys.next Subject: Re: printer "not connected" Message-ID: <5384@umd5.umd.edu> Date: 27 Sep 89 13:51:12 GMT References: <2187@sjuvax.UUCP> <6903@pixar.UUCP> Reply-To: feldman@umd5.umd.edu (Mark Feldman) Organization: University of Maryland, College Park Lines: 35 In article <6903@pixar.UUCP> loren@pixar.UUCP (Loren Carpenter) writes: >In article <2187@sjuvax.UUCP> dcarpent@sjuvax.UUCP (D. Carpenter) writes: >>After setting up my NeXT and connecting the laser printer, >>I tried to print a WriteNow file, only to receive the >>message that there was no printer connected to the Cube. ... [list of sanity checks removed] >>=============================================================== >>David Carpenter dcarpent@sjuvax.UUCP >>St. Joseph's University dcarpent%sjuvax.sju.edu@relay.cs.net >>Philadelphia, PA 19131 ST_JOSEPH@HVRFORD.BITNET > >My printer was "disconnected" too. It turned out that the problem was a >blown fuse in the printer power supply. It blows if it sees a spike over >400 volts. I called NeXT & they explained how I could fix it myself. I did >& it's fine. New printers have a better power supply, I'm told. ... [how to replace a fuse removed] > > Loren Carpenter > ...{ucbvax|sun}!pixar!loren A while back, during a thunderstorm, one of our NeXT laser printers blew a fuse, too. It's too bad that the fuse is not accessable without having to perform surgery. 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