home *** CD-ROM | disk | FTP | other *** search
- Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
- Path: sparky!uunet!paladin.american.edu!auvm!!UNIGOE"
- Errors-To: rmeyer@ufobi2.uni-forst.gwdg.de
- X-ListName: WORD-PC unmoderated list <WORD-PC@ufobi1.uni-forst.gwdg.de>
- Date: Thu, 21 Jan 1993 08:48:50 MEZ
- From: "Reinhold Meyer, Forstliche Biometrie UNIGOE"
- <rmeyer@ufobi2.uni-forst.gwdg.de>
- Reply-To: WORD-PC@ufobi1.uni-forst.gwdg.de
- Newsgroups: bit.mailserv.word-pc
- CC: rmeyer@ufobi2.uni-forst.gwdg.de
- Message-ID: <00966EF1.552BB5A0.16682@ufobi2.uni-forst.gwdg.de>
- Subject: RE: PostScript driver for MS WORD 4.0 ( fwd )
- Lines: 37
-
- Date: Wed, 20 Jan 1993 08:53:53 -0800
- From: "Jim Goes" <goes@chimera.sph.umn.edu>
- Subject: Re:
-
- > Hello,
- >
-
- > is there any postscript driver for MS Word version 4.0
- > that DOES work?
-
- >
-
- > I have three different versions but none of them sends the
- > fxxxing ini file. Printing to a file results in a 4 line
- > file without the postscript header.
-
- >
-
- > Thanx
- > Andreas
- >
-
- > PS: The destination printer is a Microtek Truelaser.
-
- I used to have this problem back in my 4.0 days in sending output to
- a DEC LN03 laser. My solution, though it was a kludge, was to create
- a macro to save the word document as a postscript file, load it,
- include the ini file at the beginning, and print it. Seems like a
- lot of hassle but it worked, and once the macro was programmed it was
- easy. --
- ***************************************************************
- Jim Goes + InterNet: goes@chimera.sph.umn.edu
- Health Management & Policy + (NeXTmail welcome!)
- School of Public Health + Phone: (612) 624-3118
- University of Minnesota + FAX: (612) 624-3972
- ***************************************************************
- When I hear "family values," I reach for my revolver.
-