Postscript Printer Error
Contents |
to solve such an error? Why do PostScript errors even exist? What is a PostScript error? Every PostScript device contains a RIP (or Raster Image Processor). This is error limitcheck offending command image a computer that translates the pages you want to print from PostScript error undefined offending command stack into a format that the PostScript device understands. If the RIP encounters an error while performing this translation, it postscript errors returns a PostScript error message to the device that send the file. The error can be caused by bugs in the PostScript code itself, data corruption, limitations of the RIP and PostScript
Syntax Error Offending Command Nostringval
device processing the file, incompatibilities between different devices or applications, bad karma,… What do PostScript errors look like? A PostScript error has two parts: the error and the offending command. Take a look at a typical PostScript error: %%[Error: limitcheck; Offending command: image ]%% The error tells you exactly what problem the RIP encountered while processing your file. In the example, it is a error syntax error offending command stack limitcheck. Thankfully, there are a limited number of errors that can occur on PostScript devices. I think there are about 30 or so but I could be wrong. The offending command signals what specific PostScript command (or operator as they are called) was being processed by the RIP when the error occurred. In some cases, the offending command doesn't really look like a command but it is a series of random characters. This means the RIP has encountered some information in your printfile that it considers to be a PostScript operator but is not. This can happen with corrupted images, bad network connections and so on. Can PostScript errors be solved? Well, this website wouldn't make much sense if that wasn't possible. Of course, it helps if you know the famous Adobe Red Book by heart. But knowledge of the PostScript language is no prerequisite for troubleshooting PostScript errors. In reality, it is often a matter of luck. Errors caused by bugs in applications or drivers are sometimes well documented and easy to resolve. The same is true for errors caused by limitations or bugs in the software o
the Basics section to determine exactly what PostScript error and offending command you got hit with. Then do one of the following (not necessarily in that order but this seems to be the most logical approach to me): 1. Try printing one more error undefined offending command stack xerox time Take a deep breath, look through the window during a couple of seconds, check
Error Unregistered Offending Command Xshow
all the parameters in the Print windows and print again. Sometimes a simple mistake like setting the orientation wrong causes errors. Have a
Error Undefined Offending Command New
colleague print the job. He or she may instantly see what you did wrong. Everybody makes a stupid mistake once in a while (I once spent 2 hours troubleshooting a ‘broken' Mac, only to find out the https://www.prepressure.com/postscript/troubleshooting/basics keyboard wasn't plugged in properly). This is definitely the first thing to try if no other documents or applications cause similar problems. 2. Cut the print job into smaller pieces Don't print large jobs with many pages or big images in one go. Print a couple of pages at the time or even one single page at the time. This makes it easier for both your computer and the RIP to process the file. Always https://www.prepressure.com/postscript/troubleshooting/tips try this approach if you have an older printer or RIP. 3. Search for solutions for your specific error Look up both the error and offending command in my database of PS errors and offending commands. This may give you a clue as to what to do next. Check out other sites as well by searching the web for pages about the specific PostScript error or offending command. Another alternative is to post your question on the b4print prepress forum. 4. Switch to another computer, app, driver,… Print the job from another computer, from another version or copy of the application used to create the file and try switching drivers. Always print the file to another PostScript device as well. If the same error occurs, you are at least sure the error is somehow related to your document or the way it is created or printed. The reverse is not true: if a document prints on one device but not on another, this does not mean that that device is unreliable or faulty. The inconsistency may be caused by differences in drivers, memory and hard disk capacity, installed fonts,workflow or PostScript revisions. PostScript aims to be device independent but it obviously isn't. I always print troublesome files to file and then use Acrobat Distiller to check whether it generates the same error. 5. Rese
the links to other people's web pages are now broken. Why can't they stay still! Quick contents Introduction - what is an error? What is the error? http://boffin.quite.com/ps/errors.htm Use an error handler Still no error details? Things to try first Checking for corrupt graphics About us PostScript error details (alphabetical by error name) HP Laserjet Error codes (30 PS ERROR nn) Introduction - what is an error? This is intended for people who have to try and deal with PostScript errors. You don't need to know anything about PostScript, except that it is a language that gets sent to a printer. By 'errors' offending command I mean specific errors detected by a PostScript printer, that make it stop printing. This won't help you if the results are complete, but not what you expect. Good information on errors is hard to come by. The information here may help. It is long and detailed, and best used as a reference. Still, be prepared for a long struggle. Sometimes a file simply cannot be printed on a particular printer, particularly if it is old error undefined offending or has limited memory. (The amount of memory supplied by default with many printers is not adequate for complex graphics or using many fonts). Some people will be dealing with PostScript files sent to them, that they must try to print; others will be generating the PostScript themselves. Not all of the advice in this document can be followed by both groups. Although I refer to 'printers' throughout, you might be using a printer, a printing or previewing package on a PC or workstation, or a high-end typesetter. This file is definitely not intended to help people writing their own PostScript. The discussion is confined to errors likely to be found when a program writes the PostScript on your behalf. If writing PostScript you will need a good manual, and lots of patience! A particularly unpleasant source of problems is bugs, either in the programs that write the PostScript, or in a few cases in the PostScript interpreter itself. As bugs can cause anything to happen, this document may not be much use either, but I have included information on some bugs that have been discovered in common software. Good luck! You may need it. What is the error? PostScript errors are reported in various ways. Before you can get anywhere with a problem you need to know the error name and offending c
be down. Please try the request again. Your cache administrator is webmaster. Generated Mon, 24 Oct 2016 11:09:07 GMT by s_wx1126 (squid/3.5.20)