Samsung SCX 4826FN User Manual (ENGLISH) - Page 75

Common Windows problems, Fail To Print, - scanner driver

Page 75 highlights

CONDITION SUGGESTED SOLUTIONS Blank areas appear at the bottom of each page or on other pages, with a small strip of text at the top. You may have chosen the wrong paper settings in the user option setting. For details about paper settings, see page 30. Common Windows problems CONDITION SUGGESTED SOLUTIONS "File in Use" message appears during installation. Exit all software applications. Remove all software from the StartUp Group, then restart Windows. Reinstall the printer driver. "General Protection Fault", "Exception OE", "Spool32", or "Illegal Operation" messages appear. Close all other applications, reboot Windows and try printing again. "Fail To Print", "A printer timeout error occurred." messages appear. These messages may appear during printing. Just keep waiting until the machine finishes printing. If the message appears in ready mode or after printing has been completed, check the connection and/or whether an error has occurred. Refer to the Microsoft Windows documentation that came with your computer for further information on Windows error messages. Common Linux problems CONDITION The machine does not print. Some color images come out all black. SUGGESTED SOLUTIONS • Check if the printer driver is installed in your system. Open Unified Driver configurator and switch to the Printers tab in Printers configuration window to look at the list of available printers. Make sure that your machine is displayed on the list. If not, invoke Add new printer wizard to set up your device. • Check if the printer 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 printer should be restored. The "stopped" status might be activated when some problems in printing occurred. For instance, this could be an attempt to print document when port is claimed by a scanning application. • 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. You should open ports configuration and select the port assigned to your printer. 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 owner 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 later version of CUPS (cups-1.1.22 or higher). This is a known bug in Ghostscript (until GNU Ghostscript version 7.05) when the base color space of the document is indexed color space and it is converted through CIE color space. Because Postscript uses CIE color space for Color Matching System, you should upgrade Ghostscript on your system to at least GNU Ghostscript version 7.06 or later. You can find recent Ghostscript versions at www.ghostscript.com. Troubleshooting_ 75

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138

Troubleshooting
_ 75
Common Windows problems
Common Linux problems
Blank areas appear
at the bottom of each
page or on other
pages, with a small
strip of text at the
top.
You may have chosen the wrong paper settings
in the user option setting. For details about
paper settings, see page 30.
CONDITION
SUGGESTED SOLUTIONS
“File in Use”
message appears
during installation.
Exit all software applications. Remove all
software from the StartUp Group, then restart
Windows. Reinstall the printer driver.
“General Protection
Fault”, “Exception
OE”, “Spool32”, or
“Illegal Operation”
messages appear.
Close all other applications, reboot Windows
and try printing again.
“Fail To Print”, “A
printer timeout error
occurred.” messages
appear.
These messages may appear during printing.
Just keep waiting until the machine finishes
printing. If the message appears in ready mode
or after printing has been completed, check the
connection and/or whether an error has
occurred.
Refer to the Microsoft Windows documentation that came with your
computer for further information on Windows error messages.
CONDITION
SUGGESTED SOLUTIONS
CONDITION
SUGGESTED SOLUTIONS
The machine does
not print.
Check if the printer driver is installed in your
system. Open Unified Driver configurator
and switch to the Printers tab in Printers
configuration window to look at the list of
available printers. Make sure that your
machine is displayed on the list. If not, invoke
Add new printer wizard to set up your device.
Check if the printer 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 printer
should be restored. The “stopped” status
might be activated when some problems in
printing occurred. For instance, this could be
an attempt to print document when port is
claimed by a scanning application.
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. You should open ports
configuration and select the port assigned to
your printer. 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 owner 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 later
version of CUPS (cups-1.1.22 or higher).
Some color images
come out all black.
This is a known bug in Ghostscript (until GNU
Ghostscript version 7.05) when the base color
space of the document is indexed color space
and it is converted through CIE color space.
Because Postscript uses CIE color space for
Color Matching System, you should upgrade
Ghostscript on your system to at least GNU
Ghostscript version 7.06 or later. You can find
recent Ghostscript versions at
www.ghostscript.com.