Hi John,
yes, I created a subdirectory called /usr/programs/ Then I decompressed
the two files into it, followed by the command "./configure; make; make
install". But it appears that the file "xscanimage" isn't physically on
my filesystem. I just tried the older version of sane-1.0.2, but it
doesn't work either.
How does the system have to be prepared/configured for the for file to
be created? Isn't there an rpm-version of these two files so
there is no need anymore to compile it myself?
Regards,
Timo
John Craig schrieb:
>
> Hi,
>
> I assume you compiled the program successfully (no fatal errors) and installed
> it with 'make install'. You need to find out where it was installed, possibly
> in /usr/local/bin. You need to make sure this is in your path. Otherwise, you
> can invoke it with the full path name-- '/usr/local/bin/xscanimage'
>
> Timo Hoderlein wrote:
>
> > Hi Sébastien,
> >
> > There something wrong! I installed a virgin system of Mandrake 7.0,
> > deinstalled the sane package provided by Mandrake and downloaded the
> > files snapscan-28102000_tar.gz of the backend and sane-1.0.3_tar.gz.
> > Then I followed the instructions in the documentation. When I then try
> > to invoke xscanimage, the command doesn't exist on the file system. What
> > is the problem?
> >
> > So, I couldn't get to the point of trying out the patch.
> >
> > Greetings
> >
> > Timo
> >
> > Sébastien Sablé schrieb:
> > >
> > > Timo Hoderlein <timo.hoderlein@wanadoo.es> writes:
> > >
> > > > But when I try to scan color pictures, I only get final results of
> > > > pictures of the size of CD covers and the scanning works only up to a
> > > > resolution of 75 dpi. The result, though, is worthless because the parts
> > > > of the picture are disarranged and displaced and the colors are not like
> > > > the original and blurred. At a depth of 100 dpi and higher, the scanner
> > > > moves through the whole area, but the frontend does not receive RGB-data
> > > > ("no green status bar").
> > >
> > > I had the same problems with my scanner, but corrected them thanks to
> > > a few changes in snapscan. I made the same changes for your model
> > > (SNAPSCAN310) in this version of the backend:
> > >
> > > http://download.sourceforge.net/snapscan/snapscan-28102000.tar.gz
> > >
> > > You can read documentation on how to use this here:
> > >
> > > http://snapscan.sourceforge.net/
> > >
> > > If this doesn't work, could you please try:
> > >
> > > export SANE_DEBUG_SNAPSCAN=1
> > >
> > > before scanning to see which model is detected.
> > >
> > > If this works, please let me know so we can add it in snapscan.
> > >
> > > > possibility to scan with a resolution of more than 300 dpi.
> > >
> > > Your scanner probably can't go that high.
> > >
> > > --
> > > Sébastien Sablé
> > > sebastien.sable@gmx.net
> > >
> > > --
> > > Source code, list archive, and docs: http://www.mostang.com/sane/
> > > To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com
> >
> > --
> > Source code, list archive, and docs: http://www.mostang.com/sane/
> > To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com
>
> --
> Source code, list archive, and docs: http://www.mostang.com/sane/
> To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com
-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com
This archive was generated by hypermail 2b29 : Thu Nov 02 2000 - 11:32:50 PST