Hi,
since a few days this file is gone (it used to be in the sane group
home-directory on alioth). Does somebody know why?
best
-jochen
Hi,
> I'm trying to see what SANE has to offer for page scanners or sheet
> scanners (the portable, non-bulk feed variety). I selected Boolean
> search, then entered search terms: page scanner, "page scanner" and,
> page and scanner, plus the same combinations for "sheet scanner"
> It seems ther
Hi,
I don't know whether somebody came up with a similar or better solution,
so here's mine:
On new linux installations, where hal is used to manage device access
rights, the old way of granting user saned access rights to scanners by
adding the user to the group scanner or so no longer works. ha
Hi,
thanks for reporting this. It's fixed in CVS now.
regards
-- jochen
Hi,
I guess the bug is that in sane_close the scanner_devList entry
corresponding to the open handle is destroyed, and later in sane_exit
all scanner_devList entries are destroyed again.
I guess in sane_close, the entry should be be destroyed, but only marked
as free or so.
regards
-- jochen
Hi,
Julien BLACHE wrote:
> Gah, that damn crash reporter is getting in the way. Can you try to
> get rid of it?
You have to set the env variable MALLOC_CHECK_ to 0, i.e., in bash
export MALLOC_CHECK_=0
or in tcsh
setenv MALLOC_CHECK_ 0
then you will get a proper backtrace with gdb..
http://w
Hi,
Neil Youngman wrote:
> I have a Mustek 1200CP parallel scanner, which appears to be supported by
Better buy a new scanner :)
> sane-find-scanner -p -vv /dev/usb/lp0 doesn't find any scanners. Is there
> something else I should try, or won't it work with a converter?
lp0 is a printer device
Hi,
that's a common problem of many backends, please file a bug at our
alioth bug tracker. See bug #303681
http://alioth.debian.org/tracker/index.php?func=detail&aid=303681&group_id=30186&atid=410366
for a similar bug.
regards
-- jochen
Hi,
what does ls -l /dev/bus/usb/001/002 show?
Assuming you don't have appropriate access rights to this device, does
changing access rights help?
regards
-- jochen
Hi,
is saned actually executed when you run it from inetd? can you connect
with telnet for example?
regards
-- jochen
Hi,
Wouter van Marle wrote:
> However doing the same as user, doesn't detect the scanner.
looks as if the usb device doesn't have the correct access rights.
I'm not sure where it's mounted on debian, either /proc/bus/usb/aaa/bbb
where aaa and bbb are the values in epson:libusb:aaa:bbb or /dev/usb
Hi,
Circuitsoft Development wrote:
> Why not? Almost every other daemon I've seen does.
that's not the point here. I don't want to have some more or less
unrelated registry entry to enforce a design decision for future versions.
regards
-- jochen
Hi,
Alex Austin wrote:
> I'm working on a SANEd / WIA (Windows Imaging Architecture) bridge
> driver right now. I suppose I could be the contact person, but if
> someone else would prefer, I have no attachment to it. I figured the
> head maintainer of the SANE net backend could, but looking furthe
't think I'm the right person to specify as
> "in-charge" of the protocol.
>
> See http://www.dns-sd.org/ServiceTypes.html
>
> The info I've collected so far:
> Short name of protocol: sane-port
> Long description: SANE Control Port
> Name and Em
Hi,
tj wrote:
> What else if anything do I need to do?
did you check the troubleshooting guide at
http://penguin-breeder.org/sane/mustek_pp/#trouble ?
regards
-- jochen
Hi,
Alessandro Zummo wrote:
> I'd appreciate if everyone who is interested can reply
> with their own commitments for the 2007.. ehm.. sane2 :)
I'm quite surprised to hear there is a sane2 standard - at least one
that we can easily start to implement.
I don't think it's a good idea to start ha
Hi,
Dura-Zell wrote:
> To exclude any hardwarproblems I tested the parallelport with some other
> devices:
you don't happen to have the possibility to try your scanner with the
original drivers?
regards
-- jochen
Hi,
Dura-Zell wrote:
> [sanei_pa4s2] pa4s2_open: device `0x378` opened...
this looks good...
> [sanei_pa4s2] pa4s2_readbyte_nib: reading value 0x77 from '0x378'
and this looks very bad. should be A5 or A8 or similar.
is your parallel port configured in EPP mode (maybe you can configure
that in t
Hi,
the search engine (http://www.sane-project.org/cgi-bin/driver.pl) now
supports search for usb-ids as well.
You can either fill in the IDs in the form (you can also leave out
either the vendor or the product ID), or invoke the script directly:
driver.pl?p=4002
will search for usb devices wit
Henning Meier-Geinitz wrote:
> Should we change the links in sane-hp.man and sane-microtek2 to your
> page?
i just checked those links and they don't work anyway. what about
replacing them with the current ppscsi homepage, and also adding a link
to my page?
kind regards
-- jochen
Hi,
I've updated the ppSCSI driver suite patch for 2.6.13 kernels.
Furthermore, I've added a stand-alone version, i.e. the ppSCSI drivers +
Makefile, so you don't need to patch the kernel anymore but can build
them seperatly.
Both are available from http://penguin-breeder.org/kernel/download/
ki
Hi,
I once started to write a driver for this scanner, which was quite
unstable and only supported greyscale scanning. Basically, it's a
modification of the ccd300 driver.
I'm always thankful if somebody wants to take over a part of the backend
by adding support for a scanner. However, this is qu
Hi,
what's the output of
SANE_DEBUG_MUSTEK_PP=128 scanimage -L
kind regasds
-- jochen
Hi,
saned isn't a stand-alone program, but you have to run it using
(x)inetd. See http://penguin-breeder.org/sane/saned/ or the saned and
sane-net man-pages.
kind regards
-- jochen
Hi,
I've commited a patch to CVS that introduces an option "no_epp" to
mustek_pp.conf. When this option is defined, the EPP protocol is not tried.
This works around a known bug in the parport kernel code of linux that
causes the mustek_pp backend to hang on some systems.
kind regards
-- jochen
Hi,
could you try to set your BIOS settings to something else than EPP? Like
SPP oder standard mode or something?
kind regards
-- jochen
Hi there,
ok, I'm back home again :-)
let's see, can you send me your modprobe.conf?
kind regards
-- jochne
Hi,
it's /etc/modprobe.conf in fedore core 3 :)
kind regards
-- jochen
378h
> DMA Channel: DMA3
>
> But dmesg don't agree, why?
> Is there something else I must do, like reinstall the Kernel or the
> parport0 module, is there a module I have forgotten to install or what ?
>
> Thank's for all help.
>
> Sincerely,
> Philip Moller
Hi,
Philip Moller wrote:
> Hi!
> I read in the installationmanual
> (http://penguin-breeder.org/sane/mustek_pp/) under "Known distribution
> specific issues" that Fedora Core 1 has to remove the symbolic link
> libsane.so.1, is that advice for Fedora Core 3 to ?
no, it only affects fc1
Do you hav
Hi,
could you please send the output of
SANE_DEBUG_SANEI_PA4S2=128 scanimage -L
kind regards
-- jochen
Hi,
Patrick Marquetecken wrote:
> If I run scanimage -L on the client with xinetd enabled i see this error
> on the server.
> Jan 11 21:24:11 [xinetd] START: sane-port pid=10946 from=192.168.123.7
> Jan 11 21:24:11 [xinetd] FAIL: sane-port address from=192.168.123.7
An error message like this me
Hi,
I assume you are configured xinetd to execute saned as user saned (or
similar)
does saned still work, if you execute it like this
# su - saned
$ saned -d128
(i.e. running as user saned)
kind regards
-- jochen
Patrick Marquetecken wrote:
> On Tue, 11 Jan 2005 17:37:55 +0100
>
Hi,
Patrick Marquetecken wrote:
> After each connection attempt there is a /tmp/saned.7876.stderr file.
well, what is in that file?
kind regards
-- jochen
Hi,
have you tried the troubleshooting section at
http://penguin-breeder.org/sane/saned/ ? I'm pretty sure that should
solve your problem
kind regards
-- jochen
Hi Eddy,
what do you think about this patch: http://c0ffee.org/stuff/mustek_pp.diff
Eddy De Greef wrote:
> PS: I think we should do something about this. Users should get a
> warning that the backend isn't functional already during compilation.
kind regards
-- jochen
Hi,
I'm not yet sure what this bug is, but I have the feeling it's a kernel
bug which makes the driver hang. Could you try to update the kernel? As
far as I know there's a new kernel from SuSE available via online update.
kind regards
-- jochen
Hi,
Hauke Zuehl wrote:
> [mustek_pp] sane_init: invalid driver name ``cis1200''
this error message is a bit mis-leading, this probably means the scanner
is not found.
Could you try (as root)
sane-find-scanner -v -v -v -p
kind regards
-- jochen
Hi,
this appears to be a problem with either libieee1284 or the kernel. I'll
try to investigate into this a little further...
kind regards
-- jochen
Hi,
Jose Sanchez wrote:
> I patched the kernel with the patch in the web page. Everything went
> ok. I compiled the kernel, but the modules where not compiled again.
> Do I have to configure something or I am missing something in my
> compilation.
You have to enable ppSCSI and the module for y
Hi,
i have ported the ppscsi driver suite to 2.6 and try to keep it working.
You could submit a request to SuSE to include it in future kernels, if
enough people ask for it, they will probably include it.
The patch is available from my homepage:
http://penguin-breeder.org/kernel/#ppscsi
kind re
Hi,
Eddy De Greef wrote:
> After he compiled everything from source, upgraded his kernel,
> and altered the parport BIOS settings, Neal's problem disappeared.
> It's impossible to say what was the real problem, unfortunately.
>From what I read on parport-devel this is a bug in the SuSE kernel
reg
Hi,
Neal Gamradt wrote:
> [sanei_pa4s2] pa4s2_readbyte_nib: reading value 0xa5
> from 'parport0'
> [...]
> [sanei_pa4s2] pa4s2_readbyte_nib: reading value 0x00
> from 'parport0'
the backend gets the correct value first, but later the scanner only
returns the wrong value 0x00. To me this looks lik
Hi,
I'm still trying to reproduce your problem. Basically, the old (1.0.7)
code was just copied over and patched to support libieee1284. I guess as
soon as I have an 1015/01 scanner, I should be able to fix this.
i'll let you know as soon as I have something
kind regards
-- jochen
Hi,
Julien Langer wrote:
> with mustek_pp 0.13-beta I used:
ehrm, I meant the old one, the 1.0.7 config
kind regards
-- jochen
Hi,
Julien Langer wrote:
> [mustek_pp] ccd_init: found scanner on port ``parport0'' (ASIC id 0xa5, CCD 1)
Hum, my SE 6000 P identifies itself with 0xa8 + CCD 0. Could you please
attach the old (working) mustek_pp.conf (without all the comments)?
kind regards
-- jochen
Hi,
Ok, I'll test this tommorow (this scanner is in the basement and it's
late now...)
kind regards
-- jochen
Julien Langer wrote:
> Hello,
>
> ScanExpress 6000 P doesn't work correctly with mustek_pp backend
> 0.13-beta.
Hi,
Eddy De Greef wrote:
> It looks good.
> I'm all for including it (but I may be a bit prejudiced :-).
It's included since yesterday (just before feature freeze :-)
kind regards
-- jochen
This is a multi-part message in MIME format.
--070004080404080406040306
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Hi,
I just wrote a short patch to sane-find-scanner which detects mustek
parallel port devices. With sanei_pa4s2 it's possible to get a li
Hi
Due to the demand for a port to the 2.6 series of the ppSCSI patch by
several SANE users, I will try to provide an up-to-date patch.
I don't have the possibility to test this patch by myself, since I don't
own such an adapter. This also means that I don't maintain the ppSCSI
patch in respect t
Hi,
The bug you're describing should be fixed in CVS. Please try using CVS
snapshot version.
Why it behaves like a 600 CP scanner, I have no idea.
best regards
-- jochen
Hello,
the problem with "Address already in use" is probably caused by an
incorrect shell script. You cannot give option -d to saned in such a
script but have to execute saned without parameters. On
http://penguin-breeder.org/sane/saned/ an example is given.
The other problem you've stated is tha
Hello,
another idea. May it be, that there are any saned or scanimage running
after the first scan attempt?
regards
-- jochen
Jim George wrote:
> Eddy and Joachen,
>
> when I tried to run saned under gdb I got the following output. Doesn't
> look good does it? Can you tell me what I should do
Hello,
I've thought long about your problem but I still don't get how your
parport can be locked that badly.
What kernel version are you using? What Linux distribution? Could you
please send the output of (after rebooting - that is in a state where
the scan will work?)
SANE_DEBUG_SANEI_PA4S2=6 s
Hi,
Jim George wrote:
> [sanei_pa4s2] sanei_pa4s2_open: could not find scanner
> [sanei_pa4s2] sanei_pa4s2_open: reported ASIC id 0xb5
this looks like the backend couldn't find your scanner (0xa5 would have
been a valid ID for example)
> [sanei_pa4s2] sanei_pa4s2_enable: called for fd 0 with valu
Hi,
if you're only using saned to allow non-root users to scan, you could
aswell solve this with correct access rights to /dev/parport0
regards
-- jochen
Wolfgang Fabics wrote:
> Thanx a lot, Henning... you gave me the right idea. It's a local
> resolver/DNS config problem... gonna look into tha
Hi,
does this also happen when you scan from command line, i.e. using scanimage?
regards
-- jochen
Hi,
sorry for the lately unreliable operation of the mailing list search
engine. I'm experiencing disk space shortage at the moment, I hope I can
fix that within a few days.
best regards
-- jochen
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--enig7E5A96C3DA3448ADC508E109
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Hi,
I've finally ported the CCD part to the new mustek_pp backend... sorry
for the long delay.
I tested it here, works
--=.E(ZvrHD6M:2+ys
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Hi,
yes, it's true, and it just shouldn't work.
regards
-- jochen
[David A Iacobellis]
> I read on another site that ccd scanners were disabled in the sane
> 1.0.10 backend and only the cis scanners wo
--=.Ck,JUCF/u'4.N7
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Hi,
some remarks on the Parallel Port sections:
Interface Types -> Parallel Port Devices:
Jonathan's page is really very outdated for some time now. It's
better (also for the other scanner types
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--enigC23D0D5E5B47D942DBAEFBFB
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Hi,
Julien BLACHE wrote:
> As long as one has the option of using the system's libieee1284, I
> won't object. Otherwise
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--enig5F795099F5F25C456C69E563
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Hi,
I commited the new (and fixed) sanei_pa4s2 to cvs earlier today.
In order to use the mustek_pp backend, you either
This is a multi-part message in MIME format.
--030003090207040009070707
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Hi,
attached is a new version of the sanei pa4s2. Most important changes are
support for libieee1284 and a function sanei_pa4s2_devices()
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--enigC5068C84F9E9AC538F851276
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Hi,
I just commited version 12-alpha of the mustek_pp driver to the SANE
CVS. It's a complete rewrite of the backend bas
Hi,
I moved the mailing list archive and driver search engines to another
box, namely belleile.informatik.uni-freiburg.de. If you're using (as you
should) the alias sane.informatik.uni-freiburg.de, you shouldn't need to
update anything.
The new box features two UltraSPARC 2 (168mhz) CPUs, 512MB r
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The man page sane-mustek_pp contains examples for your scanner. Don't
forget to uncomment the mustek_pp line in your dll.conf too.
regards
- -- jochen
Hans Krueger wrote:
> what should that mustek_pp.conf file should look like for Mustek 600 III
> E
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mertens Bram wrote:
> * Something I haven't mentioned before because I can't see how this
> would affect anything is that the scanner is attached to a "switchbox"
> (a little box that allows more parallel devices to be attached to a
> single paralle
; On Thu, 2002-11-28 at 17:13, Mertens Bram wrote:
>
> >On Thu, 2002-11-28 at 17:00, Jochen Eisinger wrote:
> >
> >>hum, i nearly forgot.. you're using a 600dpi scanner, there's a special
> >>option for this in the config file. use600 (see the man-page)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
Mertens Bram wrote:
> Do I simply add this line to the end of the file?
> The section
> # Use this option for 600 dpi scanners
> # for example ScanExpress 1200 ED Plus
> #option use600
yes, that's it
regards
- -- jochen
- --
...and I doubt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
hum, i nearly forgot.. you're using a 600dpi scanner, there's a special
option for this in the config file. use600 (see the man-page)
do you have that option set?
regards
- -- jochen
Mertens Bram wrote:
> On Tue, 2002-11-26 at
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
Mertens Bram wrote:
> I've tried to scan twice without the acquire preview but using the start
> scan button from the main window and both times xsane crashed due to an
> "Floating point exception"!
>
> Does that shed any light?
not really...
c
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
Mertens Bram wrote:
> [mustek_pp] attach: asic 0xa5, ccd 01
That appears to be a 600dpi scanner, for those only grayscale scanning
is supported? can you scan grayscale pictures?
regards
- -- jochen
- --
...and I doubt complaining to the author
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
does scanimage -L show your scanner? If yes, could you please send me
the output of the following command:
SANE_DEBUG_MUSTEK_PP=128 scanimage -T
regards
- -- jochen
- --
...and I doubt complaining to the author will get you
anything but a free
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
Melanie wrote:
> I have been given a Mustek ScanExpress A3 EP scanner, which turned out
> to be 1505 based (ID 0xA2). I have so far located 3 different Mustek
> backends, only one of which offers the beginnings of support for the
> 1505 chipset.
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--enig9DA3C85722504C1B3A50F6B2
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Hi,
a new search engine which searches by model name, manufacturer &
bus-type is available at:
http://sane.informatik.u
Hi,
[Henning]
> Yet another related topic: It would be great to have some sort of
> database generated from the .desc files. So a user could use the WWW
> to search for his scanner. E.g with search boxes for Manufacturer,
> bus-type and model name. The output would be all we now about the
> model
Hi,
this scanner is supported by the current development version of the
mustek_pp backend, more details (including the backend) are available from
http://penguin-breeder.org/?page=mustek_pp
regards
-- jochen
Rick Seitz wrote:
> Is there a backend for this EPP scanner. I see there is a 12000 P t
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--enig97ABF95867FD8DFC70AE985C
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Hi,
Robert Kleemann wrote:
> Sure, I ran "tcpdump -i any -x -s 1024" and then ran "scanimage -L"
> locally. You can fin
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--enig42C0110941AE2353D253F8C6
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Hi,
could you send a tcpdump of the traffic between scanimage and saned? I
don't have xinetd running, so it's hard to te
Hi,
the debian package does _not_ include the gphoto2 backend by default,
you have to modify the debian/rules file to configure the gphoto2
backend, i.e. include the option --with-gphoto2 in the configure call.
(Il package Debian non include di default il backend di gphoto2,
devi modificare i deb
The following is an OpenPGP/MIME signed message
created by Enigmail/Mozilla, following RFC 2440 and RFC 2015
--enig1572E1EE0932CC393A1AE65B
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Hi,
lp0 etc are line printers (therefor lp) and not scanners. Please d
The following is an OpenPGP/MIME signed message
created by Enigmail/Mozilla, following RFC 2440 and RFC 2015
--enig302F6C67C1E7CA256B0EFE8A
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: 7bit
Hi,
Grzegorz Jaskiewicz wrote:
> 1) how should i configure sane 1.0
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
[Gene Heskett]
> So if you're asking can you print and scan at the same time, the
> answer is yes IF the scanner driver plays nice. Does sane do that?
> I dunno.
I know, it doesn't (yet). That's because the driver is using the
parallel port d
--=.In0vTD?05_+AN5
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Hi,
to which port is your scanner connected? Or are you using a printer
while trying to scan? You could try to unload the parport modules (or at
least make sure they do not lock the port address...)
reg
--=.AGf7y02i'gR/A0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Hi,
[Andrei B.]
> I used the example shown for inetd.conf using tcpd directly, but it
> did not work because tcpd expected to find saned in /usr/sbin, while
> it was installed in /usr/local/sbin.
>
> I'
--=.D36NLyRkPgK6vG
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Hi,
Please use either backend version 1.0.11-alpha (download it from
http://www.penguin-breeder.org/?page=mustek_pp) or apply Eddy's patches
for CIS scanners (http://home.tiscalinet.be/EddyDeGreef/ - the
--=.xTPmA5y/RBN1w+
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Hi,
a completly rewritten version of the mustek_pp backend is available for
testing at:
http://www.penguin-breeder.org/?page=mustek_pp
So far, only CIS scanners are supported - thanks to Eddy De Greef
--u1'7p0?wL_3=.K=.
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Hi,
I added a TODO entry for saned:
- Add support for IP ranges in saned.conf (like 10.0.0.0/8)
should not be difficult to add, however the config file format needs to
changed for IPv6 anway, so I d
--=./KnjxXs?IEh'N,
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Hi,
due to problems with the isp hosting the old sane-net homepage, the page
has moved to
http://www.penguin-breeder.org/?page=sane-net
Please update your bookmarks. The old URL now redirects to the
Hi!
Are you running saned as user root (as it should be for mustek_pp) or as
user saned (as the saned man page describes - but which is only correct
for scsi scanners)?
regards
-- jochen
jerry white wrote:
> Have been trying to connect a user to the scanner through the saned net
> interface a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi!
Sorry, for the long delay, I haven't been online for some days...
Jim George wrote:
| Jochen, and anyone else who wants to chip in here...I hope the following
| makes sense and helps in the resolution of this problem.
You still have not send th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi!
Jim George wrote:
| Something has gone wrong now. When I issue the command scanimage >
| out.pnm, as myself or root on the server, it scans but then stops with
| no error messages at all. The only way I can kill I can return to the
| prompt is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi!
The mustek_pp backend wasn't changed between 1.0.5 and 1.0.6, so this
shouldn't do much. From the output you've send, everything should work.
So again my questions, does scanning work when done locally by root
using scanimage (i.e. without saned/n
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi!
Does this also happen with plain scanimage on your scanner server (as root)?
Could you put somewhere on he internet such a scanned image and the
output of
SANE_DEBUG_MUSTEK_PP=128 scanimage -T
(assuming you're using bash)
regards
- -- jochen
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi!
Jim George wrote:
> # specify the port your scanner is connected to. Possible are 0x378 (lp1)
> # 0x278 (lp2) and 0x3bc (lp0)
> port 0x3bc
Well, that's an old problem with kernel 2.2.x -> 2.4.x... reminds me I
should add this to the config-ex
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi!
Jim George wrote:
> I've just installed sane with the mustek_pp backend.
>
> I had no /dev/scanner entry in my /dev directory therefore, after much
> scrabbling around and guessing, I created a symbolic link from
/dev/lp0 to
> /dev/scan
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi!
Henning Meier-Geinitz wrote:
> The question is: Is it intended behavour that only fully qualified
> domain names are allowed in saned.conf? If yes, we should note this in
> man saned. Otherwise, I think a change in saned.c is necessary.
I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi!
There appears to be a group working on a driver for HP Scanjet 2200c
project. I've added a pointer to scanjet2200c.sourceforge.net to PROJECTS.
regards
- -- jochen
- --
"I'd rather die before using Micro$oft Word"
-- Donald E. Knuth
- -- jochen
mh wrote:
| Jochen Eisinger, Sam, 08 Sep 2001:
|
|>Hi!
|>
|>~From the debug output Michael send me, I assume that the bug isn't in
|>the net backend. The data pipe is closed correctly and the sigpipe
|>occurs on the control pipe. Why this doesn't happen with a dela
1 - 100 of 119 matches
Mail list logo
