On Wednesday 13 March 2002 12:35 pm, William Smyth wrote:
>Hi All
>
>I have noticed a lot of work is going on writing a sane driver
> that will work with the EPSON Perfection 1250. Will this driver
> when completed work with a EPSON Perfection 1250 Photo ? I can
> not add to the coding side of the
Hi,
On Wed, Mar 13, 2002 at 06:28:02PM +, Richard Davies wrote:
> SANE_DEBUG_SNAPSCAN=255 scanimage -L
>
> [sanei_debug] Setting debug level of snapscan to 255.
> [snapscan] sane_snapscan_init
> [snapscan] sane_snapscan_init: Snapscan backend version 1.4.7
> [snapscan] add_device(/dev/sg0)
>
Hi,
On Tue, Mar 12, 2002 at 11:46:57PM -0600, Frank Zago wrote:
> I've added a new backend for TECO / Relisys scanners.
Fascinating, yet another backend. Do you ever sleep? :-)
> Currently it only handles the Relisys RELI 2412.
> It should also work with the following scanners:
> AVEC 2400
And this is what I have found inside:
P98003
0022H
UT51C162JC-35
9940
GENIUS 04-43-006B
9935
WM
8143-12C
A4AH54P
UTC
78D05
WL
83AK
LM2595S
-ADJ P+
Now, please can you tell me what scanner I have?
Hi,
On Mon, Mar 11, 2002 at 06:05:41PM -0500, w...@astro.umd.edu wrote:
> This is a nit but an annoying one for me. sane-frontend-1.0.7 hides the
> installs of its binaries. On my solaris installs I like to document
> everything
> installed so that I can more easily manage things on update or r
Hi,
On Wed, Mar 13, 2002 at 01:17:05AM +, Richard Davies wrote:
> [sanei_debug] Setting debug level of snapscan to 255.
> [snapscan] sane_snapscan_init
> [snapscan] sane_snapscan_init: Snapscan backend version 1.4.0
> [snapscan] add_device(/dev/sga)
/dev/sga? Didn't you write that you enters
Further steps taken to isolate the problem
Confirmed conflict between scanner and CD burner.
Removed sane 1.0.6 and replaced it with sane 1.0.7
SANE_DEBUG_SNAPSCAN=255 scanimage -L
[sanei_debug] Setting debug level of snapscan to 255.
[snapscan] sane_snapscan_init
[snapscan] sane_snapscan_init:
The SANE network protocol says that data is transfered as a
series of blocks, each preceeded by the block size as a 4-byte
integer. Observing, it appears that blocks are usually about 8KB
(8188 in fact). However, a frontend program doesn't get a full
block on each call. Nor does it get the maximum
> On Tue, Mar 12, 2002 at 11:46:57PM -0600, Frank Zago wrote:
> > I've added a new backend for TECO / Relisys scanners.
>
> Fascinating, yet another backend. Do you ever sleep? :-)
Sometimes :)
I've a written a set of templates that cut down the time of
development of a new scsi backend: get some
Dear (X)sane gurus,
My setup:
- Xsane server on FreeBSD, with sane (backend and
frontend) v. 1.0.7, Xsane v. 0.84,
- Windows NT with xsane-win 0.84.
On FreeBSD no problems.
On Windows NT: scanimage, no problems. Xsane-win: mode
Viewer and mode Save, no problems. But in mode
Preview, Acquire Pre
On Sun, Mar 10, 2002 at 07:58:28PM +, Richard Davies wrote:
I don't know what is going on but it suddenly gave me this information when I
rebooted it and tried the SANE_DEBUG_SNAPSCAN=255 scanimage -L again
[sanei_debug] Setting debug level of snapscan to 255.
[snapscan] sane_snapscan_init
[
11 matches
Mail list logo
