🚀 go-pugleaf

In article <19309@mimsy.UUCP> chris@mimsy.UUCP (Chris Torek) writes:
>In article <2932@tahoe.unr.edu> mikew@wheeler.wrcr.unr.edu (Mike Whitbeck)
>writes:
>>I got a version of TeX/LaTeX (HaTe ThIs!) going on an Atari ST ....
>>However when I send the dvi file to my friendly SUN 3 at work
>>the printer (iptex, shell script calling an IMAGEN driver,
>>imagen1) program complains about a missing "postamble" and
>>questions if this is REALLY a dvi file then quits.
>
>The first step in examining a questionable dvi file is to run dvitype
>over it.  If dvitype likes it, there may well be a bug in the dvi
>interpreter (in this case, probably an ancient version of imagen1).

I remember a bug in older versions of iptex whose symptoms are similar
to this.  It would not tolerate more than a small number of filler
bytes at the end of the DVI file (16 comes to mind).  If it didn't
find the end of the postpost within a short distance of the end of the
file, it complained that it couldn't find the postamble.  We
discovered this when moving a dvi file made under VMS over to a Unix
machine.  The VMS TeX padded out with the dvi filler byte to the end
of the last block.  This is perfectly legal dvi, but at least one
older version of iptex didn't like it.

		William LeFebvre
		Department of Electrical Engineering and Computer Science
		Northwestern University
		<phil@eecs.nwu.edu>