Hi,
Erik P. Olsen wrote:
> Hi René,
>
> Have you had a chance to take a look on this problem?
I'm a bit busy here. I just looked into it and it looks ok ... :-(
Can you confirm this trend:
- the scanner does sometimes not react as programmed by the
backend when used quickly after power-
Hi Ren=C3=A9,
Have you had a chance to take a look on this problem?
--=20
Regards,
Erik P. Olsen
On Sun, 2004-09-05 at 17:56, Erik P. Olsen wrote:
> Hi again,
>=20
> On Tue, 2004-08-31 at 00:17, Ren=C3=A9 Rebe wrote:
> > Hi,
> >=20
> > Erik P. Olsen wrote:
> >=20
> > > OK, I'll do this additiona
--=-YeiqcXNpUXADIrGWge4F
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Hi again,
On Tue, 2004-08-31 at 00:17, Ren=C3=A9 Rebe wrote:
> Hi,
>=20
> Erik P. Olsen wrote:
>=20
> > OK, I'll do this additional test, but I fear wait_4_light() will wait
> > forever. A
Hi,
Erik P. Olsen wrote:
> OK, I'll do this additional test, but I fear wait_4_light() will wait
> forever. As I see it the scanner performs correctly after reboot, then
It should not. It is executed before _every_ scan. So it works at least
after the initial warmup after powering the scanner a
On Mon, 2004-08-30 at 23:22, Ren=C3=A9 Rebe wrote:
> Hi,
>=20
> sorry for the delay - at least this week I'm =C3=BCber-busy again ...
>=20
> > OK, log attached with SANE_DEBUG_AVISION=3D7. Used xsane to produce t=
he
> > problem. The scenario was as follows:
> >=20
> > 1. Reboot
> > 2. Correct scan
Hi,
sorry for the delay - at least this week I'm über-busy again ...
> OK, log attached with SANE_DEBUG_AVISION=7. Used xsane to produce the
> problem. The scenario was as follows:
>
> 1. Reboot
> 2. Correct scan
> 3. Wait half an hour
> 4. Incorrect scan, stopped half way through with this hor
On Sat, 2004-08-28 at 14:50, Erik P. Olsen wrote:
> On Thu, 2004-08-26 at 19:33, René Rebe wrote:
> > Hi,
> >
> > Erik P. Olsen wrote:
> >
> > > I don't think this is true. I am running the latest bleeding edge
> > > backend from
> > > http://svn.rocklinux-consulting.de/sane-avision/trunk/backen
--=-z8do0T8i2SGPL5X1rg34
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
On Thu, 2004-08-26 at 19:33, Ren=C3=A9 Rebe wrote:
> Hi,
>=20
> Erik P. Olsen wrote:
>=20
> > I don't think this is true. I am running the latest bleeding edge
> > backend from
> > http://s
On Thu, 2004-08-26 at 19:33, Ren=C3=A9 Rebe wrote:
> Hi,
>=20
> Erik P. Olsen wrote:
>=20
> > I don't think this is true. I am running the latest bleeding edge
> > backend from
> > http://svn.rocklinux-consulting.de/sane-avision/trunk/backend/
> > with my HP 7400c and I first thought that it had be
Hi,
Erik P. Olsen wrote:
> I don't think this is true. I am running the latest bleeding edge
> backend from
> http://svn.rocklinux-consulting.de/sane-avision/trunk/backend/
> with my HP 7400c and I first thought that it had been corrected. But it
> turned out to be true only after a reboot and su
On Tue, 2004-08-24 at 12:35, Ren=C3=A9 Rebe wrote:
[snip]
>=20
> > 8/15/04 21:37 Powersave on
> > Suspect that avision driver is not handling this state correctly.
>=20
> Correct - your 1.0.14 release version does not handle the lamp power-of=
f=20
> very well. This is fixed in CVS for some time al
Hi Thomas,
Thomas Frayne wrote:
> I tried to send this to sane-devel, but it never seemed to have arrived.
> Perhaps it was because of the attachment.
>
> I have an HP 7450C scanner that works well under Windows XP. I have
> been trying, off and on, for about eighteen months to get it running
12 matches
Mail list logo
