> I see...So we should only tell people that's stuff broken? i.e. if it works
> fine for 80% of the people out there, but no one replys that it works and
> people only see "it's broke" mail, then it really doesn't matter how
> many people it works for since all they see is failures.....

You have a valid point, and I'm definitely not saying that you
shouldn't have spoken up - I'm just saying that your success does not
guarantee another's success.   Really, what we both should have done
would have been to say exactly what hardware was working (or in my
case not working) for us.   Chances are that if you have an AHA-2940
and a SCHMOE-1014 drive running on a 133MHz Pentium on an ASUS
motherboard, and they're working fine, then if another person tries
the exact same configuration, they should win too.

> I'm sorry, but I don't agree with this. The converse could also be true
> as well here, you're unlucky with the particular set of hardware you've got,
> and my otherwise normal setup (by far the most common I've seen) does just
> fine. People need to, and if they're in the position of buying hardware
> need to hear both sides of this issue.

People need real information that they can use to avoid losing.   If
we were all Marketroids here, sure, we'd want to say only good things
about the product.   But we're not marketroids, and we're not trying
to sell product - we're trying to help people to succeed using the
product.   Honesty is the best policy.

> Since your description (locks up solid) wasn't real specific, is this
> the running out of SCB's bug? If so, that doesn't even directly relate
> to the ahc driver itself and is more of a MI scsi problem.

It's been several months since I took out the AHA-2940 controller, and
I don't remember the exact message, but my recollection is that it was
a timeout talking to the controller, not a bug running out of SCBs
(unless that manifests itself as a timeout).

			       _MelloN_