Problems with SATALink 3512

We have been standardizing on the SATALink 3512 host adapters under Windows
2000 and 2003 and I'm seeing really frustrating inconsistencies in its
behavior. Occasionally we will plug in a single external SATA drive and
nothing shows as mounted on the OS desktop. You go to disconnect the
drive, and now you suddenly get a drive unsafely disconnected dialog. So
it appears that at some level the device driver is alive and working, but it
just cannot complete its mounting sequence to present a working device with
a mounted drive letter. The same drive on a different system comes up
right away.

We then try a different style of eSATA enclosure on the "not working" SATA
adapter, and that drive works. So there is some kind of complex
interaction between the enclosure and the adapter that we cannot understand.

The bottom line of all of this is it is making SATA extremely time consuming
to work with. We end up having to mount many different drives in different
enclosures to finally find one that just works. Is this likely a
problem with the driver, or the design of the hardware?

Is there some known single (preferably dual) external ESATA host adapter for
Windows that is 100% rock solid with many different types of drive
enclosures? I need JBOD not RAID just to work on individual drive
platters and transfer data around between machines.

--
Will