Path: utzoo!utgpu!attcan!uunet!yale!husc6!husc4!kovar
From: kovar@husc4.HARVARD.EDU
Newsgroups: comp.lang.postscript
Subject: Trying to get Microsoft Word's POSTSCRP.INI to work ...
Message-ID: <543@husc6.harvard.edu>
Date: 3 Nov 88 18:54:01 GMT
References: <17188@shemp.CS.UCLA.EDU>
Sender: news@husc6.harvard.edu
Reply-To: kovar@husc4.harvard.edu (David Kovar)
Organization: Graduate School of Design, Harvard University
Lines: 39


  We're running Microsoft Word in a DOS window on a Sun386i. A printed
document gets a file called POSTSCRP.INI added to the front of it
and it is then passed on to lpr which passes it to an Apple LaserWriter
via some CAP utilities.

  When I first tried to get this to work, the document would never
appear on the laserwriter. The following line appeared to be
responsible:

	userdict /msdict known { stop } if

And then the initialization when on to define /msdict in such a
way that it appears to stay resident. So, the next time you tried to
print a paper, it would find /msdict and the job would abort. At
least that is how I see it.

So, I commented out the check for /msdict and everything worked.
'cept I get an infinite number of copies of whatever document is
being printed.

So, finally, a few questions. 1) Has anyone encountered and solved this
problem before? 2) Is there anyway to make it just not define /msdict
if itis already defined? (I tried making it skip over the definition
of /msdict et al if /msdict was known but I was getting stackoverflow
errors.) 3) Any ideas, off hand, why I would be getting multiple
copies of the paper?

I realize that these questions might be dificult to answer without
the actual PostScript but I don't think I'm allowed to distribute
MicroSoft's initialization routines. 

Thanks very much for any help you might be able to provide ...

-David Kovar

P.S. There is no easy way to just load the initialization stuff
into the printer each time it reboots and not send it with each job.
At least, I've not come up with any yet ...