🚀 go-pugleaf

In article <1993Jan21.135812.1@tango.cchs.su.oz.au>, brennan@tango.cchs.su.oz.au (Luke Brennan) writes:
|>Newsgroups: vmsnet.sources.d
|>Path: eratu.rz.uni-konstanz.de!news.belwue.de!news.uni-stuttgart.de!rz.uni-karlsruhe.de!ira.uka.de!yale.edu!nigel.msen.com!emory!swrinde!zaphod.mps.ohio-state.edu!cs.utexas.edu!uunet!munnari.oz.au!metro!tango.cchs.su.oz.au!brennan
|>From: brennan@tango.cchs.su.oz.au (Luke Brennan)
|>Subject: TeX DVIALW drivers?
|>Message-ID: <1993Jan21.135812.1@tango.cchs.su.oz.au>
|>Sender: news@ucc.su.OZ.AU
|>Nntp-Posting-Host: tango.cchs.su.oz.au
|>Organization: Cumberland College of Health Sciences
|>Date: Thu, 21 Jan 1993 13:48:12 GMT
|>Lines: 19
|>
|>	G'day!
|>
|>	One of my TeX afficiandos tells me that the DVIALW driver
|>	is sqwarking at his DVI file (even though TeX didn't barf)
|>	
|>	We're using the TeX 3.1 (PD VMS 3.3/DECUS) with DVIALW driver 2.10b
|>
|>

I have similar problems with DVIALW. There is a workaround: 
  edit the Postscript-file and delete the strange last line!

Eberhard