Subject: | |
From: | |
Reply To: | |
Date: | Wed, 16 Jun 1999 11:00:53 -0700 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
Our experience has been somewhat the same, although we never did implement
HP's network printing solution -- we just evaluated it and found enough
problems to convince us to *not* implement it. We currently use ESPUL's
PrintPath NLM solution, and have for years with great success. Recently,
our server group asked us to get rid of the NLM solution to avoid a
Y2K-related upgrade to the Novell server on which the PrintPath NLM's
reside. Hopefully, we've persuaded against this -- I think that, until
HP's solution is more solid, I don't want to do the proverbial "fix what
ain't broke" routine. Don't want more grief ... got plenty of grief. :-)
Lee
From: Mark Bixby <[log in to unmask]> on 06/16/99 10:12 AM
Please respond to [log in to unmask]
To: [log in to unmask]
cc: (bcc: Lee Gunter/BCBSO/TBG)
Subject: Re: [HP3000-L] Network Printing & LPQ series printers
Lane Rollins writes:
>
> Does the SERIAL_PRINTER_SIMULATION help the funky printing problem? Does
it
> cause any other weird side effects?
Mark Bixby replies:
<some snipped>
So my standard method for migrating a DTC serial printer to a network
printer
is:
1) Configure the printer using MPE FOS network printing.
2) Wait for any user complaints.
3) If there are complaints, switch the printer to Minisoft's NetPrint92.
So
far NetPrint92 solves all complaints. (We acquired NetPrint92 when we were
still on MPE/iX 5.0 and HAD to start doing network printing before we were
ready update to 5.5)
|
|
|