Xref: utzoo comp.sys.ibm.pc:24792 comp.lang.postscript:1627
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!agate!violet.berkeley.edu!izumi
From: izumi@violet.berkeley.edu (Izumi Ohzawa)
Newsgroups: comp.sys.ibm.pc,comp.lang.postscript
Subject: Re: DOS programs and PostScript (MS Word)
Message-ID: <20446@agate.BERKELEY.EDU>
Date: 16 Feb 89 02:20:03 GMT
References: <206@nlgvax.UUCP> <24456@amdcad.AMD.COM>
Sender: usenet@agate.BERKELEY.EDU
Organization: University of California, Berkeley
Lines: 27

In article <24456@amdcad.AMD.COM> phil@diablo.AMD.COM (Phil Ngai) writes:
>In article <206@nlgvax.UUCP> geertj@nlgvax.UUCP (Geert Jan de Groot) writes:
>|WordPerfect, Lotus 123, ORCAD, ChiWrite, but they all gave more or
>
>I have used ORCAD with PC-NFS running a Laserwriter and it seems to
>print fine for me. (did you know you can make the LW run at 38.4K?)
>
>Microsloth Word, on the other hand, is nothing but trouble.

There indeed was a real problem with MS WORD version 3.xx.

However, we have no trouble sending Word Version 4.0 output
via PC Network server to Apple LaserWriter.  We had to make a
little patch to POSTSCRx.INI by commenting out the line which says:

serverdict begin 0 exitserver

This way, Word jobs will not store anything permanently in LW.
And subsequent other jobs will have the full VM of LW.
This works because WORD V4.0 sends POSTSCRx.INI file each time it
prints something.

Word V3.xx apparently tried to save a little time by sending the
equivalent .INI file only once the first time.

Izumi Ohzawa
izumi@violet.berkeley.edu