Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!samsung!noose.ecn.purdue.edu!mentor.cc.purdue.edu!tmp
From: tmp@mentor.cc.purdue.edu (Tom Putnam)
Newsgroups: comp.sys.next
Subject: Re: NEXT/Postscript Conversion
Keywords: postscript, transfer, conversion
Message-ID: <11274@mentor.cc.purdue.edu>
Date: 4 Jun 90 19:44:45 GMT
References: <Jun.4.14.00.09.1990.26582@pilot.njin.net>
Reply-To: tmp@mentor.cc.purdue.edu (Tom Putnam)
Organization: Purdue University
Lines: 38

In article <Jun.4.14.00.09.1990.26582@pilot.njin.net> sinowitz@pilot.njin.net 
(Jonah Sinowitz) writes:
>    I am attempting to transfer an MS-WORD,
>postscript file, using FTP to the NEXT. When
>trying to print the file, the result was:
>error, postscript errors.
>
>Any ideas ???

You need to include a postscript initialization file on the front.
Word sends a bunch of macro definitions in front of the file that
you "print."  With Word 5.0, the file is named "postscrp.ini."  
You have to tweak the macros a bit to remove the stuff that checks 
for pre-loaded macros.  

Here are the changes I made to postscrp.ini (Word 5.0):

	8,15d7
	< %%BeginExitServer: 0
	<  userdict /msinifile known 
	<  {msinifile (POSTSCRP) eq {stop} if} if
	<  serverdict begin 0 exitserver
	<  userdict /msorigstate known {msorigstate restore} if
	<  save /msorigstate exch def
	<  /msinifile (POSTSCRP) def
	< %%EndExitServer
	186c178
	< /PSe {restore end currentfile closefile} bind def
	---
	> /PSe {restore end} bind def
	323d314
	< ^D 

-- 
Tom Putnam                               Assistant Director
Internet: tmp@mentor.cc.Purdue.EDU       Purdue University Computing Center
  BITNET: TMP@PURCCVM                    Mathematical Sciences Bldg.
   Phone: (317) 494-1787                 West Lafayette, IN 47907