Re: [hpoj-devel] ptal-mlcd ECP changes

[Bob P. <bpa...@cs...>]

> Bob Paddock wrote:
> > Second scan at -300 came out ok, but it took about 3 minutes to scan it,
> > it was a black and white page, but it was probably still scanned as color
> > since I did change any thing besides adding the -300.
> >
> > I loaded up the out.jpg image with KView then my machine started going so
> > slow it was useless, the mouse moved in great leaps and lunges.  Had to
> > cycle power.  Don't know if this is in any way related to scanning, for
> > the moment lets assume that it was not.  The scan did look fine.
>
> A 300dpi JPEG image requires lots of RAM to process, because I think
> libjpeg insists on decompressing it into RAM.  A high resolution setting
> like 300dpi is overkill for most situations.

I tried 300dpi as the OCR software I use seems to prefer it.

> > Third scan of b&w page in color with the defaults got me:
> > patlChannelRead returns 0!
> > Broken Pipe.
>
> It would be helpful to know if ptal-mlcd reported any error messages,
> because chances are that something went wrong at that level.

Where do I look for those at?  Didn't think the syslog stuff was implimented 
yet?

> > All pages looked like there where twice as long as they should have been
> > when viewing out.jpg in the viewer.  Last half was a blank gray looking
> > thing, probably scanned the color of the unit it self.
>
> That's a known issue (mentioned briefly in SCAN-HOWTO and in the "Bugs and
> TODO" list on the web) 

Yes I did see that, just wanted to be thorow in my report.

> I added an item on the TODO list to work on this before I release 0.8.
> For now, you could try writing a script that calls ptal-hp in a loop.  I
> neglected to document that ptal-hp has different exit codes depending on
> whether the scan was successful and there are (1) or aren't (0) more pages
> to scan.

Thank you.

> >
> > HPOJ:
> >
> > just those five chars.
>
> That's really bizarre.  I guess CUPS has different methods of configuring
> print queues, 

CUPS seems to be beast all its own.  Its what I'm use to, is there some thing 
better out there?

> fails, you can just invoke something like "lpr filename.ps" from a shell
> prompt (or whatever the CUPS equivalent is to lpr).

lpr-cups.