Hi,
On Fri, Mar 07, 2003 at 02:50:45PM -0500, Dirk Petersen wrote:
I would be happy to do some testing but unfortunately
my coding skills do not go beyond python, C is rather like klingonian
for me. In the latest sane backend sources (Top of the changelog below)
I could not find the header
Hi,
the order does matter. But in that case it seems to be a problem in the
backend.
The recommended sequence (at least for the hp-backend) to specify the
options is the order they appear in xscanimage.
Sincerely
Peter
Franz Bakan schrieb:
Hi,
a user reported that
SCANIMAGE.EXE -d hp
Hi,
try to plug in the USB-cable of the scanner after your system is up. If
you hear a short beep after a few seconds, the system should have
recognized the scanner. If not, have a look at /var/log/messages for
error messages.
Did you unplug the SCSI-connection of the scanner ? This might be
Hi,
On Fri, Mar 07, 2003 at 11:02:26PM -0600, David Wilson wrote:
I hate to admit defeat, but I have not been able to get my USB HP 6200C
scanner to show up when I try the sane-find-scanner program.
cat /proc/bus/usb/devices shows nothing.
Nothing as in the file is empty, nothing as in the
Hi,
Please send the mail to the list, not to me.
On Sat, Mar 08, 2003 at 08:54:05AM -0600, David Wilson wrote:
Think I finally have this problem at least cornered.
I compiled the kernel with:
* Preliminary USB device filesystem
* OHCI support
Ok. Well, at least if you have a OHCI
I've tried it with RedHat 8.0 linux. The sense bytes 16 and 17 really
point to the offending byte (I've tried to set a invalid resolution
an others). There is a 8 byte window header you can't
see in the hexdump above. The offending byte is at position 25 (0x02).
This means 'grayscale
