Dell 1815dn Multifunction Mono Laser Printer - Manual (Page 147)

Common Windows Problems
Common Linux Problems
I can't view the Help file. To view the Help file, you need to have Microsoft Internet Explorer 4 service pack 2 or above.
I can't use Network Scan Manager. Check your operating system.
Supporting operating systems are Microsoft Windows 98/Me/NT4.0/2000/XP/Server 2003/Vista.
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.
"Error Writing to LPTx" message appears. • Ensure that the cables are connected correctly, the machine is on.
• This message may also appear if bi-directional communication is not turned on in the 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 standby mode or after printing has been completed, check the connection and/or
whether an error has occurred.
NOTE: Refer to Microsoft Windows 98/Me/2000/XP/Server 2003/Vista User's Guide that came with your PC for further information on Windows
error messages.
Condition Suggested solutions
The printer doesn't print. • Check if the printer driver is installed in your system. Open MFP configurator and switch to the Printers tab
in Printers configuration window to look at the list of available printers. Make sure that your printer 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 printer 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 MFP port is claimed by a scanning application.
• Check if the MFP port is not busy. Since functional components of MFP (printer and scanner) share the
same I/O interface (MFP port), the situation of simultaneous access of different "consumer" application to
the same MFP 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
MFP 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 printer does not appear on the scanners
list. • Check if your printer is attached to your computer. Make sure that it is connected properly via the USB
port and is turned on.
• Check if the scanner driver for your printer is installed in your system. Open MFP Configurator, switch to
Scanners configuration, then press Drivers. Make sure that driver with a name corresponding to your
printer's name is listed in the window.
• Check if the MFP port is not busy. Since functional components of MFP (printer and scanner) share the
same I/O interface (MFP port), the situation of simultaneous access of different "consumer" application to
the same MFP 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 while starting scan procedure, and appropriate message box appears.
• To identify the source of the problem, you should open MFP ports configuration and select the port
assigned to your scanner. MFP 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.
The printer doesn't scan. • Check if a document is loaded into the printer.
• 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 MFP port is not busy. Since functional components of MFP (printer and scanner) share the same
I/O interface (MFP port), the situation of simultaneous access of different "consumer" application to the
same MFP 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
while starting scan procedure, and appropriate message box will be displayed.
To identify the source of the problem, you should open MFP ports configuration and select the port
assigned to your scanner. MFP 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.