One thing I forgot to mention. For ages I've been using a snapscan.conf
file (probably dating back to 1.0.3). Tonight I took a look at the
current snapscan.conf, and notice that the syntax had been changed. So I
gave it a go.
Didn't work.
My guess is that in the new format:
scsi AGFA * Scanner
t
no whizz at SCSI.
Cheers
Paul
--
Paul Floyd http://paulf.free.fr (for what it's worth)
MailTo:pa...@free.fr
What happens if you have lead in your pants as well as lead in your
pencil?
--74D3CAC94EF4BBCDDE2A17F9
Content-Type: text/plain; c
phore_close(), snapscani_semaphore_wait(),
> snapscani_semaphore_signal. Until an OS/2 implementation is provided the
> OS/2
> version of the functions may be left empty (maybe issuing a warning
> message).
> However, the OS/2 implementation should be simple.
Are there any developers that have OS/2 and a USB scanner? For that matter, are
there any backends other than snapscan that use semaphores with USB?
A bientot
Paul
--
Paul Floyd http://paulf.free.fr for those with time to waste
What's the point? The sharp thing on the end.
"snapscan-usb.c"
#endif
where the 'stubs' version doesn't include the offending header file, but it does
have empty function bodies to keep the linker happy.
After these changes, it all worked (for me). So far, the "smoothest" build I've
experienced with SAN
reware OS/2 application I use - this applies both to tiff and
pnm. I'll look into this when I have some more time.
A bientot
Paul
--
Paul Floyd http://paulf.free.fr (for what it's worth)
MailTo:pa...@free.fr
If more is better, are double standards better than single ones?
Hi
I've updated my SANE related web pages, specifically
http:/paulf.free.fr/software,html
bit also
http://paulf.free.fr/sane-os2.html
and
http://paulf.free.fr/sane-os2-gui.html
Regards
Paul
--
Paul Floyd http://paulf.free.fr (for what it