SOLVING PROBLEMS 5.195The N-up setting does notwork correctly for someof my documents.The N-up feature is achieved through post-processing ofthe PostScript data that is being sent to the printingsystem. However, such post-processing can only beadequately achieved if the PostScript data conforms to theAdobe Document Structing Conventions. Problems mayarise when using N-up and other features relying on post-processing if the document being printed isn’t compliant.I am using BSD lpr(Slackware, Debian, olderdistributions) and someoptions chosen in LLPRdon’t seem to take effect.Legacy BSD lpr systems have a hard limitation on thelength of the option string that can be passed to theprinting system. As such, if you selected a number ofdifferent options, the length of the options may beexceeded and some of your choices won’t be passed to theprograms responsible for implementing them. Try to selectless options that deviate from the defaults, to save onmemory usage.I am trying to print adocument in Landscapemode, but it printsrotated and cropped.Most Unix applications that offer a Landscape orientationoption in their printing options will generate correctPostScript code that should be printed as is. In that case,you need to make sure that you leave the LLPR option toits default Portrait setting, to avoid unwanted rotations ofthe page that would result in a cropped output.Some pages come out allwhite (nothing isprinted), and I am usingCUPS.If the data being sent is in Encapsulated PostScript (EPS)format, some earlier versions of CUPS (1.1.10 and before)have a bug preventing them from being processedcorrectly. When going through LLPR to print, the PrinterPackage will work around this issue by converting the datato regular PostScript. However, if your applicationbypasses LLPR and feeds EPS data to CUPS, the documentmay not print correctly.I can’t print to a SMB(Windows) printer.To be able to configure and use SMB-shared printers (suchas printers shared on a Windows machine), you need tohave a correct installation of the SAMBA package thatenables that feature. The “smbclient” command should beavailable and usable on your system.My application seems tobe frozen while LLPR isrunning.Most Unix applications will expect a command like theregular “lpr” command to be non-interactive and thusreturn immediately. Since LLPR is waiting for user inputbefore passing the job on to the print spooler, very oftenthe application will wait for the process to return, and thuswill appear to be frozen (its windows won’t refresh). This isnormal and the application should resume functioningcorrectly after the user exits LLPR.Problem Possible Cause and Solution