Xref: utzoo comp.sys.ibm.pc:24834 comp.lang.postscript:1635
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!decwrl!amdcad!diablo!phil
From: phil@diablo.amd.com (Phil Ngai)
Newsgroups: comp.sys.ibm.pc,comp.lang.postscript
Subject: Re: DOS programs and PostScript (MS Word)
Message-ID: <24469@amdcad.AMD.COM>
Date: 16 Feb 89 21:44:55 GMT
References: <206@nlgvax.UUCP> <24456@amdcad.AMD.COM> <20446@agate.BERKELEY.EDU>
Sender: news@amdcad.AMD.COM
Reply-To: phil@diablo.AMD.COM (Phil Ngai)
Organization: Advanced Micro Devices, Inc. Sunnyvale CA
Lines: 27

In article <20446@agate.BERKELEY.EDU> izumi@violet.berkeley.edu (Izumi Ohzawa) writes:
|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.

I'm using Word 4.0 with PC-NFS and it does not work reliably for me.
It may be that PC Network acts differently from PC-NFS. Also, I tend
to print by outputting to a file and then using PC-NFS "net print".
Word does not seem to put on the .ini file when it prints to a file.
Perhaps 4.0 does when printing to a printer but not a file? 

--
Phil Ngai, phil@diablo.amd.com		{uunet,decwrl,ucbvax}!amdcad!phil
"In Texas, they run the red light after it turns red."
"In Taiwan, they run the red light before it turns green."