[sane-devel] Neat NM-1000

2014-01-11 Thread Torfinn Ingolfsen
On Sat, Jan 11, 2014 at 4:23 AM, Kentrell Johnson
 wrote:
>
> Would it be possible to determine the chipset from taking it apart and
> examining the internals?  There seem to be no accessible screws on the
> device, so I am not sure I can open it without breaking it (but am
> willing to do that as a last resort).

This should be your last resort; if you are unlucky chips are unmarked
or just one big ASIC.

> Is reverse engineering the Windows or Mac drivers a possibility for
> determining the chipset?  Maybe running them through 'strings' would be
> revealing?

You won't know until you try it. :)
Sometimes, the *.inf files provided with Windows drivers has clues
about chipsets and so on.
Worth a look (.inf files are text files)

HTH
-- 
Regards,
Torfinn Ingolfsen



[sane-devel] Brother DCP315CN scanner

2014-01-11 Thread ttz642
Had this printer / scanner working pre ubuntu 13.10, doesn't work with 
13.10 :-(

Link to brscan2 source code:

  * 
http://www.brother.com/cgi-bin/agreement/agreement.cgi?dlfile=http://www.brother.com/pub/bsc/linux/dlf/brscan2-src-0.2.5-1.tar.gz&lang=English_source

I tried configuring and building but it is old and many of the required 
packages aren't available. The source needs updating.


Other source files:

  * 
http://welcome.solutions.brother.com/bsc/public_s/id/linux/en/download_src.html

-- next part --
An HTML attachment was scrubbed...
URL: 
<http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20140111/350023eb/attachment.html>


[sane-devel] Neat NM-1000

2014-01-11 Thread Kentrell Johnson
Hello,

I have a Neat NM-1000 scanner that I would like to try to get working
with SANE.  Someone previously tried to get it working, but ultimately
could not determine which chipset it uses:

  http://lists.alioth.debian.org/pipermail/sane-devel/2011-June/028637.html

The chipset is still not detected with the latest SANE backends
(1.0.24).  'sane-find-scanner -v -v' reports:

  

The e-mail linked above suggested using usbsnoop on Windows to capture a
log, from which it might be possible to determine the chipset.  I
installed usbsnoop from http://sourceforge.net/projects/usbsnoop/, but
it does not seem to be functional in Windows 7.  Is there another USB
sniffer that might capture the relevant information?

Would it be possible to determine the chipset from taking it apart and
examining the internals?  There seem to be no accessible screws on the
device, so I am not sure I can open it without breaking it (but am
willing to do that as a last resort).

Is reverse engineering the Windows or Mac drivers a possibility for
determining the chipset?  Maybe running them through 'strings' would be
revealing?

Thanks,
Kentrell