I just save to pdf and get the advantage of adobe's excellent print engine combined with Pagestream's ease-of- use.

Henry Lazarus sent from my Treo

-----Original Message-----

From: Henry G Belot <hbelot@ix.netcom.com>
Subj: Re: [PageStreamWindowsBeta] Re: Workaround and fixes to PageStreaam
Date: Sat Dec 30, 2006 11:06 am
Size: 14K
To: PageStreamWindowsBeta@yahoogroups.com

> ...As I have previously noted, the printing function in version 4.1.5.8,
> which I have been very happily and successfully using for at least 2
> years, has no trouble printing any document that I design. When I
> purchase an "updated" or "new" version I think that I have a right to
> expect it to surpass the previous version. In setting up the printer
> in version 5.xx.xx Pro, it is obvious that the programing has been
> changed. My question is: to what end? The old addage "if it ain't
> broke, don't fix it!" comes to mind.

To the best of my recollection /every/ version of PageStream for Windows
has had printing problems, including 4.1.5.8. It's just that some
combinations of computers and printers respond differently than others.
Some people have zero problems, others may not be able to print at all.
Deron is not a big player with a multitude of printers and computers to
test his work on or the power to press another company to conform their
products to so-called Windows standards. If Deron or Dan can't reproduce
the problem with the equipment at their disposal, fixes are largely
educated guesswork.

As I remember the effort to overhaul the print engine in recent versions
of PageStream was because previous drivers were riddled with workarounds
that all but guaranteed that no PageStream print engine would ever work
properly for everyone. The print engine in PageStream 5 is an
improvement compared to versions between 4.1.5.8 and the present build.
I'm sure it will continue to improve, but slowly. Unlike a larger
company, Deron can't delegate things like this to other engineers. He's
under pressure on a lot of fronts for improvements, fixes, and to
fulfill commitments for new platform-specific versions. He has to clear
some of these. Sometimes we get lucky. A fix for one version becomes a
benefit on all platforms. If, as seems to be the case here, the issue
has less to do with the print engine than with the size of the files
being sent to the engine, there could be a fix sooner rather than later.

HB