HP3000-L Archives

December 2000, Week 2

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Doug Becker <[log in to unmask]>
Reply To:
Doug Becker <[log in to unmask]>
Date:
Tue, 12 Dec 2000 09:48:26 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (44 lines)
I don't necessarily know a lot about this area (but necessity is making me a quick study).

We had some issues concerning printing and found that <plug> Printpath from RAC Consulting has resolved all or our problems with network printing.

The software is reasonably priced, Richard A. Corn is extremely competent and knows his stuff, Espul has been around for a long time, is stable and works well.

Thanks to Printpath, we will actually be able to dispense with our DTC shortly--we have one printer to go and our technician has committed to connecting our remaining impact printer this week.

It turns out that Printpath has a log that can be examined to find out what happened should something go awry. </plug>

Does HP provide a log file to determine what might have gone wrong in the print process for network printing?

_________________________________
Wirt Atmar wrote:

>>> Wirt Atmar <[log in to unmask]> 12/12 8:39 AM >>>
Jim,

> I am calling the HPRC, but not all of this stuff is supported by HP (mainly
>  the printers) so any help is appreciated.

With no other no knowledge than what you printed and the fact that you had a
power failure, I would presume that you also have had a hardware failure (or
at least a device that was confused on restart). I'm presuming that all of
your printing is done through network printing and JetDirect cards.

To isolate the problem, I would first cycle the power on the printer
connected to LDEV 114 to see if that helps. If it does, great. If it doesn't,
and you have a spare, identical printer, I would swap them out.

If that fixes the problem, you now know that you have a bum printer. If it
doesn't, then it suggests the HP3000 is the root cause.

If it is the HP3000, I would then do a shutdown and a start norecovery. If
that fixes the problem, great. Something merely got confused on powerup after
the failure. If it doesn't, and all of your other printers are working, then
it has to be some sort of configuration problem with that specific LDEV.

If reconfiguring the printer/spooler/npconfig files doesn't fix the problem,
then I'd just give up and buy a more reliable computer system. However, I
really don't think you'll get to this point in the decision tree.

Wirt Atmar

ATOM RSS1 RSS2