On Thursday 29 September 2005 19:19, Henning Meier-Geinitz wrote:
> No firewall/packet filter involved? From your first log it really
> looks like something blocks the data port.
>
Thanks! I removed the firewall on that machine and remote scanning via saned
now works perfectly.
Thanks Henning
C
On Wednesday 28 September 2005 09:49, Stephan wrote:
> However under remote scanning saned still locks up after what sounds like
> "a) motor initialization and b)turning the lamp on".
>
I've found some previous reports of saned having timing issues.
http://lists.alioth.debian.org/pipermail/sane-d
hello
On Wednesday 28 September 2005 22:23, Gerhard Jaeger wrote:
> hmmm, I thought my last mail was quite clear!
> I don't think it's necessary to snoop the USB traffic - it's necessary to
> find out the correct clock values...
Armed with Gerard's suggestion, I have been playing around with the
On Wednesday 28 September 2005 22:23, Gerhard Jaeger wrote:
> hmmm, I thought my last mail was quite clear!
> I don't think it's necessary to snoop the USB traffic - it's necessary to
> find out the correct clock values...
>
Thanks Gerhard
I'm assuming you're referring to this email:
http://list
On Wednesday 28 September 2005 19:25, Luke Kendall wrote:
> I read the thread "CanoScan LiDE 25" that finished on Mon Jul 18 06:24:08
> UTC 2005.
>
> I've just bought one of these and found I couldn't get it to work under
> SuSE 9.2 (though I saw a review of MandrakeMove that seemed to indicate
> i
