Offending command: Put

The put command is too generic to allow for easy troubleshooting. You may have to check the page of general troubleshooting tips (a link is in the column in the left hand column).


  • PostScript errors caused by the PostScript command put are sometimes caused by custom fills. Check all drawings in your lay-out whether they contain custom files and either replace or recreate these.
  • “Put” errors may also be related to a damaged font. Reinstall all fonts used in your document from the original disks, both on your Mac or PC and your RIP. This is a known problem with Linotype PostScript level 1 RIPs when printing from FreeHand 7.
  • A PostScript error invalidaccess error, offending command put can be caused by the use of an incorrect driver. I once got around this error by switching from an Agfa PPD to a generic Scenicsoft PPD while creating PostScript code for Scenicsoft Preps. Using a PPD driver of a recent device for outputting on an older RIP can cause similar problems.
  • I once spend half a day troubleshooting a file from a customer that kept generating rangecheck errors, offending command put. It turned out that some of the about 20 spot colors in the file had round brackets in them (one colour was named ‘bordeaux (tarif 1)’) and this was unacceptable for the in-rip separation algorithm of the RIP. Changing the names of the spot colors solved the issue. The customer never experienced the problem himself because he always output preseparated files.
  • A rangecheck error, offending command put can occur while trying to print complex Xpress 3.3 files containing lots of nested EPS files (Illustrator files which contained other Illustrator EPS files which themselves contained EPS files of scanned images). Here are three solutions for this problem:
  1. Make a back-up copy of XPress and open this copy with ResEdit. Open the PSHD resource and look for line 1007. Use the search command to find the following piece of text: /A 128 array def. Change the 128 to a higher value (like 250 or even 500). Save the altered application and use it to print the file. Although this solution works, it may still generate the “rangecheck” error if you print lots of pages in one go.
  2. You can also send the file as a composite file and have the RIP do the separation. On Agfa RIPs, this workflow is called “Inrip separaration” or ‘Composite printing’.
  3. Download the following piece of PostScript code to the Postscript level II RIP and then print your file. I cannot guarantee that this code works with non-Agfa RIPs.

true 0 startjob
userdict begin
/F18 /array load def
/array { dup 128 eq { pop 50000 } if F18 } bind def

This piece of code will remain active until the RIP is rebooted or reset. You can add it to user/boot but then the first line should not be included.