[comp.sys.apple] Postscript w/AWGS

j_p@pro-lep.cts.com (Jason Perez) (11/16/89)

  I'm using AWGS 1.0v2 and after setting up a Postscript drive I type
open-apple F and then printed the file.  It seems to create one file per page
of text, and only does two pages at a time before it says "Data cannont be
printed".  What's the problem here>

        With Multiscribe GS I don't have this problem.  When I print to a file
it prints the entire document to one Postscript file, and then doesn't try to
print it afterwards to the LaserWriter.  I'm using GS/OS 5.0 btw, w/ 1.25 Mb
and a 40Mb Vulcan.
_____

UUCP: crash!pro-lep!j_p
ARPA: crash!pro-lep!j_p@nosc.mil
INET: j_p@pro-lep.cts.com

mattd@Apple.COM (Matt Deatherage) (11/17/89)

In article <0.net.apple@pro-lep> j_p@pro-lep.cts.com (Jason Perez) writes:
>
>  I'm using AWGS 1.0v2 and after setting up a Postscript drive I type
>open-apple F and then printed the file.  It seems to create one file per page
>of text, and only does two pages at a time before it says "Data cannont be
>printed".  What's the problem here>
>
>        With Multiscribe GS I don't have this problem.  When I print to a file
>it prints the entire document to one Postscript file, and then doesn't try to
>print it afterwards to the LaserWriter.  I'm using GS/OS 5.0 btw, w/ 1.25 Mb
>and a 40Mb Vulcan.
>_____
>
>UUCP: crash!pro-lep!j_p
>ARPA: crash!pro-lep!j_p@nosc.mil
>INET: j_p@pro-lep.cts.com

The Print Manager uses the calls PrOpenDoc and PrCloseDoc as a signal that a
print job is beginning and ending.  Some applications call PrOpenDoc and
PrCloseDoc on each *page*, rather than further distinguishing pages within
a job with PrOpenPage and PrClosePage, to improve memory performance when
printing with an ImageWriter.

The LaserWriter driver can't know this and happily creates a different file for
every print job it gets.  I've not seen the "data can't be printed" error so
I can't really tell you who to blame for that.

-- 
-----------------------------------------------------------------------------
Matt Deatherage, Apple Computer, Inc. | "The opinions expressed in this tome
Send PERSONAL mail ONLY (please) to:  | should not be construed to imply that
Amer. Online: Matt DTS                | Apple Computer, Inc., or any of its
ThisNet: mattd@apple.com              | subsidiaries, in whole or in part,
ThatNet: (stuff)!ames!apple!mattd     | have any opinion on any subject."
Other mail by request only, please.   | "So there."
-----------------------------------------------------------------------------

wombat@claris.com (Scott Lindsey) (11/17/89)

In article <0.net.apple@pro-lep> j_p@pro-lep.cts.com (Jason Perez) writes:

>   I'm using AWGS 1.0v2 and after setting up a Postscript drive I type
> open-apple F and then printed the file.  It seems to create one file per page
> of text, and only does two pages at a time before it says "Data cannont be
> printed".  What's the problem here>

AWGS originally printed one page at a time to avoid memory overhead when
printing to the ImageWriter (where the entire document has to be spooled in
memory).  I'm not sure why you get two pages dumped to file instead of just
one, but the problem is a matter of the LaserWriter checking for Fan-F at
the beginning of each document.  If you hold down that key sequence the
entire time you're printing, you'll get one postscript file per page (along
with trying to do a Find after you're done).

AWGS 1.1 checks the printer type and prints multiple pages at a time if
printing to a LaserWriter (but still does 1 page at a time if you're printing
to an ImageWriter).


Scott Lindsey     |"Cold and misty morning. I heard a warning borne in the air
Claris Corp.      |    About an age of power when no one had an hour to spare"
ames!claris!wombat| DISCLAIMER: These are not the opinions of Claris, Apple,
wombat@claris.com |    StyleWare, the author, or anyone else living or Dead.