[sane-devel] Umax 1220p OS/2 errors

Franz Bakan Franz Bakan" <fbakan@gmx.net
Thu, 14 Feb 2002 21:30:16 +0100 (CET)


Hi,

Someone tried to use sane-1.0.7 on OS/2 for his Umax 1220p Scanner but did not
succeed so far. I have no experience with parallelport-scanners so I have no
chance to solve this problem.

The command 

 set SANE_DEBUG_UMAX_PP=255
 set SANE_DEBUG_UMAX_PP_LOW=255
 scanimage --device=umax_pp 1>1.pnm 2>errors.log

results in the following errors.log

...
[umax_pp_low] Command bloc 8: 00 00 04 00 02 00 00 0C 00 03 C1 80 00 20 02 00 16 \
              41 E0 AC 03 03 00 00 46 A0 00 00 00 00 00 00 00 10 FFF00 
[umax_pp_low] 	->xskip     =0x41 (65)
[umax_pp_low] 	->xend      =0xACE (2766)
[umax_pp_low] 	->scan width=0xA8C (2700)
[umax_pp_low] 	->bytes/line=0x2500 (9472)
[umax_pp_low] 
[umax_pp_low] SendWord() passed   (umax_pp_low.c:2397)
[umax_pp_low] SendWord, reg1C=0x91 (umax_pp_low.c:2410)
[umax_pp_low] SendWord(cmd3) passed (umax_pp_low.c:3254)
[umax_pp_low] SendData, reg19=0xE8 (umax_pp_low.c:2957)
[umax_pp_low] SendData failed  got 0xE8 instead of 0xC0 or 0xD0 (umax_pp_low.c:2961)
[umax_pp_low] Blindly going on .....
[umax_pp_low] SendData, reg1C=0x91 (umax_pp_low.c:2975)
[umax_pp_low] SendData(data,2048) passed ...  (umax_pp_low.c:3261)
[umax_pp_low] SendWord() passed   (umax_pp_low.c:2397)
[umax_pp_low] SendWord failed  got 0xE8 instead of 0xC0 or 0xD0 (umax_pp_low.c:2401)
[umax_pp_low] Blindly going on .....
[umax_pp_low] SendWord, reg1C=0x91 (umax_pp_low.c:2410)
[umax_pp_low] SendWord(cmd4) passed (umax_pp_low.c:3265)
[umax_pp_low] EPPRegisterWrite(0xE,0xD) passed...   (umax_pp_low.c:3001)
[umax_pp_low] EPPRegisterWrite(0xF,0x0) passed...   (umax_pp_low.c:3002)
[umax_pp_low] Unexpected reg19: 0xE8 instead of 0xC0 or 0xD0 (umax_pp_low.c:3007)
[umax_pp_low] PausedReadData(2048,dest) failed (umax_pp_low.c:3270)
[umax_pp_low] CmdSetDataBuffer(initbuf) failed ! (umax_pp_low.c:4961)
[umax_pp] attach: failed to probe scanner on port 0x378
[umax_pp] attach: couldn't attach to `0x378' (Error during device I/O)
...

What could be wrong?

Any ideas?

Complete errors.log available on request.

Bye,
Franz