On Fri, Oct 11, 2002 at 08:19:58PM -0400, Karl Heinz Kremer wrote:
> On Fri, Oct 04, 2002 at 07:48:04PM -0500, Petr Hlustik wrote:
> > Well, after I've written all this, I remembered I brought in my Debian
> > Sarge laptop - so I installed sane there and tried the scanner there after
> > modyfing t
--yrj/dFKFPuw6o+aM
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Fri, Oct 04, 2002 at 07:48:04PM -0500, Petr Hlustik wrote:
> Well, after I've written all this, I remembered I brought in my Debian
> Sarge laptop - so I install
On Fri, Oct 04, 2002 at 07:14:27AM -0400, Karl Heinz Kremer wrote:
> Did you change anything since it worked? And I really mean anything,
> even if you think it's absolutely unreleated to scanning (e.g.
> connect or turn on a parallel printer). I don't think that you've
> changed anything on the s
--SLDf9lqlvOQaIe6s
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Did you change anything since it worked? And I really mean anything,
even if you think it's absolutely unreleated to scanning (e.g.=20
connect or turn on a parallel
On Thu, 3 Oct 2002, Petr Hlustik wrote:
> [epson] sane_init, >pio 0x378<
> [epson] sane_init, >pio 0x378<
A question. Why is this in there twice? I don't think this is your
problem, but it looks like it's trying to attach twicw.
--
Greg Weeks
http://durendal.org/greg/
Hello Greg et al.,
I'm afraid I'm back with another problem. I tried to run the scanner as
UID 0 again and got this new error:
scanimage --list-devices
[epson] Unknown type or level B, using B3
device `epson:0x378' is a Epson flatbed scanner
default device is `epson:0x378'
plus the scanner is
On Thu, 3 Oct 2002, Petr Hlustik wrote:
> I guess I'm back to either scanimage or su to root, with no Gimp
> integration. Sigh.
I used saned not suid but ran as root from inetd. This isn't the fastest,
but it worked ok for me.
--
Greg Weeks
http://durendal.org/greg/
On Thu, Oct 03, 2002 at 02:29:04PM -0400, k...@khk.net wrote:
> This is a limitation all parallel port scanners have when used with Sane.
> You already know the reason for this: Sane uses the IO ports and not
> the device file to talk to the scanner.
>
> As long as you trust everybody who's using
On Thu, Oct 03, 2002 at 02:29:04PM -0400, k...@khk.net wrote:
> This is a limitation all parallel port scanners have when used with Sane.
> You already know the reason for this: Sane uses the IO ports and not
> the device file to talk to the scanner.
>
> As long as you trust everybody who's using
This is a limitation all parallel port scanners have when used with Sane.
You already know the reason for this: Sane uses the IO ports and not
the device file to talk to the scanner.
As long as you trust everybody who's using your computer, you can just
make the frontend(s) you are using setuid ro
On Thu, 3 Oct 2002, Petr Hlustik wrote:
> Hello,
>
> I got my hands on the Epson Expression636 which comes with both SCSI and
> parallel ports. W/o SCSI on my RedHat8 box, I tried the parallel
> port. Scanning works if I'm root (Yes!!) but not as a regular user. This my
I noticed this too. I'm as
Hello,
I got my hands on the Epson Expression636 which comes with both SCSI and
parallel ports. W/o SCSI on my RedHat8 box, I tried the parallel
port. Scanning works if I'm root (Yes!!) but not as a regular user. This my
diagnostics:
SANE_DEBUG_EPSON=9 scanimage -d epson:0x378 > pnm.out
[sanei_d
12 matches
Mail list logo
