Samsung CLP-600 N-up feature is achieved through post, Some of my, Documents, Am using BSD lpr

Problem	Possible Cause and Solution
The N-up setting does	The N-up feature is achieved through post-
not work correctly for	processing of the PostScript data that is sent to the
some of my	printing system. However, such post-processing can
documents.	only be adequately achieved if the PostScript data
	conforms to the Adobe Document Structing
	Conventions. Problems may arise when using N-up
	and other features that rely on post-processing if
	the document being printed isn’t compliant.
I am using BSD lpr	Legacy BSD lpr systems have a hard limitation on
(Slackware, Debian,	the length of the option string that can be passed to
older distributions)	the printing system. As such, if you selected a
and some options	number of different options, you may have
chosen in LLPR don’t	exceeded the length of the options and some of
seem to take effect.	your choices won’t be passed to the programs
	responsible for implementing them.Try to select
	fewer options that deviate from the defaults, to
	save on memory usage.
I am trying to print a	Most Unix applications that offer a Landscape
document in	orientation option in their printing options will
Landscape mode, but	generate correct PostScript code that should be
it prints rotated and	printed as is. In that case, you need to make sure
cropped.	that you leave the LLPR option set to its default
	Portrait setting, to avoid unwanted rotations of the
	page that would result in cropped output.
Some pages come out	If the data being sent is in Encapsulated PostScript
all white (nothing is	(EPS) format, some earlier versions of CUPS (1.1.10
printed), and I am	and before) have a bug preventing them from being
using CUPS.	processed correctly. When going through LLPR to
	print, the Printer Package will work around this
	issue by converting the data to regular PostScript.
	However, if your application bypasses LLPR and
	feeds EPS data to CUPS, the document may not
	print correctly.
I can’t print to an SMB	To be able to configure and use SMB-shared printers
(Windows) printer.	(such as printers shared on a Windows printer), you
	need to have a correct installation of the SAMBA
	package that enables that feature. The “smbclient”
	command should be available and usable on your
	system.
My application seems	Most Unix applications will expect a command like
to be frozen while	the regular “lpr” command to be non-interactive
LLPR is running.	and thus return immediately. Since LLPR is waiting
	for user input before passing the job on to the print
	spooler, very often the application will wait for the
	process to return, and thus will appear to be frozen
	(its windows won’t refresh). This is normal and the
	application should resume functioning correctly
	after the user exits LLPR.

Problem	Possible Cause and Solution
How do I specify the	It can be specified in the “Add Printer” dialogue of
IP address of my SMB	the configuration tool, if you don’t use the CUPS
server?	printing system. Unfortunately, CUPS currently
	doesn’t allow you to specify the IP address of SMB
	printers, so you will have to be able to browse the
	resource with SAMBA in order to be able to print.
Some documents	Some versions of CUPS, especially those shipped
come out as white	with Mandrake Linux before the 8.1 release, have
pages when printing.	some known bugs when processing PostScript
	output from some applications. Try upgrading to the
	latest version of CUPS (at least 1.1.14). Some RPM
	packages for the most popular distributions are
	provided as a convenience with this Linux Printing
	Package.
I have CUPS and some	There may be some local options defined in your ~/
options (such as N-	.lpoptions file, which are manipulated by the
up) seem to be always	lpoptions command. These options are always used
enabled even though I	if not overridden by LLPR settings. To get rid of all
don’t choose them in	options for a printer, run the following command,
LLPR.	replacing “printer” with the name of the queue:
	lpoptions -x printer
I configured a printer	Most printing systems will not run as the super-user
to print to a file, but I	but as a special user (usually “lp”). Therefore, make
get “Permission	sure that the file you have chosen to print to is
denied” errors.	accessible to the user owning the spooler daemon.
On my PCL (or GDI)	Unfortunately, some Unix applications may generate
printer, I sometimes	non-compliant PostScript output that may not be
get error messages	supported by Ghostscript, or even the printer itself
printing instead of my	in PostScript mode. You can try to capture the
document.	output to a file and view the results with Ghostscript
	(gv or ghostview will allow you to do so
	interactively) and see if you get error messages.
	However, since the application is probably at fault,
	contact your software vendor to inform them of the
	issue.
Some color images	This is a known bug in Ghostscript (until GNU
come out all black.	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.

7.18

Solving Problems