| OK, I've traced this a little further now. 0
By watching the sender process this message (size and content
of the NBS files that it produces) I'm now sure that this is where the
fault lies (i.e, the sender).
I can reproduce this at will.
This has worrying implications for TEAMLINKS V2/ALL-IN-1 V3.0
implementations as I'm sure that this combination of products will
result in a lot of very 'pretty' PostScript documents being produced.
Call now logged with UK TSC.
Any thoughts/comments ?
Chris
|
| Hi,
Just to add to this (as I have the call!!), I have done some testing
here and found the following;
The actual file which reproduces the problem is on wayout::pcgfow.ps.
The original file had a record format of 766 byte records, but once you
import the document into ALL-IN-1 v3.0-1, send it to user@a1@node, and
FA and SVC to send the document to VMS, the file has been truncated so
it only has a record format of length 255 byte records.
The actual postscript file has an image in it, and when you try to
print the document after it has been routed through ALL-IN-1, you find
that the document stops printing at the page which has the image on it.
It looks as though the problem is introduced in v3.0, as this file can
go through the same route in v2.4, and is imported out correctly with a
record format of 766 byte records.
The difference between 2.4 and 3.0 is that in v2.4 the document was
sent as a foreign attachment with .fgn extension, whereas in v3.0 it is
treated as a ps attachment with .ps attachment.
Any ideas?
Thanks,
Julie
|