Xref: utzoo comp.windows.ms:13380 comp.lang.postscript:8893
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!mips!apple!fernwood!uupsi!sunic!fuug!funic!csc.fi!vsarkela
From: vsarkela@csc.fi
Newsgroups: comp.windows.ms,comp.lang.postscript
Subject: Re: MS Windows PS driver weird?
Message-ID: <1991Jun3.111652.1@csc.fi>
Date: 3 Jun 91 11:16:52 GMT
References: <1991May31.164205.28877@sarah.albany.edu>
Sender: usenet@nic.funet.fi
Lines: 27
Nntp-Posting-Host: csc.fi

In article <1991May31.164205.28877@sarah.albany.edu>, rds95@leah.albany.edu 
(Robert Seals) writes:
> Hello,
> Has anybody had difficulty with the PostScript driver that
> comes with Windows 3? We find that the code generally works,
> but leaves the printer in a wacko condition; the next job
> is scaled down in size and backwards...successive jobs get
> smaller and smaller.
> We 'print' to a file then transer to a unix host that uses
> lpr to spool to our ps printers.
> The stupid ^Ds at the beginning and end are tolerable, easy enough
> to get rid of, but this scaling problem really stinks.
> Our printer is a DEC LN03R, but I observe the same thing on
> my RS/6000's display postscript.
> 
> Why is this, how do I fix it?
> 

The  problem is, that postscript printer needs that control-d in order to 
reset after previous job. End-of-line is also important character and 
it is *NOT* newline (used by U*ix), but carriage return (13 decimal,
015 octal).

We solved this problem with filter, which puts a carriage return before
each new line and also after control-d. Hope this helps....

-- vesa sarkela   vsarkela@csc.fi  Finnish Pulp and Paper Research Institute