bob@MorningStar.Com (Bob Sutterfield) (08/15/90)
I'm trying to print RFC1129 on a printer attached to a NeXT box, which the workstation faerie dropped nearby the other day. Even though I removed everything after the "%!" in the first line (the stuff erroneously claiming conformance to Adobe formatting conventions), I'm still told Couldn't print file because of malformed PostScript Error: limitcheck; OffendingCommand: printerdevice whereupon the Thalidomide RFC is punted from the queue altogether. Has anyone been successful in printing RFC1129 on a fairly strict PostScript device? Or on a NeXT printer? Any suggestions?
bob@MorningStar.Com (Bob Sutterfield) (08/15/90)
(Sorry to quote the whole thing for comp.lang.postscript, but the answer wasn't crossposted to comp.protocols.time.ntp, where other folks may find it useful.) In article <243@heaven.woodside.ca.us> glenn@heaven.woodside.ca.us (Glenn Reid) writes: In article <BOB.90Aug14163401@volitans.MorningStar.Com> bob@MorningStar.Com (Bob Sutterfield) writes: Couldn't print file because of malformed PostScript Error: limitcheck; OffendingCommand: printerdevice Try adding these hacks to the beginning of the file and see if it does any better: /letter { } def /legal { } def /note { } def The "Error: limitcheck; OffendingCommand: printerdevice" indicates that it is trying to set a paper size that perhaps confuses the NeXT interpreter. That makes sense - I had originally thought I was overrunning a job size page limit or some such, but couldn't find those knobs anywhere in the printer configuration. If the above hacks don't help, take a look at the beginning of the file and see if anything jumps out at you that looks like the setting of a page size. You can probably just remove them, whatever they may be. Device-dependent anyway. I didn't find any. I hope that helps. Yep, that did the trick for both 1128 and 1129. Thanks!