Condition |
| Suggested solutions |
|
|
|
| • | Check if a document is loaded into the |
|
| machine. |
| • | Check if your machine is connected to |
|
| the computer. Make sure if it is |
|
| connected properly if I/O error is |
|
| reported while scanning. |
| • | Check if the port is not busy. Since |
|
| functional components of MFP (printer |
|
| and scanner) share the same I/O |
|
| interface (port), the situation of |
|
| simultaneous access of different |
|
| “consumer” application 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. This can usually happen |
The machine does not |
| while starting scan procedure, and |
| appropriate message box will be | |
scan. |
| |
| displayed. | |
|
| |
|
| To identify the source of the problem, |
|
| you should open ports configuration and |
|
| select the port assigned to your |
|
| scanner. Port’s symbol /dev/mfp0 |
|
| corresponds to LP:0 designation |
|
| displayed in the scanners’ options, /dev/ |
|
| mfp1 relates to LP:1 and so on. USB |
|
| ports start at /dev/mfp4, so scanner on |
|
| USB:0 relates to /dev/mfp4 respectively |
|
| and so forth sequentially. In the |
|
| Selected port pane you can see if the |
|
| port is occupied by some other |
|
| application. If this is the case, you |
|
| should wait for completion of the current |
|
| job or should press Release port button, |
|
| if you are sure that the present port’s |
|
| owner is not functioning properly. |
|
|
|
| • | Check if Gimp |
|
| “Xsane: Device dialog.” on the “Acquire” |
|
| menu. If not, you should install Xsane |
|
| |
I cannot scan via Gimp |
| You can find Xsane |
| Gimp on Linux distribution CD or Gimp | |
| home page. For the detail information, | |
|
| refer to the Help for Linux distribution |
|
| CD or Gimp |
| If you wish to use other kind of scan | |
| application, refer to the Help for | |
| application. | |
|
|
|
Condition | Suggested solutions | |
|
| |
| Please avoid changing print job | |
| parameters (via LPR GUI, for example) | |
| while a print job is in progress. Known | |
I encounter error | versions of CUPS server break the print | |
job whenever print options are changed | ||
“Cannot open port | and then try to restart the job from the | |
device file” when | beginning. Since Unified Linux Driver | |
printing a document. | locks port while printing, the abrupt | |
| termination of the driver keeps the port | |
| locked and therefore unavailable for | |
| subsequent print jobs. If this situation | |
| occurred, please, try to release the port. | |
|
| |
The printer does not | Incompatibility between the PDF file and | |
the Acrobat products: | ||
print PDF file correctly. | Printing the PDF file as an image may | |
Some parts of | ||
solve this problem. Turn on Print As | ||
graphics, text, or | ||
Image from the Acrobat printing options. | ||
illustrations are | ||
NOTE: It will take longer to print when you | ||
missing. | ||
| print a PDF file as an image. | |
|
|
Common Macintosh problems
Condition | Suggested solutions | |
|
| |
| Incompatibility between the PDF file and | |
The printer does not print | the Acrobat products: | |
Printing the PDF file as an image may | ||
PDF file correctly. Some | ||
solve this problem. Turn on Print As | ||
parts of graphics, text, or | ||
Image from the Acrobat printing options. | ||
illustrations are missing. | ||
NOTE: It will take longer to print when | ||
| ||
| you print a PDF file as an image. | |
|
| |
The document has |
| |
printed, but the print job | Update your Mac OS to OS 10.3.3. or | |
has not disappeared from | ||
higher. | ||
the spooler in Mac OS | ||
| ||
10.3.2. |
| |
|
| |
Some letters are not | This problem is caused because Mac | |
OS can not create the font during the | ||
displayed normally | ||
Cover page printing. English alphabet | ||
during the Cover page | ||
and numbers are displayed normally at | ||
printing. | ||
the Cover page. | ||
| ||
|
|
14.17 <Troubleshooting>