<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.18.2">
</HEAD>
<BODY>
On Fri, 2008-07-11 at 18:40 -0400, m. allan noah wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE>
[...]
> - The double-feed options --dfdetect and --dfdiff have been replaced by a
> new one, --df-action,
no- they have not been replaced, they are disabled until you set
df-action to something other than default.
</PRE>
</BLOCKQUOTE>
<PRE>
</PRE>
That would explain it :-)
<PRE>
</PRE>
<BLOCKQUOTE TYPE=CITE>
<PRE>
[...]
> then --overscan is the only option
> which is exposed by the backend for this scanner, but which does not
> actually work. Maybe the option could be hidden when the scanner returns
> (os_x_basic, os_y_basic) = (0, 0), as this scanner does?
yes- i dont have a good way to detect the overscan capability, other
than the existence of the page code that is used to enable it, which
also enables other things. do you get an error when you set overscan?
if not, then the problem might be that your os_x/y_basic need to be
overridden, like the 4120c?
</PRE>
</BLOCKQUOTE>
<PRE>
</PRE>
There is no error. I will try overriding the settings.<BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
<PRE>
> Interestingly, the
> paper guides limit page width to 220 mm, so there is 2-3 mm of unused CCD on
> each side - presumably for overscan, but it appears to be not implemented,
> or maybe deliberately disabled for this scanner :-(
what is the maximum page-width value?
</PRE>
</BLOCKQUOTE>
<BR>
224.846 mm.
<PRE>
</PRE>
<BLOCKQUOTE TYPE=CITE>
<PRE>
[...]
</PRE>
</BLOCKQUOTE>
<BR>
Best regards,<BR>
Jacob Nielsen
</BODY>
</HTML>