[softwarelist] Re: Michael Harding - printing keeps crashing.

  • From: Ross McGuinness <farmstay@xxxxxxxxxxxxxxxx>
  • To: davidpilling@xxxxxxxxxxxxx
  • Date: Fri, 04 Mar 2011 08:32:27 +0800

In message <8aa65dae51.martin@xxxxxxxxxxxxxxxxxxx>
          Martin Wuerthner <public@xxxxxxxxxxxxxxx> wrote:

snip

Iyonix v5.16(16 Jan 2010), Printers v1.72 (5 Nov 04) using PS2 and PS3 
to print to file and produce PDFs ready for our printing company which 
prints out on a digital printer. In all cases we use jpegs. Some from 
our cameras, some from scanned images.
> Even 409k is small by today's standards. There should never be a
> problem printing a sprite of that size. OvationPro has been used to
> produce books with many large illustrations.

The OPro print memory is set to 25Mb and the books we produce range up 
to 500+ A4 pages with some books having images on most pages. Some 
pages have four or five images on them.

>>> Faced with a 100 page document with 1000 graphics in. I would set
>>> off with a printer driver set to print to file, and then apply the
>>> binary chop - print pages 1-50 if they crash then print pages 1-25,
>>> if they don't print pages 50 to 100. Keep dividing by two until you
>>> find what is causing the crash.

When printing to PDF I observe as each page is rendered and if it 
takes 'too' long deduce that there is a large image on that page. By 
going back and reducing the image to less than 1Mb the problem is 
usually resolved. When there are multiple images the reduction applied 
through ChangeFSI is greater ie images inserted at 300-600Kb.

We also are reduced to printing up to the problem page. After the 
problem page(s) to the end of the chapter and then I recombine the 
sets of pages for the chapter on the Mac.

>> I could occasionally deduce which page had a problem by observing the
>> page count of the print screen, noticing where it crashed. But I never
>> really knew why it was crashing, particularly when sometimes it
>> crashed and sometimes it printed out the same documents.

Taking the same course I could locate the 'problem' page and would 
then look at the images. OvPro-Picture-Proxy to check image size. Then 
go back to directory storing the image and 'rectify' - either rotate 
the image in ChangeFSI or reduce the image size to less than a Mb.

> Sounds very much like a problem outside of OvationPro. The most likely
> candidate is a problem with TurboDrivers, in particular in conjunction
> with "high address dynamic areas" problems.

Have long since ceased using Turbo drivers. Yesterday when this issue 
arose on the list I simply opened an OPro page, created a frame, 
dropped an image from my digital camera (jpeg around 2 Mb) then 
created a new page and did the same thing. Printed via PS2 (to PDF) 
and also PS3. Then I rotated one image in OPro. When I went to print 
to PDF using PS2 it immediately came back with a 'not enough memory' 
message. In PS3 it started to process, came up with the same memory 
message and then appeared to render. At the end there was a 'PDF' 
created of around 500Kb but upon opening it was a blank page.

My work around over the years has been to try and ensure all images 
are less than 1Mb, with multiple images on a page reduce the image 
size (in Kb) to meet the size of the frame, when printing watch the 
rendering to locate trouble pages, seek image info and rectify using 
ChangeFSI, and above all never rotate an image in OPro - always do so 
with ChangeFSI. Printing in small sets of pages rather than whole 
chapters is the safest way to go.

> Martin


-- 
Ross and Bev McGuinness, Cinnamon Coloureds Farmstay
1800 South Coast Hwy DENMARK  WA 6333 Tel:+61 8 9848 1781
Fax:+61 8 9848 1231 Web: http://www.denmarkwa.com.au/cc/
To unsubscribe or subscribe goto: //www.freelists.org/list/davidpilling

Other related posts:

  1. Home
  2. davidpilling
  3. Archive
  4. 03-2011