Xref: utzoo comp.lang.postscript:5784 comp.protocols.time.ntp:34 Path: utzoo!attcan!uunet!tut.cis.ohio-state.edu!mstar!mstar.morningstar.com!bob From: bob@MorningStar.Com (Bob Sutterfield) Newsgroups: comp.lang.postscript,comp.protocols.time.ntp Subject: Re: printing RFC1129 Message-ID: Date: 15 Aug 90 14:10:34 GMT References: <243@heaven.woodside.ca.us> Sender: usenet@MorningStar.COM (USENET Administrator) Reply-To: bob@MorningStar.Com (Bob Sutterfield) Organization: Morning Star Technologies Lines: 34 In-Reply-To: glenn@heaven.woodside.ca.us's message of 15 Aug 90 02:22:22 GMT (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@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!