Microtek ScanMaker 8700
Biggest chip, I guess this is the one. It is square (about 1" 1/16" or about 27 mm) with a huge number of legs on each side: M012 541-30-510012 0032PU005 I am not sure if it is a "O" as in oscar or a "0" as in "zero". "510012" might be 51 week of december 2000, but I am not sure. === This IC looks like an eprom or some kind of programable ic, but it does not appear to have a window on it. The values are printed on two papers stickers. One of them has a code bar. This ic, is on a socket, similar in size and shape to the one of the BIOS of older AT motherboards. It is about 41 mm long. or about 1" 1/8". It seems to have 16 legs on each side. 200011255 ARB149911 SM8700 === They are others integrated circuits. Some are for the "firwire 1394" or USB interface, the stepper motors control, etc.
Is reported to be the same scanner as Agfa DuoScan f40, but has different USb ids.
<device descriptor of 0x05da/0x20b1 at 001:002> bLength 18 bDescriptorType 1 bcdUSB 1.00 bDeviceClass 255 bDeviceSubClass 3 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x05DA idProduct 0x20B1 bcdDevice 0.00 iManufacturer 0 () iProduct 0 () iSerialNumber 0 () bNumConfigurations 1 <configuration 0> bLength 9 bDescriptorType 2 wTotalLength 32 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 () bmAttributes 64 (Self-powered) MaxPower 0 mA <interface 0> <altsetting 0> bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 0 bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 () <endpoint 0> bLength 7 bDescriptorType 5 bEndpointAddress 0x81 (in 0x01) bmAttributes 2 (bulk) wMaxPacketSize 64 bInterval 0 ms bRefresh 0 bSynchAddress 0 <endpoint 1> bLength 7 bDescriptorType 5 bEndpointAddress 0x02 (out 0x02) bmAttributes 2 (bulk) wMaxPacketSize 8 bInterval 0 ms bRefresh 0 bSynchAddress 0 <trying to find out which USB chip is used> checking for GT-6801 ... this is not a GT-6801 (bcdUSB = 0x100) checking for GT-6816 ... this is not a GT-6816 (bDeviceClass = 255, bInterfaceClass = 0) checking for GT-8911 ... this is not a GT-8911 (check 1, bDeviceClass = 255, bInterfaceClass = 0) checking for MA-1017 ... this is not a MA-1017 (bDeviceClass = 255, bInterfaceClass = 0) checking for MA-1015 ... this is not a MA-1015 (bDeviceSubClass = 0x3) checking for MA-1509 ... this is not a MA-1509 (bcdUSB = 0x100) checking for LM983[1,2,3] ... this is not a LM983x (bDeviceClass = 255, bInterfaceClass = 0) checking for GL646 ... this is not a GL646 (bDeviceClass = 255, bInterfaceClass = 0) checking for GL646_HP ... this is not a GL646_HP (bDeviceClass = 255, bInterfaceClass = 0) checking for GL660+GL646 ... this is not a GL660+GL646 (bcdUSB = 0x100) checking for GL841 ... this is not a GL841 (bDeviceClass = 255, bInterfaceClass = 0) checking for ICM532B ... this is not a ICM532B (check 1, bDeviceClass = 255, bInterfaceClass = 0) <Couldn't determine the type of the USB chip> found USB scanner (vendor=0x05da, product=0x20b1) at libusb:001:002
If anything is wrong or missing on this page please file a bug report or use the the form for adding an unsupported device.
If you own an unsupported scanner, please send as much information as possible. Especially the output of sane-find-scanner -v -v and/or cat /proc/scsi/scsi (for SCSI scanners) or cat /proc/bus/usb/devices (for USB scanners) can help. If you dare to open the scanner, have a look at the text that's printed on the chips. That may help to identify the chipset. If you know that the scanner is similar to another one (e.g. supported by the same Windows driver), please also mention this fact.
Are you a manufacturer or vendor of scanners and one of your scanners is not supported by SANE yet? In this case please have a look at our information for manufacturers.