Comments on: PostScript error: limitcheck

By: deno

deno — Tue, 24 Jan 2012 19:50:35 +0000

I m having this error on a 4700 color laserjet network printer. It starts spitting out pages non stop with this error.. anyone has an idea if this is software or hardware. Also I have all latest driver and firmware updates.. driver I am suing is PCL6.. any help would be appreciated

Regards
deno

By: Adrian

Adrian — Thu, 10 Feb 2011 13:18:56 +0000

very interesting article.
I am getting an error:
PS limitcheck error, offending command “setpagedevice”

Anybody have an ideea?

By: jeff

jeff — Thu, 14 Oct 2010 09:02:39 +0000

Sometimes the easiest way to removed embedded control sequences is to copy and paste the affected section to notepad, tidy up the text you want preserved, then copy and paste it back.

The affected text will p;obably need to be tidied up afterwards to make it consistant with the rest of the text but an effective way to remove unwanted (and unseen) sequesnces.

By: Ashley

Ashley — Fri, 20 Aug 2010 19:16:59 +0000

I am getting this post-script error also…
I am creating publishing PDFs from a WORD document and uploading them to our site.
I have no problems printing them with the HP2840 Color Laser Printer from the file kor from the website. My boss can’t seem to print them either from the transfered file (from my computer to his) or from the website.
He is running Windows 7 with Office Suite 2007.
I’m running Vista 64-bit with Office Suite 2007.
I even tried publishing the file from his WORD.
He has had clients also contact him saying they were have problems printing the PDFs also.
Do you have any clue what is going on?
Thanks in advance!

By: IT-Green recycling

IT-Green recycling — Wed, 11 Nov 2009 15:36:40 +0000

Interestingly, I’m currently getting a limitcheck error on an HP4700- less than 2 years old! >Our now defunct 4600 never had this issue when printing the exact same file!

By: laurens

laurens — Wed, 24 Sep 2008 21:01:44 +0000

Back in the olden days (meaning: 10 years ago) printservers would often have their own set of data that would be appended to every printjob, essentially increasing the complexity of the job. That was sometimes enough to make a device run out of memory. I don’t know if it still makes much of a difference nowadays.

By: John Gilbert

John Gilbert — Mon, 22 Sep 2008 13:10:44 +0000

This is a good article about Postscript limitcheck errors. I do have one question, however. You say not to print using a printer queue. Could you explain your reasons?

I work in a prepress environment and have used a Panther RIP running on a Mac G4 in Mac OS 9.2.2. It worked fine except for in-RIP separations, which would crash the RIP software if we left the preview window open. We were told that the RIP software was not fully compatible with the OS version we had installed (recommended is System 7.5).

Several months ago, I replaced the G4 with a Blue & White G3 and installed OS 8.6 to see if that would correct the issue. Unfortunately, the problem still existed, and a new problem developed. When printing two jobs in sequence, the first would print fine and then the second would die with a random Postscript error. I have not been able to figure this one out, but now I think it may have to do with our printer server setup.

I use a Powermac G4 running Mac OS 10.4.11 as my main prepress workstation. We have another G4 running Mac OS 10.3.9, serving as a print server for a our Imagesetter as well as a LaserJet. Print Jobs stack fine in the LaserJet queue, but the imagesetter’s queue exhibits the issue above. Bypassing the print server and printing directly to the imagesetter does not solve the problem.

I can get all the print jobs to image correctly if I place the print server’s job que on hold, spool several jobs, and then release them one at a time, when the imagesetter finishes the prior job.

If you could shed some light on the subject and offer some possible solutions, it would be appreciated.