this working.
Hope the above helps and I have again included the sane debug output below.
--
Best regards,
Craig
http://slashboot.org/
Support OpenBSD
http://www.openbsd.org/orders.html
# export SANE_DEBUG_PLUSTEK=19 ; scanimage -L
[sanei_debug] Setting debug level of plustek to 19.
[plustek
Gerhard Jaeger wrote:
On Sunday 18 June 2006 17:40, Craig wrote:
Hi.
I've been trying without success for a while now, to get this USB
scanner working on OpenBSD 3.9 and previously 3.8, using
sane-backends-1.0.17 and previously 1.0.16
sane-find-scanner reports:
found USB scanner (vendor
Oliver, thanks for taking a look.
For those kinds souls that would be willing to take a look, the USB
snoop log is stashed up on my web site. You can grab it from here
http://www.gizmo-a-gogo.org/sane/usbsnoop.zip
Thanks,
Craig
Oliver Schwartz wrote:
Hi,
I've taken a look at the USB trace
to collect more debugging information.
This is an Ubuntu Dapper installation with kernel 2.6.15.
Sane version 1.0.17
Thanks in advance for any help you can give me,
Craig
[epson] sane_init: sane-backends 1.0.17
[sanei_debug] Setting debug level of sanei_usb to 128.
[sanei_usb] sanei_usb_init
to help out on this one? I'm a programmer, although I
have almost zero experience with Linux C programming or anything USB
related. I see the iScan driver stuff, but I'd really prefer to use
Sane if I can.
Thanks,
Craig
Henning Meier-Geinitz wrote:
Hi,
On 2006-05-06 21:25, Craig Setera
in place of the ScanMaker 3 I have. The new scanner
is using the same SCSI ID (6).
Regards,
Craig.
--
Craig Dewick. Send email to cdew...@sunshack.org
Point your web client at www.sunshack.org or www.sunshack.net to access my
archive of Sun technical information and links to other
On Mon, 8 Apr 2002, Karsten Festag wrote:
Hi Craig,
do you have an entry like
/dev/scsi/scanner/c6t6d0
in the microtek.conf file?
Yes. I modified microtek.conf and dll.conf in /usr/local/etc/sane.d. The
first file looks like this:
# Uncomment following line to disable real calibration
On Tue, 9 Apr 2002, Karsten Festag wrote:
Hi Craig,
The 'scsi * * scanner' line is for autodetecting every scanner on the
scsi subsystem. It is not neccessary if you specify the device file and
I don't know if the autodetection works on Solaris.
Hope that helps, otherwise please follow
Hello,
Reading the Microtek backend web page at http://www.mir.com/mtek; I
noticed a way to get debug info displayed. So I did this and re-ran xsane:
262 craig@lios # setenv SANE_DEBUG_MICROTEK 128
263 craig@lios # xsane microtek:/dev/scsi/scanner/c6t6d0
[sanei_debug] Setting debug level
and correctly reports what it is, so what could be causing
'xsane' to be unable to access it?
Regards,
Craig.
--
Craig Dewick. Send email to cdew...@sunshack.org
Point your web client at www.sunshack.org or www.sunshack.net to access my
archive of Sun technical information and links
actually valid in a makefile? What's wrong with it? I'm guessing the
comma might be spurious, but I could be wrong.
Regards,
Craig.
--
Craig Dewick. Send email to cdew...@sunshack.org
Point your web client at www.sunshack.org or www.sunshack.net to access my
archive of Sun technical
11 matches
Mail list logo
