Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!wuarchive!udel!haven!decuac!bacchus.pa.dec.com!rust.zso.dec.com!shlump.nac.dec.com!dimsum.dec.com!pwong From: pwong@dimsum.dec.com (Paul H. Wong) Newsgroups: comp.lang.postscript Subject: Re: PC to VAX Postscript Help Summary: Printing a PostScript file generated by Windows on a LPS40 Keywords: PostScript Windows LPS40 Message-ID: <17499@shlump.nac.dec.com> Date: 20 Nov 90 23:04:01 GMT Sender: newsdaemon@shlump.nac.dec.com Organization: Digital Equipment Corporation Lines: 30 In article <11476.2747f4a1@ecs.umass.edu>, keene@ecs.umass.edu writes... >I'm using Microsoft Windows v3.0 and Microsoft Word for Windows 1.0 to >create a postcript output file that I can upload to our VAX VMS system and >send to a LPS40. I've installed the postscript driver through windows and >selected the LPS40, and specified the output to be send to a file. But >when I download the file to the VAX and type LPSTEXT file.name all I get is >a printout of the postcript instructions!!! I'm not sure what your LPSTEXT command actually does but my guess is that it sends a TEXT file to the LPS40's ANSI-symbiont (which treats the file as any plain old text file and hence the printout of the PostScript instructions). Since the file you generated is already a PostScript file, you should use the corresponding command (LPSPS maybe?) to send a PostScript file instead. If all things fail, you can just use the print command directly: $ print/queue= file.name You'll have to use the corresponding lpr command on Ultrix. - Paul -------------------------------------------------------------------------- Paul H. Wong | Digital Equipment Corporation 110 Spit Brook Road | EASYnet: DIMSUM::PWONG ZKO2-2/M28 | ARPAnet: pwong@dimsum.dec.com Nashua, NH 03062-2698 | Usenet : ...!decwrl!dimsum.dec.com!pwong U.S.A. | Phone : (603) 881-2575 --------------------------------------------------------------------------