🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Thread View: comp.os.netware.misc
2 messages
2 total messages Started by Daniel M. Rosenblum Fri, 17 May 1996 00:00
NetWare 3.11 (Re-initialize) print mode question
#402
Author: Daniel M. Rosenblum
Date: Fri, 17 May 1996 00:00
47 lines
3119 bytes
I am the administrator of a Novell 3.11 server which feeds
several HP LaserJet IIISi, 4, and 4M printers.  Each of
these printers is on our Ethernet (frame type Ethernet_II)
with either an Extended Systems or an HP JetDirect card.
Each one is fed by two print queues, one using PCL (and
always captured as LPT2:) and the other using PS (and always
captured as LPT3:).  The CAPTURE commands refer to PRINTCON
job definitions that are kept in a shared PRINTCON.DAT on
SYS:PUBLIC (CAPTURE.EXE has smode=5).  The PRINTCON job
definitions in turn refer to PRINTDEF printer definitions,
with the job definition for the PCL queue using the Device
Mode that sets the printer to PCL, and the definition for
the PS queue using the Device Mode that sets it to PS.  (In
other words, we use what the HP manuals call Controlled
Language Switching instead of Automatic Language Switching--
with the LaserJet IIISi, we of course don't have a choice.)

I would like to switch each printer to PostScript mode
immediately after any PCL job is printed on the printer.
(The reason I'd like to do this is that we have some Unix
machines on campus that are configured to print only to
PostScript printers, and if we have the printers always in
PostScript mode, we can print directly from those Unix
systems to our printers.)  From my reading of the Novell
NetWare 3.11 Print Server manual, if I include in the
(Re-initialize) device mode the functions that change the
printer to PostScript mode, each job using that job
definition will end with commands to switch the printer to
PostScript.

Question (if you're still with me :-) ): Will every job that
goes through the corresponding queue have the functions in
(Re-initialize) appended to it, even if the queue is
associated with the printer port without using a CAPTURE
command that refers to the PRINTCON job definition (for
instance, by going through Control Panel | Printers |
Connect in Windows 3.1x)?  If not, I don't have a way of
reliably resetting the printer to PostScript after each PCL
job, but if so, I can make a whole lot of faculty members
here very happy by enabling them to print directly off the
Unix systems (without depriving everyone of PCL printing).
-- 
Daniel M. Rosenblum, Ph.D., Microcomputer Analyst (de facto coordinator
   of computing), Faculty of Management, Rutgers University (Newark)
dmr@andromeda.rutgers.edu    180 University Ave., Newark, NJ  07102-1895
DROSENBL@gsmack.rutgers.edu         201-648-5176
Re: NetWare 3.11 (Re-initialize) print mode question
#401
Author: chapmand
Date: Sun, 19 May 1996 00:00
120 lines
4889 bytes
Howdy Doc,

The basic problem with using CAPTURE JOB=XYZ is, the PCL/PS commands you
entered into the device definition in PRINTDEF and called via the PRINTCON
jobname are transfered to the Printer as a PCL/PS header BEFORE the print
job gets to the printer. Thus you can tell it what to do BEFORE you send
data, but not after.

You CAN use CATURE JOB=XYZ with windows users, PROVIDED the Windows PC is
NOT setup to print directly to the NetWare Print Queue. If they print
directly to the queue, they will use the settings in the windows Control
Panel instead of the JOB specified in the CAPTURE command. (as a side
note, I seem to recall that you can set a PrintCon Job name in the Control
Panel settings for a printer...).

A quick note on sending embedded PCL commands to the JetDirect card. On
newer cards (ASSUME yours ARE), you MUST go into the "Advanced" section of
the printer config in JetAdmin and enter the "PJL Settings" section. From
there, UN-CHECK the three PJL boxes. If you fail to do this, the JetDirect
card will ignore the PCL commands. (PJL is Printer Job Language)

With regards to the Unix users (this is a little out of my league though),
they have no way of knowing the Language the printer is set to before they
print. You may have to have a Unix person write a shell script to set the
language to PostScript before they send a job to a printer that can't
auto-switch based on the incoming bit-stream.

Hope this helps...

Dave Chapman

In article <4nij9s$rq0@andromeda.rutgers.edu>, dmr@andromeda.rutgers.edu
(Daniel M. Rosenblum) wrote:

> I am the administrator of a Novell 3.11 server which feeds
> several HP LaserJet IIISi, 4, and 4M printers.  Each of
> these printers is on our Ethernet (frame type Ethernet_II)
> with either an Extended Systems or an HP JetDirect card.
> Each one is fed by two print queues, one using PCL (and
> always captured as LPT2:) and the other using PS (and always
> captured as LPT3:).  The CAPTURE commands refer to PRINTCON
> job definitions that are kept in a shared PRINTCON.DAT on
> SYS:PUBLIC (CAPTURE.EXE has smode=5).  The PRINTCON job
> definitions in turn refer to PRINTDEF printer definitions,
> with the job definition for the PCL queue using the Device
> Mode that sets the printer to PCL, and the definition for
> the PS queue using the Device Mode that sets it to PS.  (In
> other words, we use what the HP manuals call Controlled
> Language Switching instead of Automatic Language Switching--
> with the LaserJet IIISi, we of course don't have a choice.)
> 
> I would like to switch each printer to PostScript mode
> immediately after any PCL job is printed on the printer.
> (The reason I'd like to do this is that we have some Unix
> machines on campus that are configured to print only to
> PostScript printers, and if we have the printers always in
> PostScript mode, we can print directly from those Unix
> systems to our printers.)  From my reading of the Novell
> NetWare 3.11 Print Server manual, if I include in the
> (Re-initialize) device mode the functions that change the
> printer to PostScript mode, each job using that job
> definition will end with commands to switch the printer to
> PostScript.
> 
> Question (if you're still with me :-) ): Will every job that
> goes through the corresponding queue have the functions in
> (Re-initialize) appended to it, even if the queue is
> associated with the printer port without using a CAPTURE
> command that refers to the PRINTCON job definition (for
> instance, by going through Control Panel | Printers |
> Connect in Windows 3.1x)?  If not, I don't have a way of
> reliably resetting the printer to PostScript after each PCL
> job, but if so, I can make a whole lot of faculty members
> here very happy by enabling them to print directly off the
> Unix systems (without depriving everyone of PCL printing).
> -- 
> Daniel M. Rosenblum, Ph.D., Microcomputer Analyst (de facto coordinator
>    of computing), Faculty of Management, Rutgers University (Newark)
> dmr@andromeda.rutgers.edu    180 University Ave., Newark, NJ  07102-1895
> DROSENBL@gsmack.rutgers.edu         201-648-5176
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.


.
.
.
.
.
.
.
.
.
.
Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads