🚀 go-pugleaf

FM8: Placed PDFs are sporadically changed to an image (WIN DIB) in PostScript

Symptoms:
Placed PDF has same appearance in PostScript as in FM application.
Transparent PDF appears on a white background and not page background.
Colour changed.
Appearance is generally rasterized

Background:
We use FrameMaker for paginating directories.
Output in PostScript (+100.000 pages/year).

Why WIN DIB?
Within the affected PostScript we found these lines where actually an EPS has to be:

%%BeginDocument: Pscript_Win_PassThrough
gsave
803 3492 translate 0.0 rotate -803 -3492 translate
%%EndDocument
Pscript_WinNT_Compat dup /suspend get exec
Pscript_WinNT_Incr dup /resume get exec
Pscript_WinNT_Incr begin
%%BeginResource: file Pscript_Win_Dib_L2 5.0 0
�
/DeviceRGB dup setcolorspace /colspABC exch def
: 1039 165 24 0 1040 165 283 3410 F F 3 [ 0 0 0 ] F
X
doNimage
JcC<$JcC<$JcC<$JcC<$JcC<$JcC<$JcC<$JcC<$JcC<$JcC<$JcC<$JcC<$eGk+"JcC<$JcC<$ � lots of binary � s3BO%cJSZIhuD!Zs3BO%cJSZIhu<~> Z
; 30000 VM?
Pscript_WinNT_Compat begin /$x mysetup def end
Pscript_WinNT_Incr dup /suspend get exec
Pscript_WinNT_Compat dup /initialize get exec
%%BeginDocument: Pscript_Win_PassThrough
grestore
;
%%EndDocument

Since we use FM8:
With FM6 that kind of error never occurred.
We switched from FM6 to FM8 in December 2008.
In the last 10.000 pages (FM8) we found 12 cases.

Unfortunately we can�t reproduce these errors.
In some way it reminds us of the �PDF text drop-out� error.
At that time we found �%%BeginResource: file Pscript_T3Hdr 5.0 0� as an indicator.
Now whenever an error occurs we found this line:
%%BeginResource: file Pscript_Win_Dib_L2 5.0 0

System: Win XP SP3

Any ideas?
Thanks
Norbert