Fujitsu eLux NG S26361-F2600-L134 Manual Do Utilizador
Códigos do produto
S26361-F2600-L134
www.
myelux
.com
eLux
®
NG
Build # 27
63
If the output format of the application differs from the local printer format, you will have to
activate the filter.
activate the filter.
File format
Convert to
Filter Setting
UNIX text
DOS
text “Text”
PostScript
PCL2
“PCL2”
If the application output format is the same as the printer format, disable the filter (“None”).
Troubleshooting
Printing is a complex topic beyond the scope of this manual. For help with a specific printer,
please contact the printer manufacturer. As a guide, below is help for some common
questions.
1. PostScript file – PostScript printer (Filter = “None”)
Most local applications – such as the local browser or Acrobat Reader – generate PostScript
output. To print PostScript files to a PostScript printer, the filter should be set to “None.”
If your printer prints a large amount of ASCII text, your file could be PCL. To check the file
format, in the print dialog select “Print to file” and save to a network drive or to the local
directory “tmp”. Open the resulting *.prn file using Notepad or vi. If the first line starts with %!
the file is PostScript.
2. PostScript file – PCL printer (filter should be set to “PCL2”)
For this filter option to be displayed, the PCL package must be installed on the Thin Client
(“PCL printer support” located in the base OS). By default, it is not installed.
3. Is the printing problem affecting multiple devices or just one device? If one device, make
sure the Thin Client is working properly – try printing to other printers, accessing network
drives, contacting other devices, etc. If it cannot, it is not a printer problem. If it can, see if the
print job reaches the printer (most printers have a status line). If it does, the problem is most
likely the file format. See 1 and 2 above.
4. Attempt to communicate with the printer on a protocol level. If the printer has an IP address,
ping it from a local shell (see “4.8.1 XTerm (Local Shell)”). If you are unsuccessful, or if the
problem is affecting multiple Thin Clients, it may be a network problem.
5. If the application stops responding, or “hangs,” you may have a performance problem. For
example, the Thin Client buffers print data in main memory. How large is the main memory
compared to the file you are trying to print? The more complex the file, the larger it will be.
Graphics and color increase file size. PostScript files are often much larger than the original
file. If your main memory is small, printing large files could cause a delay if the printer is not
ready at the time a print task is running (see 6). Avoid this by checking the printer status in
advance and by setting a “Maximum printer response” time-out.
6. Hardware problem: Verify that the printer is on and ready, that the paper tray is full, and that
there are no error messages in the display.
Printing is a complex topic beyond the scope of this manual. For help with a specific printer,
please contact the printer manufacturer. As a guide, below is help for some common
questions.
1. PostScript file – PostScript printer (Filter = “None”)
Most local applications – such as the local browser or Acrobat Reader – generate PostScript
output. To print PostScript files to a PostScript printer, the filter should be set to “None.”
If your printer prints a large amount of ASCII text, your file could be PCL. To check the file
format, in the print dialog select “Print to file” and save to a network drive or to the local
directory “tmp”. Open the resulting *.prn file using Notepad or vi. If the first line starts with %!
the file is PostScript.
2. PostScript file – PCL printer (filter should be set to “PCL2”)
For this filter option to be displayed, the PCL package must be installed on the Thin Client
(“PCL printer support” located in the base OS). By default, it is not installed.
3. Is the printing problem affecting multiple devices or just one device? If one device, make
sure the Thin Client is working properly – try printing to other printers, accessing network
drives, contacting other devices, etc. If it cannot, it is not a printer problem. If it can, see if the
print job reaches the printer (most printers have a status line). If it does, the problem is most
likely the file format. See 1 and 2 above.
4. Attempt to communicate with the printer on a protocol level. If the printer has an IP address,
ping it from a local shell (see “4.8.1 XTerm (Local Shell)”). If you are unsuccessful, or if the
problem is affecting multiple Thin Clients, it may be a network problem.
5. If the application stops responding, or “hangs,” you may have a performance problem. For
example, the Thin Client buffers print data in main memory. How large is the main memory
compared to the file you are trying to print? The more complex the file, the larger it will be.
Graphics and color increase file size. PostScript files are often much larger than the original
file. If your main memory is small, printing large files could cause a delay if the printer is not
ready at the time a print task is running (see 6). Avoid this by checking the printer status in
advance and by setting a “Maximum printer response” time-out.
6. Hardware problem: Verify that the printer is on and ready, that the paper tray is full, and that
there are no error messages in the display.