[softwarelist] Re: OPro 2.76

In message <4e908b78b6chris@xxxxxxxxxxxxxxxxxxxxx>
          Chris Johnson <chris@xxxxxxxxxxxxxxxxxxxxx> wrote:

> 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)
> --------------------------------------------------------------------

Many thanks - the observation that the error occurs on your machine as 
well and with Gimp-Print was very useful because it allowed me to 
finally see and confirm the error myself and I found out a few 
interesting things (see my other posting).

> 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.

That is a red herring. The problem is simply that after a print has 
failed in the way you describe above, the NEXT print causes the Type5. 
If you tried printing to PrintPDF before printing to any other 
destination you should notice that it works fine. After all, from the 
application's point of view PrintPDF is just the same as PostScript2, 
which, as you observed, works fine, too.

> 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

... all of these are not relevant. When there is an abort during 
printing that prevents the application from closing down the print 
operation correctly, this cascade of errors is perfectly normal 
(though applications should normally try to clean up properly even 
when a fatal abort happens - David, I guess, in your signal handler 
you could at least call PDriver_AbortJob to shut down the printing 
system).

> 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.

Not odd at all, this is to be expected but it is bound to fail because 
the printing had not completed so the PostScript file is truncated.

Martin
-- 
---------------------------------------------------------------------
Martin Wuerthner          MW Software          martin@xxxxxxxxxxxxxxx
---------------------------------------------------------------------

Other related posts: