Path: utzoo!attcan!uunet!munnari.oz.au!uhccux!ames!uakari.primate.wisc.edu!zaphod.mps.ohio-state.edu!swrinde!ucsd!ucbvax!decwrl!adobe!shore From: shore@adobe.com (Andrew Shore) Newsgroups: comp.lang.postscript Subject: Re: Do I need memory upgrade? Message-ID: <1608@adobe.UUCP> Date: 12 Jan 90 01:03:37 GMT References: <136800005@uxa.cso.uiuc.edu> Sender: news@adobe.COM Reply-To: shore@adobe.COM (Andrew Shore) Organization: Adobe Systems Incorporated, Mountain View Lines: 39 In article <136800005@uxa.cso.uiuc.edu> gsg0384@uxa.cso.uiuc.edu writes: >The laserwriter NTX (basic configuaration 2 Meg) of our group is connected to >a Apollo DN4500 unix machine through serial connector. >It does not allow postscrip graphics printing when the file is bigger than >1 Meg for a page. > >So, >do we need memory upgrade? I can't believe no one else has suggested this as a possible cause/solution yet.... I don't know id the DN4500 uses a BSD-based line printer spooler but... The 4.X BSD Unix line printer spooler (lpd,lpr and friends) has a printcap-based limitation on the size of spooled files. If NO "mx#" field exists in the printcap entry for the printer, then the default spool file size limitation is (according to the SunOS 4.0.3 man pages) 1000 BUFSIZE blocks. Often this is 1 Megabyte. Some versions of lpd will reject files over that size, others may just truncate. If you put an entry of the form "mx#0" in the printcap entry in question, all size limits are removed (of course, there is the amount of free space in the file system of the spool directory...). If the printer is remote, suitable "mx" entries must exists in both local and spooling-host printcap files. Other Unix-based spooling systems may impose similar restrictions. Does your problem happen will ALL postscript files over 1MB (independent of # of pages) or just on files which contain a single page over 1MB? Let me know if this was the problem. --Andy Shore shore@adobe.com -- Andy Shore Adobe Systems Incorporated shore@adobe.com {decwrl,sun,apple}!adobe!shore