Henning Meier-Geinitz wrote:
> saned -d128
>
> This will print more debug output directly to stderr. It will be
> terminated after each connection has finished, however, so it's only
> useful for debugging.
Ok, after having set up saned correctly, also the debugging output looks
sane ...
Thank
Henning Meier-Geinitz wrote:
>
>>From Windows, run telnet on port 6566 of the Linux system. If it
> ansers, press return twice. This just was saned. If you got
> "connection refused" check security settings, firewall etc. Also check
> syslof for messages from saned.
At least this gave me a clue
Henning Meier-Geinitz wrote:
>
>>From Windows, run telnet on port 6566 of the Linux system. If it
> ansers, press return twice. This just was saned. If you got
> "connection refused" check security settings, firewall etc. Also check
> syslof for messages from saned.
Thanks, Henning,
telnet 192.1
Hi,
On Wed, Oct 05, 2005 at 07:03:52PM +0200, Klaus-Peter Schrage wrote:
> ... is it possible?
I never tried but if this combination works like a normal TCP/IP
network I don't see why it shouldn't work.
> On the windows guest, I installed SaneTwain as well as xsane-win32.
> But neither xsane nor
... is it possible?
My setup:
- VMware Workstation 4.5.2 build-8848
- Host system: Fedora Core 4 with kernel 2.6.13-1.1526_FC4
- Guest system: Windows XP with SP2
- Scanner: AGFA Snapscan 1212U_2, running nicely with sane backend
version 1.0.15
I got saned running on the linux host, following th
