Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!chinacat!woody
From: woody@chinacat.Unicom.COM (Woody Baker @ Eagle Signal)
Newsgroups: comp.lang.postscript
Subject: Re: Is HP PostScript known to hang mysteriously?
Summary: bug fixes
Message-ID: <1736@chinacat.Unicom.COM>
Date: 7 Dec 90 05:50:40 GMT
References: <1019@quiddity.queensu.CA> <1734@chinacat.Unicom.COM> <1990Dec6.134809.213@panix.uucp>
Organization: a guest of Unicom Systems Development, Austin
Lines: 49

In article <1990Dec6.134809.213@panix.uucp>, schuster@panix.uucp (Michael Schuster) writes:
> In article <1734@chinacat.Unicom.COM> woody@chinacat.Unicom.COM (Woody Baker @ Eagle Signal) writes:
> >
> Actually, to my knowledge he has documented two. One is specific to the
> IID/IIID, and involves the fact that -copypage- is not side-sensitive on
> a duplexing printer. This slows it down considerably.

On a single page printer, you can image a page, do a copypage, and then
go back and erase a portion of the page, change the data and do another
copypage etc.  This makes for very fast generation of repetitive things
like flyers or newsletters that are mailed to diffrent individuals.
Unfortunatly, the duplex implementation does (currently) not work in
an analogous manner.  If you print a double sided newsletter, say, and
then want to change some data on one of the pages, you have to re-image
the entire document.  What should happen, is that you should be able to
make either the front or back side the currently active side, so that
you could select side 1, change data just like you can on a single
sided page, and then using copypage, kick another copy of the page
out.  As more and more duplexing printers (I know of on that is
currently in the works) come out, unless this is changed, they will
be crippled, and virtually useless.



> 
> The other one =I= discovered while running a Lancaster demo file of different
> screen parameters. A certain combination of -arc- and -setscreen- in
> HP is aware of both bugs. As of this writing they have not given the
> slightest indication that they intend to fix either of them.

Actually, if it works the way it does for most other Adobe OEM'S,
Adobe requires a $100,000.00 up front payment for a new rev level.
If an OEM finds a problem that requires a rev level (Adobe won't allow
a simple rom patch), then they have to determine if it is worth
$100,000.00 to get it fixed.  Generaly, they wind up accumulating the
problems for as long as possible, then get a revision to fix a bunch
all at once.

This info comes from a reliable source within an Adobe OEM.

Cheers
Woody
> 
> 
> -- 
> *%*%*%*%*%*%*%*%*%*%*%*%*%*%*%*%*%*%*%*%*%*%*%*%*%*%*%*%*%*%*%*%*
> l\  /l '     _    Mike Schuster          ...!cmcl2!panix!schuster
> l \/ l l l/ (_    NY Public Access       CIS:70346,1745
> l    l l l\ (_    New York, NY USA       MCI Mail,GEnie:MSCHUSTER