IBM 4400-006 - 4400 Model 006 B/W Direct Thermal, Руководство пользователя

Страница: 175 / 326

Printing Related
175
•
Is the Ethernet Interface configured as the queue’s “Currently
Attached Server”? If not, make sure you have associated the
queue and the printer. See “Novell Host Configuration” on page
132.
•
Is there a hold on the print job? If you select the job from
PCONSOLE’s CURRENT PRINT JOB ENTRIES, change the
User Hold or Operator Hold to “no.”
•
If you look in PCONSOLE’s CURRENT QUEUE STATUS
within the PRINT QUEUE INFORMATION menu, is the server
configured to service entries in this queue? It is possible to turn
servicing off here.
If you have followed the suggestions above and are still having
printing problems, try rebooting the Ethernet Interface. Then either
review every step you took when configuring the Ethernet Interface
or try redoing the setup, paying special attention to each step
explained in “Novell Host Configuration” on page 132.
The Job Prints Incorrectly
This category can be broken down into several sub-categories such
as lost characters, garbled data, extra banner pages, or blank
pages at the end of a job. However, the reason for these mishaps
can generally be traced back to the printing mechanism used on
your Novell system. Consider these points when configuring your
print method (e.g., CAPTURE, NPRINT, etc.):
•
Did you include the “No Tabs” option?
•
Did you specify “No Banner” with PostScript printers?
•
Did you turn off banner pages and form feeds if this is already
taken care of within an application or on the Ethernet Interface?
Doubling up these types of print features is easy to do since
these options are provided both on the Ethernet Interface (in a
model) and within the print command.
•
Are you running the latest version of PSERVER (later than
1.22)? If not, upgrade the PSERVER software.
•
In a PSERVER setup, did you ensure that the printer name
(e.g.,
d1prn
) was set up as “Defined Elsewhere”?