<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi allan,<div><br></div><div>Look I've done some poking around to implement these changes that you stated - its a bit like an elephant with a bazooka in a china shop. </div><div><br></div><div>I have libsub installed and the backends. I've gone through M. Ellerts site - but it only takes you through simple command-line scanning. </div><div><br></div><div>What I cant get into is the genesys_devices.c file.. From the abandoned backend help pages of Henning Meier-Geinitz they state there are three files in the backend..</div><div><h2></h2><p style="margin-left: 11%; margin-top: 1em;"><i>/usr/local/etc/sane.d/genesys.conf</i></p><p style="margin-left: 22%;">The backend configuration file
(see also description of <b>SANE_CONFIG_DIR</b> below).</p><p style="margin-left: 11%;"><i>/usr/local/lib/sane/libsane−genesys.a</i></p><p style="margin-left: 22%;">The static library implementing
this backend.</p><p style="margin-left: 11%;"><i>/usr/local/lib/sane/libsane−genesys.so</i></p><p style="margin-left: 22%;">The shared library implementing
this backend (present on systems that support dynamic
loading).</p><div><br></div></div><div><br></div><div>Is one of these files the genesys_devices.c file you are taliking about? Or is it inside one of these files? If so - can I use "emac" in terminal to pull up the flagged file and change it?</div><div><br></div><div>Also, do you know the equivalent of 'make' and 'run' in terminal?</div><div><br></div><div>Thanks Much</div><div><br></div><div><br></div><div>Ben</div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br><div><div>On 11 Feb 2011, at 21:25, m. allan noah wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>Stop talking about prefs. We are talking about source code :)<br><br>I've never compiled sane on a mac before (M. Ellert might have more<br>about that on his site) But i can give you the general idea:<br><br>1. install the libusb-dev package (or libusb-devel, not sure what your<br>OS calls it)<br>2. install gcc package and it's required dependencies (and 'make' too)<br>3. download latest sane-backends from <a href="http://www.sane-project.org/snapshots/">http://www.sane-project.org/snapshots/</a><br>4. tar xzf sane-backends......tgz<br>6. cd sane-backends.....<br>7. edit the lide_60 section of the genesys_devices.c file. You'll see<br>the flags in there.<br>8. run (all on one line):<br> BACKENDS=genesys ./configure --prefix=/usr --sysconfdir=/etc --disable-locking<br>9. make (then wait awhile)<br>10. copy the file backend/.libs/libsane-genesys.so.1.0.22 over top of<br>the copy provided by your distro, not sure where it is on a Mac.<br>You can save the old one before you overwrite it if you want.<br>11. test with scanimage or xsane and various options.<br><br>Only step #10 needs to be done as root.<br><br>Now, those are basically Linux directions, and I'm sure the Mac has<br>lots of differences, others might chime in here :)<br><br>allan<br><br>On Fri, Feb 11, 2011 at 4:12 PM, Ben Green <<a href="mailto:greenb1@mac.com">greenb1@mac.com</a>> wrote:<br><blockquote type="cite">Allan, Thanks very much - Following is a lot of "How to" questions?<br></blockquote><blockquote type="cite">I can't try any of this now as I have to go to work - but I'll try these suggestions later tonight -<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Just to clarify (here's my programming prowess coming to the fore!) -<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">This is all done in terminal (not sane prefs?) --<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">How do I open this file : backend/genesys_devices.c ?<br></blockquote><blockquote type="cite">once i see this file - it might make it all more clear for me..<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">How do I set GENESYS_FLAG_NO_CALIBRATION?<br></blockquote><blockquote type="cite">How do I remove existing flags?<br></blockquote><blockquote type="cite">and how do I rebuild the backend?<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">once this is done, I can scan again from the TWAIN-SANE interface (without calibration)? as this code will affect the actual backend coding is that correct?<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">ALso - if i screw it all up, can i re-insall and start again?<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Thanks a million for your help -- I'm never sure if these things work, but there's only one way to find out ..<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Cheers<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Ben<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">On 11 Feb 2011, at 20:46, m. allan noah wrote:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><blockquote type="cite">I did a bit of digging in the source, and it appears that you could<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">set GENESYS_FLAG_NO_CALIBRATION in the Lide60 entry in<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">backend/genesys_devices.c (along with removing the existing<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">calibration flags), and rebuild sane-backends. That should bypass the<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">calibration code.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">allan<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">On Fri, Feb 11, 2011 at 3:34 PM, m. allan noah <<a href="mailto:kitno455@gmail.com">kitno455@gmail.com</a>> wrote:<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">On Fri, Feb 11, 2011 at 3:18 PM, Ben Green <<a href="mailto:greenb1@mac.com">greenb1@mac.com</a>> wrote:<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">Fair enough Allan, it's not much use just putting out vague questions really<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><snip><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">i'm sure its still possible, i just need to find the way!!<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">You have no clue how to use the command line or write code, yet you<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">are sure this scanner is suitable :)<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">Many scanners do the calibration automatically, and will choke when<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">you gut them like this. Fortunately, the Genesys chips require the<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">software to initialize the calibration, so it should be possible to<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">bypass that. Unfortunately, the data will look bad. You really need to<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">do a scan with the assembled scanner, and cache the calibration<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">values, like genesys backend does for ADF machines. Then you could<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">re-use that calibration data.<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">You might have to hack some code to make these things happen.<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">allan<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">--<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">"The truth is an offense, but not a sin"<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">--<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">"The truth is an offense, but not a sin"<br></blockquote></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><br><br><br>-- <br>"The truth is an offense, but not a sin"<br></div></blockquote></div><br></div></body></html>