The following text was written by Jeff Muhlbock and sent to me by mail. Maybe it's useful for someone. I've recently decided to setup my scanner, a UMAX S-6E, up under Linux, and my second setup was to see if I could get the crappy OEM SCSI card to work. (The first step was to see if SANE supported the scanner). Anyway, it was labeled a UDS-IS11 on a sticker on the card, but printed on the board itself (both sides), it said a DTC-3181A. I ran a number of searches on google, and to my dismay, all I could find was poor reports on the DTC-3181Es and only one or two references to the DTC-3181A...all bad. It seemed that nobody had the card model that I had, and UMAX never bothered to change the UDS number as the card was upgraded, so much of what I found that way didn't apply. Finally I came across your page, and your link to the Mustek SCSI card page, and to my surprise, I actually found a picture of my card, minus the UDS label! I was overjoyed. So I tried the g_NCR5380 driver with a 2.4 kernel, and besides a few scsi0: weirdness errors, everything seems to work. So, here is a bit of information that I thought you and the Mustek scanner users may find useful: The DTC-3181A uses the DTCT-436 chip (notice no letter after 436). It is not a plug and play chip in disguise, or if it is, it is well hidden. It does have jumper locations on the board to set the base address, IRQ, and wait-state, but with the exception of the wait-state, they do not have pins, but are just solder locations and are all open. According to the Windows drivers, the base address in this configuration is set in software, although I don't know how. I just found that the base address is 0x2C0 on mine. And in this configuration, no IRQ is used. However, since there are jumper locations for an IRQ, I just might try soldering them together to see what happens... I got it to run using the g_NCR5380 driver, following the DTC-3181E instructions. It's slow...much slower than under Windows, mostly due to backtracking and because there is no IRQ. The system becomes almost completely unresponsive. I've also found that changing buffer sizes and USLEEP delays doesn't really make any difference...but that could be the UMAX scanner rather than the card. Finally, I tried hacking the g_NCR5380 driver a bit to get rid of the "weirdness" error. I found that it occurs during a device selection, and that if I called the function again from within itself (instead of returning an error), the second call would succeed. I don't know if this is making a difference at all or not, but I've left it for now. I hope that someone finds this information useful. Jeff