🚀 go-pugleaf

Pscript5.dll bug?

Has anyone seen a bug in Pscript5.dll such that when
running on Windows 2000 SP3 large chunks of text are
not printed, even tho' they are in the .ps file?
This problem occurs only when the host system is running
under heavy load, i.e. several print jobs are being
processed simultaneouly. No text is missing when only
a single print job is being processed.

The producer application is FrameMaker 6.0.

The problem seems to be related to the use of the xshow
PS operator. When Pscript5.dll uses xshow in this form:

3290 1950 M <010203040506070108090A0B09060C01060F0108060905010A0D010E0A1709>[32 72 56 61 33
56 28 32 61 39 61 61 39 55 95 31 56 50 32 61 56 36 33 32 61 33 32 56 61 61 0]xS

(all one line above)

the text referenced between < .... > above is missing. (The
character width data is processed correctly, tho'.)

The text is missing regardless of whether the ps file is
sent to PS 3 printers (Epson and Xerox) or distilled
using Distiller 4.05, 5 or 6.

OTOH when the xshow operator is given a plain text argument
all is OK, viz.

(FDH Access 100)[55 73 72 32 72 50 50 55 50 50 32 50 60 0]xS

i.e. the above works correctly.

The strange thing is that there is no missing text when
the same document is printed to ps when the system is lightly
loaded. And there are similarly no instances of hexadecimal text
references for the xshow operator (i.e. <0102....>) in the .ps
file in this case. Under light load all the text in the .ps
file is produced using plain text arguments to xshow.

As the system load increases Pscript5.dll changes the format
of the PS output to include more and more text in the
(unprintable) <0102....> format. It's as if Pscript5.dll gets
into a confused 'state' when running under heavy load. No error
messages are ever reported by the printing device or by distiller.

Anyone ever encountered this? Any fixes or workarounds?

MTIA for any help, anecdotes or fixes.

Best regards,

Rick