Tame/2 and the "Size of image is 0 bytes." error

[Al Savage]

I use this OS/2 box to run a large-format flatbed scanner, and I only
use it occasionally. Thus, it's probably been around eight months since
I last used TAME/2.

This morning, it does not work. When Tame/2 is asked to scan, the
scanner performs the scan and the resulting image file is OK.

However, the TAME progress box displays the 0 bytes message, even as the
scanner is 20 seconds from finishing the scan.

Some progressive screenshots of that progress box:
Loading Image...

While the scan is progressing, there _is_ a 0-byte file in the target
directory, produced by scanimage (I assume). At scan completion,
scanimage then writes the data to that file, and PMView shows that the
scan is correct.

Turning on TAME logging, I see this or similar in the log:

Start: 27 Jun 2014 16:08:03
Job: Scan to file
Command1: START /MIN /C SCANIMAGE.EXE -d mustek -l 3 -t 4 -x 39 -y 47
--format=tiff > F:\temp\Image003.tif

Error: Size of image is 0 bytes. Check Sane installation or
increase delay time in Settings.
Warning: Job canceled by user!
End: 27 Jun 2014 16:08:14

At the commandline, when I copy/paste from the log above:

[d:\tame]scanimage -V
scanimage (sane-backends) 1.0.23; backend version 1.0.23

[d:\tame]START /MIN /C SCANIMAGE.EXE -d mustek -l 3 -t 4 -x 39 -y 47
--format=tiff > F:\temp\Image003.tif

It scans OK as well.

I've got the scanner delay set for 3 seconds, as I have for about a
decade with this hardware. I'd changed it to the max (nine seconds) and
the symptom persists. I've worked with this for a couple of hours and
I'm out of ideas on what to look at next. It doesn't have the feel of a
sane misconfiguration, as I do actually get scans from what I tell TAME
to do.

[A.D. Fundum]

Post by Al Savage
the TAME progress box displays the 0 bytes message, even
as the scanner is 20 seconds from finishing the scan.
While the scan is progressing, there _is_ a 0-byte file in the
target directory
I've got the scanner delay set for 3 seconds

But does the message appear after 3 seconds? Is the environment (BIOS,
drivers, device settings, ...) unchanged? Can you hack a configuration
file and change the maximum delay from 3 to 127 (hex: 7F), even if the
UI wouldn't support such a setting?


--

[Pete]

Post by Al Savage
I use this OS/2 box to run a large-format flatbed scanner, and I only
use it occasionally. Thus, it's probably been around eight months since
I last used TAME/2.
This morning, it does not work. When Tame/2 is asked to scan, the
scanner performs the scan and the resulting image file is OK.
However, the TAME progress box displays the 0 bytes message, even as the
scanner is 20 seconds from finishing the scan.
http://asavage.dyndns.org/ftp/hosting/TAME/TAME_1.0.5_01.png
While the scan is progressing, there _is_ a 0-byte file in the target
directory, produced by scanimage (I assume). At scan completion,
scanimage then writes the data to that file, and PMView shows that the
scan is correct.
Start: 27 Jun 2014 16:08:03
Job: Scan to file
Command1: START /MIN /C SCANIMAGE.EXE -d mustek -l 3 -t 4 -x 39 -y 47
--format=tiff > F:\temp\Image003.tif
Error: Size of image is 0 bytes. Check Sane installation or
increase delay time in Settings.
Warning: Job canceled by user!
End: 27 Jun 2014 16:08:14
[d:\tame]scanimage -V
scanimage (sane-backends) 1.0.23; backend version 1.0.23
[d:\tame]START /MIN /C SCANIMAGE.EXE -d mustek -l 3 -t 4 -x 39 -y 47
--format=tiff > F:\temp\Image003.tif
It scans OK as well.
I've got the scanner delay set for 3 seconds, as I have for about a
decade with this hardware. I'd changed it to the max (nine seconds) and
the symptom persists. I've worked with this for a couple of hours and
I'm out of ideas on what to look at next. It doesn't have the feel of a
sane misconfiguration, as I do actually get scans from what I tell TAME
to do.

Have you tried turning off the scanner, waiting about 10-20 seconds and
turning it back on? I see these errors occasionally (Umax Powerlook
III), and doing this usually stops it.

HTH,
Pete


--