obrennan@CC3.CC.UMR.EDU (obrennan) (12/05/90)
When I try to print a Postscript file using the normal prf command , if I DON"T use the -trans flag it prints it as an ascii file and simply prints the code for the PS file. I also thought that the 10.x (mine is 10.3) was supposed to recognize the type of file and print it as such but at least in my case it doesn't. The Postscript file, as per Adobe Postscript standard, MUST start with a %! as the first 2 characters in the file (usually %!PS-Adobe), otherwise the Apollo print filters will convert the text to postscript so that it comes out as Postscript of your Postscript text (i.e. sends your Postscript file as Postscript text). Using the -trans option keeps it from applying filters. On your ascii file printouts , can you , if you like, have the users name, file name, date and page # print on each page. I know about the -head options. Haven't tried any of these, but I would think you can and that the head options would work. We also have a few old 9.7 nodes. Just wondering if their printcap files could be linked to our 10.x nodes and use lpr from them. Probably would work using the rm and rp options of printcap, but I don't know because we haven't experienced LPD communications between SR9.7 and SR10.x. Hope this helps... Gerry O'Brennan Programmer/Analyst II Computing Services University of Missouri - Rolla ------------------------------ obrennan@apollo.cc.umr.edu c0022@umrvmb.umr.edu ------------------------------
edwill@venus.lerc.nasa.gov (Glenn L. Williams) (12/11/90)
In article <9012051449.AA01247@cc2.cc.umr.edu>, obrennan@CC3.CC.UMR.EDU (obrennan) writes... > > When I try to print a Postscript file using the normal prf > command , if I DON"T use the -trans flag it prints it as an > ascii file and simply prints the code for the PS file. I also > thought that the 10.x (mine is 10.3) was supposed to recognize > the type of file and print it as such but at least in my case > it doesn't. > >The Postscript file, as per Adobe Postscript standard, MUST start with a %! as the >first 2 characters in the file (usually %!PS-Adobe), otherwise the Apollo >print filters will convert the text to postscript so that it comes out as >Postscript of your Postscript text (i.e. sends your Postscript file as >Postscript text). Using the -trans option keeps it from applying filters. > We are running a DN3550 with Mentor Graphics 7.1 and 10.1 O.S. Mentor's Postscript output contains two funnies that must be deleted before our Postscript printers will work. First, the very beginning and very end of the files contain non-printing characters that *may* confuse the printer. Second, there is a line somewhere down in the file with syntax 'letter 0 setjobtimeout'. This line must be commented out or removed, or the output will *not* work on the printer. I should mention that we use 'offline' mode so we can send the output to various printers on our lab network.