🚀 go-pugleaf

In article <POLLACK.90Aug22104029@dendrite.cis.ohio-state.edu> pollack@cis.ohio-state.edu writes:
>I could not get the distillery to run under NeWS, and so tried to run
>it under Ultrascript PC. It seemed to work(!) but the output scrolled by
>on the screen and did not land in the USLOAD.LOG file, as advertised
>by the manual.

No, usload.log is only for program crashes.  The manual, which is
designed for the Postscript-naive, may not be clear on this.

There is no automatic mechanism for logging the output of USPC's
screen.  However, there are several alternatives available to you:

	[1] I think that the distillery is designed to operate on an
	    input and output file.  Since USPC can only open a very
	    limited number of files at once for PS use, you may have
	    to run this by creating a file that you "print" (not from
	    executive, which uses an extra file descriptor of its own).

	    So maybe "still.ps" can actually do the output to where you
	    want it.

	[2] You can probably redefine the PS operators that output to
	    standard output to output to a file.  Something like:

		/myfile (filename)(w) file def
		/realprint print load def
		/print { dup myfile exch writestring realprint } bind def
		/writestring { exch pop myfile exch writestring } bind def


	[3] If all else fails (it shouldn't, but maybe you like to hack
	    PC more than PS), the USPRINT program uses simple BIOS
	    calls to put data on the screen.  You can trap the BIOS
	    INT 10 and grab the data.  Probably, you should just trap
	    the "scroll region" call and grab the data out of video memory.
- Geof
-- 
geof@aurora.com / aurora!geof@decwrl.dec.com / geof%aurora.com@decwrl.dec.com