Path: utzoo!attcan!uunet!cs.utexas.edu!tut.cis.ohio-state.edu!ucbvax!agate!shelby!polya!Neon.Stanford.EDU!rokicki From: rokicki@Neon.Stanford.EDU (Tomas G. Rokicki) Newsgroups: comp.text Subject: dvips (again) Message-ID: <11910@polya.Stanford.EDU> Date: 23 Sep 89 09:09:36 GMT Sender: USENET News System Lines: 44 To those who don't read comp.text for comp.TeX.dvi.drivers.for.PostScript, please hit `N' now . . . Now, to hit a few birds with one post. The LPS040 (at least, the ones I've played with) have 1M of virtual memory. The Apple LaserWriter has 180K. The QMS PS810 has 400K. The NeXT machine (bless its soul) has as much as you care; 1M seems to work. It's `dvips', not dvi2ps. Many print spoolers attempt to interpret %% comments---and fail miserably in their job. You might try the -N option to disable these comments and see if things work then. (This can also be specified in config.ps as a line starting with `N'). The VM specified in config.ps (on a line starting with `m') is the amount of VM free in the printer during normal operation. If your system `initializes' the printer with some prolog files, this VM may not be as high as you might like. Thus, you might try reducing this parameter. Setting it to less than 100K, though, will probably not work very well; I recommend at least 140K for most documents. (The Apple LaserWriter has 180K, and that's one of the most memory-constrained printers around.) To monitor free VM during a job, there are some lines in tex.lpro which can be uncommented (don't forget the one in the definition of /eop.) Still don't know how much VM in the machine? Send a file something like the following: %! PostScript, fool /Times-Roman findfont 30 scalefont setfont 144 432 moveto vmstatus 40 string cvs show ( ) show 40 string cvs show ( ) show 40 string cvs show ( ) show showpage The first is total available VM, the second is VM in use, the third is the save level. You should use the first less the second. Yes, 4.0 does have some minor problems; 4.1 should be available soon. -tom