Filter
Top Products
166 TROUBLESHOOTING THE M208: Novell Problems
?
The job prints but it comes out incorrectly
This category really can be broken down into several sub-categories such as lost char-
acters, garbled data, extra banner pages, or blank pages at the end of the job. However,
the reason for these mishaps can generally be traced to the printing mechanism used
on your Novell system. These points should be considered when configuring your
print method (i.e. 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 formfeeds if this is already taken care of within
an application or on the M208? Doubling up of these types of print features is
easy to do since these options are provided both on the M208 (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”?
• Is the timeout option in the CAPTURE command set high enough so the printer
doesn’t time out before the print processing has had a chance to complete? This
can be a problem with graphic jobs.
Some other things to consider when garbled data persists are:
• tab expansion (xtab) set on (in a model) with graphic jobs,
• the right driver for the printer if printing from within Windows,
• cable used between the M208 and the printer,
• type of flow control being used on the M208 and a serial printer.
With other print methods, the only thing to remember here is to configure the print job
for Byte Stream. This will pass the data to the M208 untouched.
For additional information on these suggestions or on various Novell printing mecha-
nisms, please refer to your NetWare user manuals.
?