Warp4 fixpak 5
Microtek E3 scanner, which runs fine in windows, and using the CFM
demo.
I have the emx runtime loaded on my system already.
I unzip sane101p3 into a directory, setup the aspirout.sys in the
config and I see it load okay when I boot.
find-scanner finds a scanner at b0t0l0, as does scanimage -L
(interesting that it also finds the same device at b0t*l0 where * =
0-6 )
I use the command line from that directory:
SCANIMAGE.EXE -d microtek:b0t6l0 --resolution 156 -x50 -y50
The scanner bumps and grinds a bit and almost begins the scan, and
then I get a error message that emxlibcm.dll has caused an access
violation. Other times I get an access violation message that is
caused by libsane.dll
Either one ends with the error message screen, followed by the return
to the screen and it shows this:
[F:\sane]SCANIMAGE.EXE -d microtek:b0t6l0 --resolution 156 -x50 -y50
SCANIMAGE.EXE: sane_start: Error during device I/O
Process terminated by SIGSEGV
core dumped
SYS1808:
The process has stopped. The software diagnostic
code (exception code) is 0005.
I think I have also seen exception code 0008
These are the same errors I would get when running the 0.74 version
some time ago.
I am a bit confused as to what this means, and how to go about fixing
it.
Yuri told me to set my debug statement to set sane_debug_microtek=128,
which I did, but I have no idea what that does for me :)
Thank you all for any advice or suggestions.
Regards,
John
-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com