It is so obvious a possible solution that we do not think of it most of the
time until someone else suggests it. It also is counter to the way that we
expect SCSI devices to work in such a basic way that we do not think of it
or expect that if there is a bug in the SCSI setup it will be of a
completely different nature and of a more complex sort. :-)
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Clark Guy
Sent: Wednesday, December 13, 2000 7:20 AM
To: [EMAIL PROTECTED]
Subject: RE: filmscanners: Re: Umax scanners
HI, Laurie, et al!
I tried swapping the SCSI IDs of the two scanners, and sure enough,
everything works properly now!!!! (I thought I'd tried everything else, why
didn't I try this before? !)
Thanx for the tip!!!!!
Guy Clark
<<<<<<<<<<<<<<<<<>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Oh, HO!!
Thanx, Laurie!
I think that my Umax is scsi 6 and my Minolta is scsi5. I'll have to try
that!!
Thanx again!
Guy Clark
-----Original Message-----
From: Laurie Solomon [mailto:[EMAIL PROTECTED]]
Sent: Monday, December 11, 2000 12:57 PM
To: [EMAIL PROTECTED]
Subject: RE: filmscanners: Re: Umax scanners
>For some reason, the TWAIN drivers for the two machines don't coexist well,
>and I could only use one by turning off the other one and rebooting.
I found this to be the case with my Umax SCSI flatbed and Minolta SCSI Scan
Multi until someone on one of the lists suggested that it might have
something to do with the order in which the devices were connected to the
SCSI card and the order in which SCSI ID# were assigned to the devices. I
changed the order and, lo & behold, both devices would install at the same
and remain available for use without rebooting with each switch.
Apparently, there is a flaw or bug in the Umax SCSI twain driver that
requires it to be loaded first before another SCSI scanner and assigned an
SCSI ID# lower than any other SCSI scanner; otherwise it will not install
while the other scanner is installed.
