OS/2, eCS & ArcaOS - Technical > Hardware

USB Scanners and ArcaOS

<< < (12/15) > >>

Dariusz Piatkowski:
So what is the strategy / configuration options available to utilize the RPM SANE release in a TAME installation?

I haven't actually tried it yet but it seems like removing the previous SANE install from the TAME directory and literally having TAME issue the normal calls it normally would, which in this case would all come from the \usr\bin directory, should suffice?

It goes w/o saying that the appropriate changes in the various SANE SET...= options need to be made as well.

Martin,
My experience does not directly apply to your problem, but having previously used my HP ScanJet 6390 through the SCSI interface I'm looking to simplify and convert to USB hook up. So far the CLI attempts have worked and I am getting a good scan. Once I can test the TAME re-config I will provide a fuller report-out, although I think for the most part everyone else here has covered that pretty well.

Wim Brul:

--- Quote from: Dariusz Piatkowski on January 10, 2021, 05:15:43 am ---So what is the strategy / configuration options available to utilize the RPM SANE release in a TAME installation?

I haven't actually tried it yet but it seems like removing the previous SANE install from the TAME directory and literally having TAME issue the normal calls it normally would, which in this case would all come from the \usr\bin directory, should suffice?

It goes w/o saying that the appropriate changes in the various SANE SET...= options need to be made as well.

--- End quote ---

I guess that scanimage.exe (size 25.154) in \usr\bin works by dynamically loading scanner specific backends.
It seems to me that the "Sane from Netlabs RPM - sane-backends - 1.0.28-2" does not contain these.

Lars:
Exactly. You need to install an additional RPM that is not listed as a prerequisite.
You need to install "sane-backends-drivers-scanners".
That will drop a bunch of DLLs into /usr/lib/sane, one DLL per conf file.
And if a scanner is a USB scanner, these DLLs will use usb100.dll which in turn uses USBCALLS.DLL to do their job.

Wim Brul:

--- Quote from: Lars on January 10, 2021, 12:25:35 pm ---Exactly. You need to install an additional RPM that is not listed as a prerequisite.
You need to install "sane-backends-drivers-scanners".
That will drop a bunch of DLLs into /usr/lib/sane, one DLL per conf file.
And if a scanner is a USB scanner, these DLLs will use usb100.dll which in turn uses USBCALLS.DLL to do their job.

--- End quote ---
So now I have installed "sane-drivers-scanners" and I have deleted scanimage.exe (size 4.817.128) from h:\tame.

Now scanning with the CanoScan LiDE 210 using Tame/2 on my ArcaOS system works with the latest drivers.

Thank you, Lars!

Dariusz Piatkowski:

--- Quote from: Wim Brul on January 10, 2021, 11:20:44 am ---I guess that scanimage.exe (size 25.154) in \usr\bin works by dynamically loading scanner specific backends.
It seems to me that the "Sane from Netlabs RPM - sane-backends - 1.0.28-2" does not contain these.

--- End quote ---

Yup, that's right.

I took a look at the SANE RPMs that are currently out there last night, here is what I installed:

1) sane-backends.pentium4                         1.0.28-2.oc00
This is the core of the SANE package, but limitted to mostly the EXEs themselves.

2) sane-backends-daemon.pentium4                  1.0.28-2.oc00
This is the network daemon in case you want to serve up your locally attached scanner over the network.

3) sane-backends-doc.noarch                       1.0.28-2.oc00
Documentation for SANE...although scanimage appears to be corrupted. At least here despite the fact that it can be found here => \usr\share\man\man\scanimage.1.gz, executing 'man scanimage' just produces a blank one-liner :

--- Code: ---[G:\usr]man scanimage
 Manual page scanimage(1) line ?/? (END) (press h for help or q to quit)

--- End code ---

4) sane-backends-drivers-scanners.pentium4        1.0.28-2.oc00
This is the other part that actually has the scanner hardware backend details. I am guessing this was split up b/c that approach would allow you to update these independently of the EXEs themselves.

5) sane-backends-libs.pentium4                    1.0.28-2.oc00
This is the matching drivers DLL package.

So per Wim's previous recommendation I went back to the older post. Having completely purged SANE from the current TAME install location, indeed the RPM release of scanimage.exe appears to be the only thing that must be physically moved back to the TAME directory. Having updated all of the other settings that allows TAME to use the RPM SANE release.

Here is what I have in my CONFIG.SYS:


--- Code: ---REM **********************
REM ***  SANE - START  ***
REM **********************
REM Line below is specific to TAME install
rem SET SANE_CONFIG_DIR=G:\apps\graphics\tools\tame\conf

REM Line below is specific to RPM install
SET SANE_CONFIG_DIR=g:\etc\sane.d
SET SANE_DEFAULT_DEVICE=libusb:001:001

SET SANE_DEBUG_HPAIO=4
SET SANE_DEBUG_HP=4
SET SANE_DEBUG_SANEI_USB=4
SET SANE_DEBUG_DLL=4

REM Options below allow to keep the connection OPEN all the time
REM    as opposed to an OPEN/CLOSE operation
REM SET SANE_HP_KEEPOPEN_SCSI=1
REM SET SANE_HP_KEEPOPEN_USB=1
REM SET SANE_HP_KEEPOPEN_DEVICE=1
REM **********************
REM ***   SANE - END   ***
REM **********************

--- End code ---

That has allowed me to successfully scan from CLI as well as through TAME using the USB hookup.

I suppose the only other thing that I'm unclear about is the SET SANE_DEFAULT_DEVICE=libusb:001:001 statement. This does work here, however TAME still references the 'hp' backend and indeed the CLI it executes still uses that as well, namely:


--- Code: ---Start:    10 Jan 2021  00:43:52
Job:      Scan to file
Command1: START /MIN /C SCANIMAGE.EXE -d hp --resolution 1200 --format=tiff -l 0 -t 0 -x 215 -y 296 > G:\tmp\scanner\Image025.tif
File:     G:\tmp\scanner\Image025.tif (17764970 bytes)
End:      10 Jan 2021  00:46:36

--- End code ---

For consistency's sake it's worth adjusting this in TAME, which is what I will test out next.

Ahh, one other thing, the USB DLLs.

Martin,
Here is what I have:

1) libusb1.pentium4                          1.0.21-2.oc00
2) libusb1-legacy-0.pentium4                 1.0.16-2.oc00.L
3) libusbcalls.i686                          12.07-1.oc00



Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version