At 09:05 AM 5/28/2004 -0600, F. Alfredo Rego wrote:
>At 17:35 -0700 5/27/04, Vance, Jeff H (Cupertino) wrote:
>
> >1. "Network printing to work with non-HP printers by adding a
> >pcl_supported = false option in NPCONFIG.PUB.SYS. If this option is
> >paired with pjl_supported = false, the spooler would just dump the ASCII
> >data to the printer and strip any PCL sequences from the beginning of
> >the spool file.

Why?  The printer might support PCL just fine, but not HP's status
checking, which
I thought was the original basis for the request...simply disable the
status checking
that the driver does.



>  No device status checking and reporting, failure
> >recovery, imbedded PCL sequences, or handling of CCTL information would
> >be done.

So if there is no imbedded PCL code offered to the device for initialization,
PCL stripped from the beginning of the file, how is one to take advantage of
the printer's capability given HP doesn't support it and won't support it
anyway?
Seems it's more the status handshaking that's more a problem than anything
else, when it comes to most printers on the market today that can be
shared on a network....I know I've had my share of problems with it.

The same may be true if the device is a plotter, and so forth.  So make the
stripping of PCL from the file another switch...



>  The customer would be responsible for ending each of the spool
> >files with a form feed command to flush the last page. HEADON would not
> >be supported."
>
>Nice.
>
>Why "The customer would be responsible for ending each of the spool
>files with a form feed command to flush the last page"?
>
>How about something like "end_with_form_feed = [true/false]" in
>NPCONFIG.PUB.SYS"?

Ditto!

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *