Table of Contents
Advertisement
POSSIBLE
PROBLEM
CAUSE
A PostScript error
The print job may
page prints.
not be PostScript.
The optional tray is
The printer driver
not selected in the
has not been
driver.
configured to
recognize the
optional tray.
When printing a
The resolution
document in
setting in the printer
Macintosh with
driver may not be
Acrobat Reader 6.0
matched with the
or higher, colors
one in Acrobat
print incorrectly.
Reader.
Common Windows problems
CONDITION
"File in Use"
Exit all software applications. Remove all
message appears
software from the printer's startup group, then
during installation.
restart Windows. Reinstall the printer driver.
"General Protection
Close all other applications, reboot Windows
Fault", "Exception
and try printing again.
OE", "Spool 32", or
"Illegal Operation"
messages appear.
"Fail To Print", "A
These messages may appear during printing.
printer timeout error
Just keep waiting until the machine finishes
occurred" messages
printing. If the message appears in standby
appear.
mode or after printing has been completed,
check the connection and/or whether an error
has occurred.
Refer to Microsoft Windows User's Guide that came with your
computer for further information on Windows error messages.
SOLUTION
Make sure that the print
job is a PostScript job.
Check to see whether
the software application
expected a setup or
PostScript header file to
be sent to the machine.
Open the PostScript
driver properties, select
the Device Settings tab,
and set the tray option of
the Installable Options
section to Installed.
Make sure that the
resolution setting in your
printer driver matches
the one in Acrobat
Reader.
SUGGESTED SOLUTIONS
Troubleshooting_ 122
Common Linux problems
CONDITION
The machine does
•
Check if the printer driver is installed in your
not print.
system. Open Unified Driver Configurator and
switch to the Printers tab in Printers
configuration window to look at the list of
available machines. Make sure that your
machine is displayed on the list. If not, open
Add new printer wizard to set up your
device.
•
Check if the machine is started. Open
Printers configuration and select your
machine on the printers list. Look at the
description in the Selected printer pane. If its
status contains Stopped string, press the
Start button. After that normal operation of
the machine should be restored. The
"stopped" status might be activated when
some problems in printing occurred. For
instance, this could be an attempt to print a
document when the port is claimed by a
scanning application.
•
Ensure the port is not busy. Since functional
components of machine (printer and scanner)
share the same I/O interface (port), the
situation of simultaneous access of different
"consumer" applications to the same port is
possible. To avoid possible conflicts, only one
of them at a time is allowed to gain control
over the device. The other "consumer" will
encounter "device busy" response. You
should open ports configuration and select
the port assigned to your machine. In the
Selected port pane you can see if the port is
occupied by some other application. If this is
the case, you should either wait for
completion of the current job or press the
Release port button, if you are sure that the
present application is not functioning properly.
•
Check if your application has special print
option such as "-oraw". If "-oraw" is specified
in the command line parameter, then remove
it to print properly. For Gimp front-end, select
"print" -> "Setup printer" and edit command
line parameter in the command item.
•
The CUPS (Common Unix Printing System)
version distributed with SuSE Linux 9.2
(cups-1.1.21) has a problem with ipp (Internet
Printing Protocol) printing.Use the socket
printing instead of ipp or install a later version
of CUPS (cups-1.1.22 or higher).
The machine does
It is a known problem that occurs when a color
not print whole
machine is used on version 8.51 or earlier of
pages, and output is
Ghostscript, 64-bit Linux OS, and has been
printed on half the
reported to bugs.ghostscript.com as Ghostscript
page.
Bug 688252.The problem is solved in AFPL
Ghostscript v. 8.52 or above. Download the
latest version of AFPL Ghostscript from
http://sourceforge.net/projects/ghostscript/ and
install it to solve this problem.
SUGGESTED SOLUTIONS
Advertisement
Table of Contents
