User Guide

Control panel message Description Recommended action
CHOSEN PERSONALITY
NOT AVAILABLE
For help press
alternates with
CHOSEN PERSONALITY
NOT AVAILABLE
To continue press
The printer job language (PJL) encountered
a request for a personality that did not exist
in the printer. The job is aborted and no
pages print.
1
Press
( H ELP button) for detailed
information.
2
Press
( U P A RROW button) and
(D OWN A RROW button) to step through
the instructions.
CLOSE TOP COVER
For help press
The top cover is open or the top-cover
switch (SW101) is defective.
1
Press
( H ELP button) for information.
2 Close the top cover.
3 Replace the top-cover switch (SW101).
See
Printer switches and sensors.
DATA RECEIVED
To print last page press
The printer received data and is waiting for
a form feed. When the printer receives
another file, the message should disappear.
Press (S ELECT button) to continue.
DETECTABLE SIZE
IN TRAY XX
For help press
alternates with
DETECTABLE SIZE IN TRAY XX
Recommend move
switch to STANDARD
A tray has been loaded with media that is a
standard size and the switch in the tray is
set to "custom."
1
Press
( H ELP button) for detailed
information.
2
Press
( U P A RROW button) and
(D OWN A RROW button) to step through
the instructions.
DISK DEVICE
FAILURE
alternates with
Ready
For menus press
A device failure has occurred on the
specified drive.
1 Printing can continue for jobs that do
not require access to the disk drive.
2
Press
(S ELECT button) to continue.
3 If the message persists, remove and
reinstall the EIO disk drive.
4 Reinitialize the EIO disk.
5 If the message persists, replace the
EIO disk drive.
DISK FILE
OPERATION FAILED
The printer received a PJL file system
command that attempted to perform an
illogical operation (for example, a command
to download a file to a nonexistent directory).
1 Printing can continue.
2
Press
(S ELECT button) to continue.
3 If the message reappears, then a
problem might exist with the software
application.
Table 7-6 Alphabetical printer messages (continued)
Display-message troubleshooting 335