Brakus Please enter a title. HP LaserJet dtn Printer. Everything is now defaulting to outline. In Windows NT, you cannot configure a printer to print an error message.
|Genre:||Health and Food|
|Published (Last):||16 July 2014|
|PDF File Size:||12.66 Mb|
|ePub File Size:||5.41 Mb|
|Price:||Free* [*Free Regsitration Required]|
Troubleshoot a problem further if you receive a non-specific PostScript error message, or if a PostScript error occurred without a message.
To troubleshoot a PostScript error, isolate when the problem occurs to determine if it is a system-level, application-specific, file-specific, or element-specific problem. After you isolate when the problem occurs, you can eliminate likely causes until you solve the problem. Isolate system-level printing problems Do you receive the error from more than one application? If the same problem occurs from more than one application, the cause is most likely a problem at the system level.
Damaged fonts, damaged system files, damaged printer drivers, insufficient hard disk space, network problems, or hardware problems commonly cause system-level problems. If the problem occurs only from one application, see the "Isolating Application-Specific Problems" section.
Make sure that you use an up-to-date PostScript device driver for example, printer driver. Or, use the version of the driver required by the application.
You also need plenty of free hard disk space when sending a file to a PostScript interpreter, especially when you print a large file. Make sure that free hard disk space is defragmented. If you print to an external PostScript device, secure loose connectors for example, cables, switch boxes by unplugging and replugging them.
But if a connection is loose, the symptoms of a problem can be unclear. The device receives small jobs only, or its driver appears only intermittently in the Chooser in Mac OS. To determine if the application or a specific file causes the error, create a file with only a simple element, such as a rectangle.
If this test file does cause the error, the application software could be damaged. Isolate file-specific problems Do you receive the error only with a specific file or files? If the error occurs only with a specific file, the file could have the wrong print settings selected for your PostScript interpreter. Or, it could be damaged or contain a problem element for example, a damaged graphic.
Save the new file using the Save As command, and then see if the error occurs with the new file. If the error does occur, run any built-in diagnostic routines your application offers.
Isolate element-specific problems Do you receive the error only with a specific page or elements on a page? After you rule out a damaged file as the cause, a damaged or incorrectly written element or font is likely causing the error. An element or combination of elements that requires more memory than is available could be causing the error. If the error occurs with a range of pages, look for common elements on those pages. If you can print all elements individually or in small groups, the combination of elements you print requires more memory than is available.
To isolate the element or elements that cause the problem, make a copy of the file. Then send groups of pages to the PostScript interpreter. If a group causes an error, print one page at a time from that group.
Continue sending pages until you narrow down the problem page. You can then isolate the elements causing the problem by removing elements from each page.
If an element that causes the problem is text or an element you created in the application, re-create the element. For text elements, you can also try using a different font for example, reformat the text using a different type of font. Reinstall it from the original media. If the element causing the problem is an imported graphic, first try reimporting the graphic. If the error still occurs, open the graphic in the application in which it was created, resave it with a different name.
Make sure that it prints from that application, and then reimport the graphic. If the imported graphic still causes the error, try resaving it in a different format. Or, export it from a different application, or simplify it so that it requires less memory. An imported graphic can cause a PostScript error if it contains damaged or incorrectly written information. It can also cause an error if it is too complex for the PostScript interpreter for example, it requires more memory than is available.
If the file causes a PostScript error because it is too complex, simplify it and see if it prints.
Offending command: roll
Postscript error: stackunderflow