[softwarelist] OPro 2.76

In article <4e902b6b6dray@xxxxxxxxxxxxxx>,
   Ray Favre <ray@xxxxxxxxxxxxxx> wrote:
> In article <ci1be9AcfCdFFwGE@xxxxxxxxxxxxxxxxxxx>, David Pilling
> <flist@xxxxxxxxxxxxxxxxxxx> wrote:

> <snip>

> > >I have now tried that - although it's not an operational sequence
> > >that I have ever used before (always learning). And it *does*
> > >retain the 100% scale. Thanks, I'll remember that.

> > The scale is 100% because the frame is exactly the right size
> > (which we worked out was due to it being embedded). What is
> > interesting is if this way of replacing the picture fixes the
> > printing problem.

> I didn't try printing it when initially trying the above, so I've
> just tried it again and the same old printing problem occurs - yet
> replacing the pic 'my way' does cure it (albeit with the unwanted
> reduction to 70%).

> I hope that offers you some clues ....

I have now given this a go. Printing to my Lexmark b&w laser printer
using the level 2 postscript driver resulted in a normal print
operation without any problem.


Changing the destination to my Epson C84 inkjet (printing via
GimpPrint) immediately produces the error message

--------------------------------------------------------------------
05 Dec 15:21:38 000 0000098A: Error from Ovation Pro: Overflow while
transforming point (print cancelled)
--------------------------------------------------------------------

Changing the destination to PrintPDF caused mayhem. The print
appeared to proceed for a while then we had:

05 Dec 15:27:08 000 00000000: Error from Ovation Pro: OvationPro has
suffered an internal error type=5.

Canceling this gave a cascade of error messages from each task in turn

05 Dec 15:27:16 000 000000DC: Error from WimpBar 2: Printer drivers
cannot handle VDU 4 characters (print cancelled) at 350
05 Dec 15:27:25 002 000005C7: Error from Organizer: Printer drivers
cannot handle VDU 4 characters (print cancelled) (2060).
05 Dec 15:27:28 000 000005C7: Error from Pluto: Printer drivers
cannot handle VDU 4 characters (print cancelled)
05 Dec 15:27:28 000 00800E00: Error from (unknown): Internal error,
trap while in trap handler: Internal error: abort on data transfer at
&FC030AF0, pc = 000746A0: registers at 0006ED24

This last error caused a total freeze of the Iyonix, requiring two
hardware resets to bring the machine back up again.

The odd thing was that when the reboot was finished (Printers is run
automatically during boot) PrintPDF immediately tried to 'print'
(i.e. save a disc file) of what was still in its input buffer. This
errored part way through, but a pdf file was saved to disc. Opening
this file showed p. 64 had been printed completely and correctly, but
p 65 was missing from the original two page print job. 

I do have the error status report from GhostScript (used by
PrintPDF), but I doubt it adds much.

Chris...

-- 
Chris Johnson

Other related posts: