Newsgroups: comp.lang.postscript
Path: utzoo!utgpu!tj
From: tj@gpu.utcs.utoronto.ca (Terry Jones)
Subject: Re: Microsoft Word (PC Version) and Postscript ...
Message-ID: <1990Jun9.033939.7161@gpu.utcs.utoronto.ca>
Keywords: Microsoft Word
Organization: UTCS Public Access
References: <8615@uswat.UUCP>
Distribution: usa
Date: Sat, 9 Jun 90 03:39:39 GMT

While not totally what you wanted I have resolved one bad experience
with Word5.0 and PostScript over the network.

We use CAP/transcript on a sun and spool from PC's to the sun through
ethernet via a gatorbox.

CAP is pretty slick and captures "procsets" on Unix (of which LaserPrep
is one such procset) You can then massage them to make them nice and
any subsequent jobs needing that procset get the Unix stored version.

Here is where Word5.0 croaked. It started a procset in its ini code
but never ended it so CAP swallowed THE WHOLE DOCUMENT and replaced it
with the Unix procset. Document gone! Vapour. I must admit I didn't call
Microsoft about this since I thought the chances of explaining such
a complex scenario to a front line support person and getting it acted
upon was slim... but I thought someone here might be interested.

Also on the same line we experienced Xon/Xoff problems with word5 and a
call into Microsoft indicates there is a problem and that going into
print options and TYPING in the driver name again will correct the situation
(not selecting it with F1, typing it!!) OR there is a 5.0b that fixes the 
problem and they will send you the disks. This only affects serial connected
printers. This is an annoying problem on a laserwriter since a few pages
usually come out before things croak.

2 cents worth for today!
tj