sane-project-website/old-archive/1998-10/0253.html

<!-- received="Fri Oct 23 05:22:30 1998 PDT" -->
<!-- sent="Fri, 23 Oct 1998 10:24:30 +0200" -->
<!-- name="Tobias Ernst" -->
<!-- email="tobi@bland.fido.de" -->
<!-- subject="Problems with SANE 0.74 for OS/2" -->
<!-- id="" -->
<!-- inreplyto="MSGID_2=3A2476=2F418_362fbc74@fidonet.org" -->
<title>sane-devel: Problems with SANE 0.74 for OS/2</title>
<h1>Problems with SANE 0.74 for OS/2</h1>
<b>Tobias Ernst</b> (<a href="mailto:tobi@bland.fido.de"><i>tobi@bland.fido.de</i></a>)<br>
<i>Fri, 23 Oct 1998 10:24:30 +0200</i>
<p>
<ul>
<li> <b>Messages sorted by:</b> <a href="date.html#253">[ date ]</a><a href="index.html#253">[ thread ]</a><a href="subject.html#253">[ subject ]</a><a href="author.html#253">[ author ]</a>
<!-- next="start" -->
<li> <b>Next message:</b> <a href="0254.html">Dirk Engelmann: "mustek color scan problem"</a>
<li> <b>Previous message:</b> <a href="0252.html">Dr. Andreas Bolsch: "Re: 6000SP: open of device /dev/dg0 failed, invalid argument"</a>
<!-- nextthread="start" -->
<!-- reply="end" -->
</ul>
<!-- body="start" -->
Hallo Yuri!<br>
<p>
I nohup'ed a GNU wget process on a Unix box at my university during this night,<br>
and now I finally have your sane 0.74 distribution archive. I see that you<br>
included a difference file containing all your changes on the source code.<br>
Thank you very much!<br>
<p>
As for the good news, I managed to address my scanner using your build. As for<br>
the bad news, there were several problems.<br>
<p>
Here is all information I think could be valuable:<br>
<p>
1) Config.Sys:<br>
<p>
   BASEDEV=AHA152X.ADD /V<br>
   BASEDEV=OS2SCSI.DMD<br>
   BASEDEV=OS2ASPI.DMD<br>
   DEVICE=E:\LOCAL\IMPOS21\CPASPI.SYS<br>
   device=d:\os2\boot\aspirout.sys<br>
<p>
   CPASPI.SYS is the Impos/2 driver, to this date my only possibility to<br>
   scan on OS/2 - but I don't think it should interfere with aspirout.sys.<br>
   At least, both load without any complaint.<br>
<p>
   The aspirout.sys in \os2\boot is still the one that was shipped with 0.72.<br>
<p>
2) I unzipped sane074b1.zip to e:\home\x<br>
<p>
3) I changed to e:\home\x\bin and started find_scanner. Here comes the first<br>
   queer result:<br>
<p>
   find-scanner: found scanner " Scanner 600A4 2.21" at device b0t0l0<br>
   find-scanner: found scanner " Scanner 600A4 2.21" at device b0t1l0<br>
   [and so on, until:]<br>
   find-scanner: found scanner " Scanner 600A4 2.21" at device b3t7l0<br>
<p>
   The scanner identification string is correct (Sane on FreeBSD reports <br>
   the same one), but I really don't have 32 scanners attached to this <br>
   system ;-).<br>
<p>
   As the scanner is attached to the first (only) SCSI controller at SCSI <br>
   ID 4, I then edited e:\home\x\conf to only contain a single line:<br>
<p>
   b0t4l0<br>
<p>
4) I then did<br>
   SET SANE_CONFIG_DIR=e:/home/x/conf<br>
<p>
5) I changed to e:\home\x\bin and tried scanimage --help. Result:<br>
<p>
   [...]<br>
<p>
   List of available devices:<br>
   pnm:0 pnm:1 microtek2:b0t4l0<br>
<p>
   Process terminated by SIGSEGV<br>
   core dumped<br>
   SYS1808:<br>
   Der Proze<7A> wurde gestoppt. Der Softwarediagnosecode<br>
   (Fehlercode der Ausnahmebedingung) ist  0005.<br>
<p>
   If you did keep a debugging version of this build, I can send you the <br>
   core file if you wish.<br>
<p>
   "scanimage -d microtek2:b0t4l0 --help" did work, however.<br>
<p>
6) I then scanned my first image on the command line. The scan speed was <br>
   roughly equal to that of ImpOS/2. However, just like with ImpOS/2, my <br>
   computer is hardly usable during the scan progress. It is not completely <br>
   blocked (i.E. I can switch through windows every two seconds or so), but <br>
   it is even unusable for tasks as simple as entering a text.<br>
<p>
   Is this normal behaviour? Or is it related to a driver problem of my<br>
   machine? If it is normal, do you think it could be changed? I suspect<br>
   that the problem is somewhere in the ASPI driver layer - perhaps one<br>
   would have to write a multithreaded aspirout.sys in order to circumvent<br>
   this problem ... ?<br>
<p>
7) As for the Sane/2 frontend:  <br>
<p>
   * Please make it possible to enter numbers into the dialog fields<br>
     like resolution etc. Pressing and holding the PgUp-Button until the<br>
     field has scrolled to the desired number is very boring.<br>
<p>
   * The frontend seems to start up on a hard-coded position. This is<br>
     a) bad behaviour in general, and b) the hard-coded position is such<br>
     that the title bar is ouside the physical screen on my 800x600 display<br>
     ...<br>
<p>
   * Most of the input boxes (like Halftoning) are not wide enough to<br>
     display the text that is in them. Please give them some more space.<br>
<p>
   * When scanning with the frontend in 24 bit mode, the colors are wrong.<br>
     This is not so when scanning with the command line.<br>
<p>
   * The frontend complains about the --resolution failing with "invalid<br>
     argument", no matter what resolution I enter.  (All these resolutions<br>
     work on the command line).<br>
<p>
But again thanks for your work, and take this as positive critic! I surely want<br>
to help you making Sane the best scan interface for OS/2. :-).<br>
<p>
Viele Gr<47><72>e,<br>
Tobias<br>
<p>
<pre>
--
Source code, list archive, and docs: <a href="http://www.mostang.com/sane/">http://www.mostang.com/sane/</a>
To unsubscribe: echo unsubscribe sane-devel | mail <a href="mailto:majordomo@mostang.com">majordomo@mostang.com</a>
</pre>
<!-- body="end" -->
<p>
<ul>
<!-- next="start" -->
<li> <b>Next message:</b> <a href="0254.html">Dirk Engelmann: "mustek color scan problem"</a>
<li> <b>Previous message:</b> <a href="0252.html">Dr. Andreas Bolsch: "Re: 6000SP: open of device /dev/dg0 failed, invalid argument"</a>
<!-- nextthread="start" -->
<!-- reply="end" -->
</ul>