I got some new and interesting results on my Epson GT-300.
Setting the variables SANE_DEBUG_EPSON and SANE_DEBUG_SANEI_PIO to
the value of 1, and launching scanimage for OS/2 with the command
scanimage -d epson
the program reported
[sanei_init_debug]: Setting debug level of epson to 1.
[sanei_init_debug]: Setting debug level of sanei_pio to 1.
[epson] Incompatible printer port (probably bi/directional)
[epson] type s 0x73
[epson] level a 0x61
[epson] attach: device doesn't look like an Epson scanner
Process terminated by SIGSEGV
core dumped
SYS1808:
Il processo e' terminato. Il codice per la diagnostica
software (codice dell'errore) e' 0005.
Note that the last message was brought by OS/2.
Setting the same variables to 2 gave the same result, while setting
them to 5 gave this:
[sanei_init_debug]: Setting debug level of epson to 5.
[epson] sane_init: sane 0.74
[epson] sane_init, >0x278<
[epson] sane_init, >0x278<
[epson] attach: opening 0x278
[sanei_init_debug]: Setting debug level of sanei_pio to 5.
[epson] send buf, size = 2
[epson] receive buf, expected = 1, got = 1
[epson] code 00
[epson] Incompatible printer port (probably bi/directional)
[epson] Illegal response of scanner for command: 00
[epson] type s 0x73
[epson] level a 0x61
[epson] send buf, size = 2
[epson] receive buf, expected = 4, got = 4
[epson] attach: device doesn't look like an Epson scanner
Process terminated by SIGSEGV
core dumped
SYS1808:
Il processo e' terminato. Il codice per la diagnostica
software (codice dell'errore) e' 0005.
I then tried activating the GT-6500 emulation, and reset the debug
variables to 1. Then scanimage returned
[sanei_init_debug]: Setting debug level of epson to 1.
[sanei_init_debug]: Setting debug level of sanei_pio to 1.
[epson] Incompatible printer port (probably bi/directional)
[epson] type s 0x73
[epson] level a 0x61
[epson] attach: device doesn't look like an Epson scanner
Process terminated by SIGSEGV
core dumped
SYS1808:
Il processo e' terminato. Il codice per la diagnostica
software (codice dell'errore) e' 0005.
which is the same result I gave from the first try. I then gave up.
Now, why scanimage doesn't recognize the scanner like an Epson one?
Is this due to TWAIN specifications or something else? The Epson GT-300
knows ISIS and TWAIN specifications, but does this have anything to do
with the reports?
Another try I did was setting the debug dll variable to 5, as the other
two. Launching scanimage the same result I got from the last try I did
setting the debug variables to 5.
I tried also setting the three debug variables to 1, and nothing
changed, so I think there must be something to be added to the DLL.
Yuri? Tu che ne dici?
Bye bye everybody,
Mentore
-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com