Yours line doesn't even make sense.
No sh!t Sherlock, and that would be because it happens to follow the same format of your statement.
For the last time (I've tried to help you here, but you just don't want to be helped),
Take your "help" and stick it where the sun don't shine. I certainly didn't ask for your "help" and neither did this thread, yet you still can't keep away for some reason.
if nVIdia's drivers caused your problems then everyone with an nforce3 and an nv40 would have suffered crashes and instability like you.
This is beyond a joke now. Are you really this dense when it comes to rational reasoning or do you just enjoy blatantly trolling?
If NF3 was the problem then all NF3 owners - regardless of what true AGP GPU they used - would've suffered crashes and instabillity.
That didn't happen.
We know this because
my own board which you claim was faulty
did not have an issue with ATi cards, cards which
fully supported the AGP spec and all associated features.
Not only that, but the problem would not be limited to nForce3 but affect all AGP owners regardless of chipset.
It could well have been but I didn't really pay attention to other motherboard chipsets at the time. In any case we certainly know DEP was an issue on non-NF3 platforms. Oh wait, that's a Microsoft problem, right? :roll:
Just like the dual core driver issues that are stated in nVidia's driver readme. You can't blame NF3 on those so who are you going to blame there? Microsoft again? Or perhaps Intel/AMD?
nV40 works perfectly in everything but nForce3,
Not for DEP it didn't. At least not until they fixed the problem six months after introducing it.
and not all nForce3 owners experience your troubles.
So?
Either RMA the board or replace it with a one utilizing a different chipset.
How exactly do you expect I'm running PCIe video cards in an AGP NF3 board, Sherlock?
If you don't want to do that, the solution most affected people use to alleviate the problem is disable AGP FW and revert to AGP 4x.
You think I didn't try this, among many other things? The only real solution was to install a Radeon in there and then it worked perfectly, aside from the few driver versions that had known issues with CoD and CFS3 which were later fixed.
There's nothing faulty about NF3, it's nVidia's drivers, no doubt left-over crap from the FX days when they busted their balls to raise performance at any cost.
Was in response to your taking "nVidia on the other hand made full use of the interface and is/was far more sensitive to any shortcomings chipset wise or driver wise that may be present. " out of context and launching into an unrelated optimization rant (talk about people going off on a tangent...)
There's nothing unrelated about it. You don't introduce those kinds of problems unless you're desperately trying to make up for something else (such as performance).
But then I'd wager you've already rewritten history to state that the FX line never had problems with shaders at all, it was just a giant conspiracy theory. Hence I expect my comments are lost on you.
I can assure you that back in the TNT/GF1/2 days, nVidia driver optimizations had nothing whatsoever to do with AGP compatability problems,
Sure but then I can also assure you that other genuine AGP cards like the Radeon would've also
had problems with faulty AGP boards,
unlike the NF3 situation here.
Now quit trying to blame nV40 and its drivers for what is an nForce3 problem!
It's not an NF3 problem because ATi's fully AGP implemented drivers work fine on the platform. SmartGART didn't even deem it necessary to disable problematic features like Fast Writes because it felt the board was stable enough to use them. And it was.
If you want my honest opinion, get rid of the nForce3 - it is easily the worst motherboard platform nVidia has ever produced, even VIA managed to do better.
Perhaps it was the worst but it doesn't change the fact that only the 6800U was unstable with it but two different Radeon cards - both of which fully supported AGP features - were not.
Facebook
Twitter