Ted Mittelstaedt writes:
The main point I've been trying to make is that just because FreeBSD's drivers don't support whatever modification has been made in the Adaptec code on the Vectra, does not mean that the FreeBSD driver is "broken" or "has a bug" in it.
When something doesn't work, it's broken.
I disagree - If FBSD does not (or did not) know of the HP/Compaq tweakes in the microcode, how can you claim it's broken?
If MS does not support or have a driver for so-and-so app or hardware, does it also mean Windows is broken?
According to you, it is. According to the vast majority, it's not broken, it's merely unsupported.
You could say the same about your hardware based on what you just said, if FBSD does not have the teaks to the driver version you need, then (as you think) your hardware is broken.
As you stated, you can't have it both ways.
Why not just agree that both FBSD AND your hardware are broken? Oh - I know, it worked for 8 years...
Read above to if MS don't support or have a driver for x, y, and z - then as you say, Windows is broken.
Can't have it both ways mate.
Know the difference.
-- Best regards, Chris
The time it takes to rectify a situation is inversely proportional to the time it took to do the damage. _______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
