plustek: plustek-driver/Suse 7.1/Kernel 2.4.
Subject:
Re: plustek-driver/Suse 7.1/Kernel 2.4.
From:
####@####.####
Date:
14 Mar 2001 11:56:23 -0000
Message-Id: <14d8tt-1sb0j2C@fwd01.sul.t-online.com>
Hi Thomas,
in general, it should be possible to download a
plustek-module... tar-ball, unpack it anywhere and build
the driver. Please have a look at my homepage where you find
which version is suitable for SANE-1.0.4.
If you need the SANE sources, install the sane-... source-rpm
from the SuSE-disk 6 or 7. The sources then can be found
in /usr/src/packages...
I recently did the same with SuSE 7.1 and a binary version
of SANE 1.0.4 and this works without any problems
(I must admit, that I use the latest development release
of the driver which is not available to the public...)
Gerhard
P.S.: There's a german installation guide in each tar-ball,
look for INSTALL.GER
>----- Ursprüngliche Nachricht -----
>Absender: ####@####.####
>Betreff: plustek-driver/Suse 7.1/Kernel 2.4.
>Empfänger: ####@####.####
>Datum: 12. Mär 2001 21:11
>
> Hi,
>
> Firts: Thanks a lot for your providing a plustek-driver for Linux.
In
> combination with sane 1.03, suse 7.0 and kernel 2.2 my scanner OP
9630
> worked fine. Great pleasure .-))
>
> But now ...
>
> I recently updated from 7.0 to 7.1 installing the new kernel 2.4. I
> tried to make my scanner run, but I failed.
>
> Suse provides a special sane 1.04 installation with no "backend" and
all
> the other stuff you get from the sane homepage with the
sane-tarball.
>
> However, www.mostang.com has been not reachable for the last three
days.
> I couldn't get sane 1.04 yet, and I need some scans very urgently.
>
> Question: is it possible to compile and install the plustek-driver
with
> suse-sane and kernel 2.4? Is there any driver? Where should I untar
the
> driver? What I have to do??? I had a glance at the RFMs, but I
> understood nothing :-(
>
> Could you help me?
>
> Regards
> Thomas Mandl
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail: ####@####.####
> For additional commands, e-mail: ####@####.####
>
>
