Xref: utzoo comp.protocols.nfs:31 comp.sys.ibm.pc:20968
Path: utzoo!attcan!uunet!smsdpg!seg
From: seg@smsdpg.uu.net (Scott Garfinkle)
Newsgroups: comp.protocols.nfs,comp.sys.ibm.pc
Subject: Re: PC-NFS net print bug?
Message-ID: <104@smsdpg.uu.net>
Date: 6 Nov 88 22:46:19 GMT
References: <23464@amdcad.AMD.COM>
Reply-To: seg@smsdpg.UUCP (Scott Garfinkle)
Organization: SMS Data Products Group, Inc.
Lines: 26

In article <23464@amdcad.AMD.COM> phil@diablo.amd.com () writes:
>
>I have an Easy Data AT clone running at 12.5 MHz with a WD 8003
>Ethernet interface connected to a thick wire network and a Logitech
>Mouse. The clone is running PC-DOS 3.3, PC-NFS 3.0, and Microsoft Word
>3.0. When I use "net print", it goes to a Sun-4 which hands it off to
>a microvax running 4.3 BSD which drives an Apple LaserWriter [....]

We just fixed this bug here about a week ago.  What you need to do is
fix the POSTSCRP.PRD (and POSTSCRL.PRD) files.  Microsoft is not terminating
the postscript job with a ^D ('\004') as is required.  This will generally
screw things up pretty good.  Use the "makeprd" program to convert your
printer driver(s) to text, then in the last table in the file (I forget the
byte offset), change the string "PSe" to "PSe^D" (where the caret and the 'D'
are two separate characters).  Re-convert the text back to PRD format and
you're done.

		Scott E. Garfinkle
		SMS Data Products Group
		seg@smsdpg.uucp

		<Standard Disclaimer, I suppose>
-- 
	yours, Scott E. Garfinkle
	SMS Data Products Group, Inc.
	uunet!smsdpg!seg