[sane-devel] Formulardaten

2007-11-15 Thread cgi-mai...@kundenserver.de


===
== Neuer Eintrag
===

  
---
-- Formular: 'adddev'
---

1. Your email address:
   'nonamehelp at gmail.com'
2. Manufacturer (e.g. "Mustek"):
   'HP'
3. Model name (e.g. ScanExpress 1200UB):
   'Scanjet 4890'
4. Bus type:
   'USB'
5. Vendor id (e.g. 0x001):
   '0x03f0'
6. Product id (e.g. 0x0002):
   '0x1b05'
7. Chipset (e.g. lm9831):
   'GL841'
8. Comments (e.g. similar to Mustek 1234):
   ''
9. Data (e.g. sane-find-scanner -v -v):
   'This is sane-find-scanner from sane-backends 1.0.18

  # sane-find-scanner will now attempt to detect your scanner. If the
  # result is different from what you expected, first make sure your
  # scanner is powered up and properly connected to your computer.

searching for SCSI scanners:
checking /dev/scanner... failed to open (Invalid argument)
checking /dev/sg0... failed to open (Invalid argument)
checking /dev/sg1... failed to open (Invalid argument)
checking /dev/sg2... failed to open (Invalid argument)
checking /dev/sg3... failed to open (Invalid argument)
checking /dev/sg4... failed to open (Invalid argument)
checking /dev/sg5... failed to open (Invalid argument)
checking /dev/sg6... failed to open (Invalid argument)
checking /dev/sg7... failed to open (Invalid argument)
checking /dev/sg8... failed to open (Invalid argument)
checking /dev/sg9... failed to open (Invalid argument)
checking /dev/sga... failed to open (Invalid argument)
checking /dev/sgb... failed to open (Invalid argument)
checking /dev/sgc... failed to open (Invalid argument)
checking /dev/sgd... failed to open (Invalid argument)
checking /dev/sge... failed to open (Invalid argument)
checking /dev/sgf... failed to open (Invalid argument)
checking /dev/sgg... failed to open (Invalid argument)
checking /dev/sgh... failed to open (Invalid argument)
checking /dev/sgi... failed to open (Invalid argument)
checking /dev/sgj... failed to open (Invalid argument)
checking /dev/sgk... failed to open (Invalid argument)
checking /dev/sgl... failed to open (Invalid argument)
checking /dev/sgm... failed to open (Invalid argument)
checking /dev/sgn... failed to open (Invalid argument)
checking /dev/sgo... failed to open (Invalid argument)
checking /dev/sgp... failed to open (Invalid argument)
checking /dev/sgq... failed to open (Invalid argument)
checking /dev/sgr... failed to open (Invalid argument)
checking /dev/sgs... failed to open (Invalid argument)
checking /dev/sgt... failed to open (Invalid argument)
checking /dev/sgu... failed to open (Invalid argument)
checking /dev/sgv... failed to open (Invalid argument)
checking /dev/sgw... failed to open (Invalid argument)
checking /dev/sgx... failed to open (Invalid argument)
checking /dev/sgy... failed to open (Invalid argument)
checking /dev/sgz... failed to open (Invalid argument)
  # No SCSI scanners found. If you expected something different, make sure that
  # you have loaded a kernel SCSI driver for your SCSI adapter.

searching for USB scanners:
checking /dev/usb/scanner... failed to open (Invalid argument)
checking /dev/usb/scanner0... failed to open (Invalid argument)
checking /dev/usb/scanner1... failed to open (Invalid argument)
checking /dev/usb/scanner2... failed to open (Invalid argument)
checking /dev/usb/scanner3... failed to open (Invalid argument)
checking /dev/usb/scanner4... failed to open (Invalid argument)
checking /dev/usb/scanner5... failed to open (Invalid argument)
checking /dev/usb/scanner5... failed to open (Invalid argument)
checking /dev/usb/scanner7... failed to open (Invalid argument)
checking /dev/usb/scanner8... failed to open (Invalid argument)
checking /dev/usb/scanner9... failed to open (Invalid argument)
checking /dev/usb/scanner10... failed to open (Invalid argument)
checking /dev/usb/scanner11... failed to open (Invalid argument)
checking /dev/usb/scanner12... failed to open (Invalid argument)
checking /dev/usb/scanner13... failed to open (Invalid argument)
checking /dev/usb/scanner14... failed to open (Invalid argument)
checking /dev/usb/scanner15... failed to open (Invalid argument)
checking /dev/usbscanner... failed to open (Invalid argument)
checking /dev/usbscanner0... failed to open (Invalid argument)
checking /dev/usbscanner1... failed to open (Invalid argument)
checking /dev/usbscanner2... failed to open (Invalid argument)
checking /dev/usbscanner3... failed to open (Invalid argument)
checking /dev/usbscanner4... failed to open (Invalid argument)
checking /dev/usbscanner5... failed to open (Invalid argument)
checking /dev/usbscanner6... failed to open (Invalid argument)
checking /dev/usbscanner7... failed to open (Invalid argument)
checking /dev/usbscanner8... failed to open (Invalid argument)
checking /dev/usbscanner9... failed to open (Invalid argument)
checking /dev/usbscanner10... failed to open (Invalid argument)
checking /dev/usbscanner11... failed to

[sane-devel] Canoscan 1220U vertical stripes

2007-11-15 Thread Gerhard Jaeger
Am Montag, 12. November 2007 17:44:40 schrieb Guillermo Espertino:
> It returns this (the second line, tell me if you need the whole debug
> output):
> [plustek] Plustek backend V0.51-16, part of sane-backends 1.0.18-cvs
>
>
Okay - I see.

I've testet here on two boxes and got two different results with
the same scanner :(
The problem is the dark calibration. The 1220 offers a black strip
for the calibration, which is scanned. Other devices which don't
have this, simply switch off the lamp.

So locally I also tweaked the code to not use the black strip and
the stripes disappear (on the affected box). 

Are you able to compile SANE on your own? 

- Gerhard



[sane-devel] Canoscan 1220U vertical stripes]

2007-11-15 Thread Guillermo Espertino
> Are you able to compile SANE on your own? 

I can try :)
I'm not very experienced on compiling but I can try at least.
Do I have to replace libsane only?

Thanks in advance,
Guillermo Espertino.




[sane-devel] SANE Release?

2007-11-15 Thread m. allan noah
It's been 15 months since SANE 1.0.18 was released. In that time,
we've had a few new backends added, many bugs fixed and new models
supported.

With Henning being so busy, I am offering to take the lead on
releasing 1.0.19. However, I will need some handholding, so if Henning
(or anyone else for that matter :) wants to do it instead, I would be
happy.

comments?

allan
-- 
"The truth is an offense, but not a sin"



[sane-devel] SANE Release?

2007-11-15 Thread Henning Geinitz
Hi,

On 2007-11-15 13:58, m. allan noah wrote:
> It's been 15 months since SANE 1.0.18 was released. In that time,
> we've had a few new backends added, many bugs fixed and new models
> supported.

Good idea to make a new release!

> With Henning being so busy, I am offering to take the lead on
> releasing 1.0.19. However, I will need some handholding, so if Henning
> (or anyone else for that matter :) wants to do it instead, I would be
> happy.

I won't have enough time...

There is a guideline in doc/releases.txt that might help.

Uploading is done only to alioth (FTP+HTTP) as rpm.org does not exist anymore.

Good luck!

Bye,
  Henning



[sane-devel] SANE Release?

2007-11-15 Thread m. allan noah
can you make me a project admin on alioth so i can update those pages?

allan

On Nov 15, 2007 3:35 PM, Henning Geinitz  wrote:
> Hi,
>
> On 2007-11-15 13:58, m. allan noah wrote:
> > It's been 15 months since SANE 1.0.18 was released. In that time,
> > we've had a few new backends added, many bugs fixed and new models
> > supported.
>
> Good idea to make a new release!
>
> > With Henning being so busy, I am offering to take the lead on
> > releasing 1.0.19. However, I will need some handholding, so if Henning
> > (or anyone else for that matter :) wants to do it instead, I would be
> > happy.
>
> I won't have enough time...
>
> There is a guideline in doc/releases.txt that might help.
>
> Uploading is done only to alioth (FTP+HTTP) as rpm.org does not exist anymore.
>
> Good luck!
>
> Bye,
>   Henning
>
> --
> sane-devel mailing list: sane-devel at lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/sane-devel
> Unsubscribe: Send mail with subject "unsubscribe your_password"
>  to sane-devel-request at lists.alioth.debian.org
>



-- 
"The truth is an offense, but not a sin"



[sane-devel] scanimage: sane_start: Out of memory - Umax Astra 600S

2007-11-15 Thread m. allan noah
On Nov 14, 2007 5:19 PM, Alexander Melhuish  wrote:
> Hello,
>
> I am attempting to make my scanner work. It is a Umax Astra 600S
> attached via a SCSI-Firewire interface to my MacBook, which is running
> Mac OS X 10.5. I'm using the latest version of the TWAIN-SANE
> packages, which includes sane-backends 1.0.18. I tested this
> configuration with a demo of SilverFast, which functioned properly.
>
> So far, the only way to have a complete response is using the --mode
> LineArt option - anything else and the scanner and/or interface
> 'crash'. Even in this mode though, no image is produced.
>
> Using SANE_DEBUG_SANEI_SCSI=255 and SANE_DEBUG_UMAX=255, I produced
> the attached log file. I have tried experimenting a little with the
> buffer options for sane_umax, but I'm not convinced that the back-end
> is at fault.
>
> Anyone with experience of 'Out of memory' errors or sane_umax, please
> respond. Any suggestions are welcome to just get basic functionality
> to start with.

looks like a threading issue, and the 'eom' errors are just a side
effect. I dont know anything about threading on OSX- but i bet mr
ellert does. If he does not respond to this mail, you should email him
directly.

allan
-- 
"The truth is an offense, but not a sin"



[sane-devel] scanimage: sane_start: Out of memory - Umax Astra 600S

2007-11-15 Thread Mattias Ellert
15 nov 2007 kl. 20.57 skrev m. allan noah:

> On Nov 14, 2007 5:19 PM, Alexander Melhuish   
> wrote:
>> Hello,
>>
>> I am attempting to make my scanner work. It is a Umax Astra 600S
>> attached via a SCSI-Firewire interface to my MacBook, which is  
>> running
>> Mac OS X 10.5. I'm using the latest version of the TWAIN-SANE
>> packages, which includes sane-backends 1.0.18. I tested this
>> configuration with a demo of SilverFast, which functioned properly.
>>
>> So far, the only way to have a complete response is using the --mode
>> LineArt option - anything else and the scanner and/or interface
>> 'crash'. Even in this mode though, no image is produced.
>>
>> Using SANE_DEBUG_SANEI_SCSI=255 and SANE_DEBUG_UMAX=255, I produced
>> the attached log file. I have tried experimenting a little with the
>> buffer options for sane_umax, but I'm not convinced that the back-end
>> is at fault.
>>
>> Anyone with experience of 'Out of memory' errors or sane_umax, please
>> respond. Any suggestions are welcome to just get basic functionality
>> to start with.
>
> looks like a threading issue, and the 'eom' errors are just a side
> effect. I dont know anything about threading on OSX- but i bet mr
> ellert does. If he does not respond to this mail, you should email him
> directly.
>
> allan

Could you add SANE_DEBUG_SANEI_THREAD=255 to the set of debug values?

Mattias

-- next part --
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 1438 bytes
Desc: not available
Url : 
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20071115/7e01f21c/attachment.bin
 


[sane-devel] SANE Release?

2007-11-15 Thread Étienne Bersac
Hi,

This would be very nice to have a release allowing major distros to ship
with updated SANE for next spring. Ubuntu ships CVS version of SANE
(2007-05-05). There is definitily a needs for a new release.

Regards,
?tienne
-- 
E Ultre?a !




[sane-devel] SANE Release?

2007-11-15 Thread Julien BLACHE
?tienne Bersac  wrote:

Hi,

> This would be very nice to have a release allowing major distros to ship
> with updated SANE for next spring. Ubuntu ships CVS version of SANE
> (2007-05-05). There is definitily a needs for a new release.

As far as Ubuntu goes, they're just shipping whatever I decide to ship
in Debian. And if it lands in Debian you can be sure that it's
suitable for release.

JB.

-- 
Julien BLACHE    
  GPG KeyID 0xF5D65169



[sane-devel] scanimage: sane_start: Out of memory - Umax Astra 600S

2007-11-15 Thread m. allan noah
On 11/15/07, Mattias Ellert  wrote:
> 15 nov 2007 kl. 22.14 skrev Mattias Ellert:
>
> > 15 nov 2007 kl. 20.57 skrev m. allan noah:
> >
> >> On Nov 14, 2007 5:19 PM, Alexander Melhuish
> >>  wrote:
> >>> Hello,
> >>>
> >>> I am attempting to make my scanner work. It is a Umax Astra 600S
> >>> attached via a SCSI-Firewire interface to my MacBook, which is
> >>> running
> >>> Mac OS X 10.5. I'm using the latest version of the TWAIN-SANE
> >>> packages, which includes sane-backends 1.0.18. I tested this
> >>> configuration with a demo of SilverFast, which functioned properly.
> >>>
> >>> So far, the only way to have a complete response is using the --mode
> >>> LineArt option - anything else and the scanner and/or interface
> >>> 'crash'. Even in this mode though, no image is produced.
> >>>
> >>> Using SANE_DEBUG_SANEI_SCSI=255 and SANE_DEBUG_UMAX=255, I produced
> >>> the attached log file. I have tried experimenting a little with the
> >>> buffer options for sane_umax, but I'm not convinced that the back-
> >>> end
> >>> is at fault.
> >>>
> >>> Anyone with experience of 'Out of memory' errors or sane_umax,
> >>> please
> >>> respond. Any suggestions are welcome to just get basic functionality
> >>> to start with.
> >>
> >> looks like a threading issue, and the 'eom' errors are just a side
> >> effect. I dont know anything about threading on OSX- but i bet mr
> >> ellert does. If he does not respond to this mail, you should email
> >> him
> >> directly.
> >>
> >> allan
> >
> > Could you add SANE_DEBUG_SANEI_THREAD=255 to the set of debug values?
> >
> >   Mattias
>
> Looking at the umax backend, I think the problem is line 7993 in
> umax.c that says:
>
>if (scanner->reader_pid < 0)
>
> This line should be
>
>if (scanner->reader_pid = -1)
>

i assume you mean '=='?

allan

> I have compiled a test package where I have applied this change, which
> is available here:
>
> http://www.ellert.se/PKGS/test/sane-backends.pkg.tar.gz
>
> Let us know if it works for you.
>
> Mattias
>
>
>
> --
> sane-devel mailing list: sane-devel at lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/sane-devel
> Unsubscribe: Send mail with subject "unsubscribe your_password"
>  to sane-devel-request at lists.alioth.debian.org
>
>


-- 
"The truth is an offense, but not a sin"