Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!cs.utexas.edu!oakhill!hunter From: hunter@oakhill.UUCP (Hunter Scales) Newsgroups: comp.sys.mac Subject: Re: Dumping Postscript to Disk rather than sending to printer? Message-ID: <2187@cerberus.oakhill.UUCP> Date: 7 Jul 89 19:28:20 GMT References: <3539@ogccse.ogc.edu> <2290@istop.ist.CO.UK> Reply-To: hunter@cerberus.UUCP (Hunter Scales) Organization: Motorola Inc., Austin Tx. Lines: 34 In article sarrel@dinghy.cis.ohio-state.edu (Marc Sarrel) writes: ... >the details, though, I've never used it. Or, if you have a UNIX >system you can use a program called macps (avail from >sumex.stanford.edu) that will send your mac generated ps file to a >postscript printer hooked up to UNIX. Get macps, install it, and try >to use it before you ask me any questions... :-) >-=- Ok, I did this. I created a file with my test text in it. I printed it with cmd-F to get the prolog-less postscript file. I also dumped the file with the prolog. I printed a blank document (all this MS Word) with the cmd-K option to get the laserprep file. I downloaded both to my sun 3/60. Then I ran the prepfix program to munge the laserprep file, installed in the correct directory along with the macps.config file. When I dump the file with the prolog to the LaserWriter IINT, it churns and blinks the green light for about 3 minutes and... prints nothing. When I tried to display it with the PS display program that I got from the net, it puts up a blank page and then aborts with this message: "undefined in operator statusdict" Then I tried the same thing with the file created by the macps program from the prolog-less (cmd-F) version of the test file. Same result on both the printer and PS. Any ideas what I'm doing wrong? -- Motorola Semiconductor Inc. Hunter Scales Austin, Texas {harvard,utah-cs,gatech}!cs.utexas.edu!oakhill!hunter #include