>WTH is wrong with you?
WTH is wrong with me? This is a standard set by others, not a standard I adhere to. By the standard set to judge VIA, nForce2 sucks. No doubt the nForce2 will settle down in a few months (3 to 6) as they keep working on it. Typically for mobos, by the time they get it good, people talk it down on the forums because it is dated and they think there is another product over the horizon just about to kill it off.
This is a "near-release" mobo. Judging by the way info and ads were popping up in the last few days, nForce2 boards are immanent. I don't believe Leadtek should have any more trouble implementing the reference design than other mobo makers. Why do you suppose the nForce boards have a chip turned 45 degrees? Nvidia's reference circuit board traces have it that way. So the Leadtek board is probably like other nForce boards. As you may recall, according to the news, ALL nForce boards were postponed a while ago due to some problem in getting AMD's validation. That shows you how alike all the nForce boards are.
If you have seen the previous articles on nForce2, you recall that it is mostly a facelift for higher speed, and is nearly identical to nForce, and as such it is a design that has been around a long time, not really new. The big difference is the predictor for the memory controllers.
This reviewer did something unusual. He checked to see if the mobo worked with a few different things. L*rd knows why. But he did. What happened is just exactly what happens when you try different combos of hardware together: Some of them have "issues", some don't.
He ran "SpecView". If he hadn't he would never have known it would crash. This is exactly what happens when you run hardware, especially AGP video, with different combos of software. You get "issues." Nvidia has a beta out that fixes it. Probably SpecView is one of the issues Nvidia found out about.
What happens is the big video card makers tune their drivers to detect certain programs (like Quake3) so they will run faster. Years ago, the reviewers figured this out and began to find ways to get around it, so the manufacturers have to do it differently than they used to. The name Quake3 can't show up in the driver for instance. That's fine. But then some other program might have an unforseen issue because of the tuning or the detection. BTW, drivers are programs. So you can develop an interaction issue with a sound card driver, a USB driver, a bridge driver, or whatever. (The reviewer used a SB Live 5.1)
To give an idea how a driver MIGHT develop an issue: Suppose investigation shows that game One frequently does some things that never result in something different shown on the screen. A programmer develops a work-around so the video chip never has to process any of this, resulting in a faster game. The driver has a detection for this games behavior. Game Two does something similar but it would result in something different shown on the screen. So now Game two has an issue.
I have nothing against nForce. I built an nForce board, a cheapo ASUS AN266-VM. I was delighted at how nice this mobo was considering the price. I couldn't make it crash by stressing it, but then if I could have, it would have been a worthless POS. Inexplicably, no one but ASUS makes a mobo like this one (nForce 220), at least not one you can find. But I accidently ran into an issue. One keyboard that won't work with it. The keyboard is my ol' reliable, that has always worked before and still works with 4 other computers (I checked). Unlike every other component, I have never had an issue with a keyboard before.