said:
>
>
>>>> F:\os2sane\find-scanner.exe: found processor "HP C5110A 3638" at device
>>>> b1t2l0
>>>>
>
>
>> device `hp:b1t2l0' is a HP C5110A flatbed scanner
>>
>
> This looks OK.
>
> Try
>
> scanimage -v >tmp.pnm
>
> with the same debug settings.
>
I couldn't get the > operator to work, but I did a work around. Here it is:
[dll] get_option_descriptor(handle=0x32278,option=9)
[dll] start(handle=0x32278)
F:\os2sane\scanimage.exe: sane_start: Invalid argument
[dll] cancel(handle=0x32278)
[dll] close(handle=0x32278)
[dll] exiting
[dll] calling backend `umax's exit function
[dll] calling backend `tamarack's exit function
[dll] calling backend `snapscan's exit function
[dll] calling backend `s9036's exit function
[dll] calling backend `qcam's exit function
[dll] calling backend `pnm's exit function
[dll] calling backend `net's exit function
[dll] calling backend `mustek's exit function
[dll] calling backend `microtek2's exit function
[dll] calling backend `microtek's exit function
[dll] calling backend `hp's exit function
[dll] calling backend `epson's exit function
[dll] calling backend `dmc's exit function
[dll] calling backend `coolscan's exit function
[dll] calling backend `canon's exit function
[dll] calling backend `artec's exit function
[dll] calling backend `apple's exit function
Thanks for your help,
Sandy
Content Type: text/html
Content-Transfer-Encoding: 7bit
Steven Levine wrote:
In <480F8B02.2070703@ucsd.edu>, on 04/23/08
at 12:16 PM, Sandy <sshapiro@ucsd.edu> said:
F:\os2sane\find-scanner.exe: found processor "HP C5110A 3638" at device
b1t2l0
device `hp:b1t2l0' is a HP C5110A flatbed scanner
This looks OK.
Try
scanimage -v >tmp.pnm
with the same debug settings.
I couldn't get the > operator to work, but I did a work around. Here
it is:
[dll] get_option_descriptor(handle=0x32278,option=9)
[dll] start(handle=0x32278)
F:\os2sane\scanimage.exe: sane_start: Invalid argument
[dll] cancel(handle=0x32278)
[dll] close(handle=0x32278)
[dll] exiting
[dll] calling backend `umax's exit function
[dll] calling backend `tamarack's exit function
[dll] calling backend `snapscan's exit function
[dll] calling backend `s9036's exit function
[dll] calling backend `qcam's exit function
[dll] calling backend `pnm's exit function
[dll] calling backend `net's exit function
[dll] calling backend `mustek's exit function
[dll] calling backend `microtek2's exit function
[dll] calling backend `microtek's exit function
[dll] calling backend `hp's exit function
[dll] calling backend `epson's exit function
[dll] calling backend `dmc's exit function
[dll] calling backend `coolscan's exit function
[dll] calling backend `canon's exit function
[dll] calling backend `artec's exit function
[dll] calling backend `apple's exit function
Thanks for your help,
Sandy
Content Type: text/plain
=====================================================
To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-help".
For problems, contact the list owner at
"postmaster@scoug.com".
=====================================================
<< Previous Message <<
>> Next Message >>
Return to [ 23 |
April |
2008 ]
The Southern California OS/2 User Group
P.O. Box 26904
Santa Ana, CA 92799-6904, USA
Copyright 2001 the Southern California OS/2 User Group. ALL RIGHTS
RESERVED.
SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group.
OS/2, Workplace Shell, and IBM are registered trademarks of International
Business Machines Corporation.
All other trademarks remain the property of their respective owners.
