Tony Curtis wrote:

>> My understanding is that something in the
>> device-type-config-list will bind if it's of the correct
>> type - i.e. *any* scanner if one sets:

>> device-type-config-list = "scanner";

>> whereas any device made by umax on SCSI ID 4 would bind
>> with:

>> inquiry-config-list = "umax", "*"; name="sgen" class="scsi"
>> target=4 lun=0;

>Hummm, 'twas but a guess.

>The only other experience I have to contribute is getting the
>SCSI id wrong. That tends to prevent things working :-)

I don't think its the SCSI ID, since I did at one point uncomment all
the SCSI id's, so it should have bound to a scanner on any of them.

I did finally 'solve' it. When I re-read the instructions from Jorg
Schilling's libscg driver, I realised I had installed in incorrectly -
I had only installed a 64-bit driver, not a 32-bit one too. (I
originally done it years ago, so forgot the details). When I followed
the instructions carefully, his libscg driver worked and now my
scanner is working once again.

So whilst Sun's driver won't access the scanner, libscg will.

PS. Sorry for not posting in the usual way, so the thread follows. I
am posting from Google to hide my email address, but it takes several
hours between posting a message and it appearing on Google Groups.
However, I can read the posts instantly via my ISP's news server.
Hence I tend to post with one method and read with another.

Dr. David Kirkby.