On Sat, 24 Nov 2001 23:29:34 +0100, abel deuring wrote:
>> 1. sharp.c refuses to compile because of the last changes in CVS:
>>
>> sharp.c: In function `do_cancel':
>> sharp.c:2262: storage size of `ds' isn't known
>> sharp.c:2264: warning: implicit declaration of function `shmctl'
>>
>> I thin
Franz Bakan wrote:
>
> On Thu, 22 Nov 2001 21:40:45 +0100, Henning Meier-Geinitz wrote:
>
> ...
> >Lots of changes, so please everyone: try compiling and running.
>
> I think the OS/2-specific changes which you comitted to CVS are
> OK but there are some other problems:
>
> 1. sharp.c refuses t
Hi,
> Are there any developers that have OS/2 and a USB scanner?
Well, me ...
> For that matter, are there any backends other than snapscan that use
> semaphores with USB?
No other backend seems to be using semaphores at all.
Regards,
Oliver
Hi Yuri,
> I can suggest to write a more general api, like sanei_thread, to allow
> a wider usage of code. Otherwise this code will be used only by
> snapscan sources.
That's probably the best solution - although no other backend seems to be
using semaphores at the moment.
Regards,
Oliver
--SUOF0GtieIMvvwua
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Fri, Nov 23, 2001 at 01:58:20AM +0100, Franz Bakan wrote:
> 2. epson-backend no longer works:
> for example=20
>scanimage --device=3Depson --resolution=3D1
Hi Oliver,
>For a start we can use separate functions for the semaphore operations (and
>maybe bundle them in a separate file), e.g. snapscani_semaphore_open(),
>snapscani_semaphore_close(), snapscani_semaphore_wait(),
OS/2 has a full semaphore API, so it will not be a problem to implement
su
Quoting Oliver Schwartz :
> Hi,
>
> > snapscan isn't compiled at all if ipc/semphore headers aren't found.
> > At least that's the intention.
> >
> > > My fix for this is to do something like
> > >
> > > #ifdef OS2
> > > #include "snapscan-usb-stubs.c"
> > > #else
> > > #include "snapscan-usb.c"
On Thu, 22 Nov 2001 21:40:45 +0100, Henning Meier-Geinitz wrote:
...
>Lots of changes, so please everyone: try compiling and running.
I think the OS/2-specific changes which you comitted to CVS are
OK but there are some other problems:
1. sharp.c refuses to compile because of the last changes in
On Thu, 22 Nov 2001 21:57:54 +0100, Henning Meier-Geinitz wrote:
>On Thu, Nov 22, 2001 at 10:12:33AM +0100, Paul Floyd wrote:
>> 1. configure failed to detect syslog. Had to edit include/sane/config.h
>
>Do you have any idea why this happens? Maybe we can fix configure.in.
This is what happens:
Hi,
> snapscan isn't compiled at all if ipc/semphore headers aren't found.
> At least that's the intention.
>
> > My fix for this is to do something like
> >
> > #ifdef OS2
> > #include "snapscan-usb-stubs.c"
> > #else
> > #include "snapscan-usb.c"
> > #endif
> >
> > where the 'stubs' version doe
Hi,
On Thu, Nov 22, 2001 at 10:12:33AM +0100, Paul Floyd wrote:
> 1. configure failed to detect syslog. Had to edit include/sane/config.h
Do you have any idea why this happens? Maybe we can fix configure.in.
> 3. snapscan is not supported on OS/2 (USB code uses headers that are not
> available).
Hi,
On Thu, Nov 22, 2001 at 01:14:47AM +0100, Franz Bakan wrote:
> On Wed, 21 Nov 2001 21:47:56 +0100, Henning Meier-Geinitz wrote:
>
> >Just send the mustek stuff to me. If this doesn't break anything, I
> >will include it.
>
> Sent.
Included in CVS now.
> >> 2. sanei/sanei_scsi.c
> >>
> >>
On Thu, 22 Nov 2001 10:12:33 +0100 (MET), Paul Floyd wrote:
>1. configure failed to detect syslog. Had to edit
include/sane/config.h
yes, that's another small problem.
A list of my manual modifications to get the OS/2
executables and libsane.dll is written down at:
http://home.tiscalinet.de/fb
Hi
I thought I'd throw in my experiences as well.
1. configure failed to detect syslog. Had to edit include/sane/config.h
2. similar problems with .exe as Franz. I fixed that by editing all the
Makefiles and changing the statements that look like [from memory]
ifneq ($exeext, .exe)
COPT
On Wed, 21 Nov 2001 21:47:56 +0100, Henning Meier-Geinitz wrote:
>Just send the mustek stuff to me. If this doesn't break anything, I
>will include it.
Sent.
>Without the diffs, does compilation fail or do the
>backends just don't work?
It compiles, but the backends don't work.
>> Additional
Hi,
On Wed, Nov 21, 2001 at 12:32:37AM +0100, Franz Bakan wrote:
> 1. mustek.c and microtek2.c
>
> As you probably allready know, the code for backends using fork()
> needs small changes to work with OS/2.
> I can provide diffs for mustek.c, mustek.h and microtek2.c, based on
> the work o
Hi Franz,
yes, please send me the diff for the microtek2 backend.
Which type of scanner was tested?
Regards,
Karsten Festag
Franz Bakan wrote:
> Hi,
>
> 1. mustek.c and microtek2.c
>
> As you probably allready know, the code for backends using fork()
> needs small changes to work with OS/
On Wed, 21 Nov 2001 19:40:36 +0100, Oliver Schwartz wrote:
>concerning snapscan: I have an OS/2 partition - it hasn't been booted for
>quite some time, but if you think there's a reasonable chance to get the
>snapscan code working with an (USB) scanner on OS/2 I'll try it.
Not at the moment. Th
Hi,
> It would be easy to implement these changes also for
> plustek, coolscan, agfafocus, snapscan and tamarack, but
> I will only add these if I have a chance to get this tested first.
> Regarding mustek and microtek I know that it works.
concerning snapscan: I have an OS/2 partition -
Hi,
1. mustek.c and microtek2.c
As you probably allready know, the code for backends using fork()
needs small changes to work with OS/2.
I can provide diffs for mustek.c, mustek.h and microtek2.c, based on
the work of Yuri Dario, if you are willing to include them.
Additionally sanei/s
20 matches
Mail list logo
