What really bugged me about VIA was that they couldn't write Win2K mobo drivers to save their life. I had a system that had severe stability issues because it had a Matrox AGP video card that also used main system RAM. Win2K was a company requirement. That particular Matrox card was a software requirement (at the time at least), as was running it in a mode that used system memory. So I couldn't do anything to fix the frequent lock ups.
Yet VIA kept claiming that it wasn't their fault, and at the same time, (supposedly) ASUS customer service kept telling my OEM that each of VIA's latest driver revisions would actually fix the problem. (At least, that's what the local OEM relayed to me from them.) Yet it still took four months to actually <i>fix</i> the drivers.
Normally I wouldn't have even put up with that crap, but at the time software development was under an extreme rush at work, and I couldn't afford a week of downtime to ship the system back and have the mobo replaced. That and the company wouldn't let me replace it myself because that would void the waranty.
Damn rocks and hard places.
I'm sure that it was the Win2K drivers though, because it was one of the many VIA driver revisions that finally fixed the problem.
My experience has been that VIA and Matrox both just royally suck at firmware development. I try to avoid them as much as humanly possible now. Not because I don't believe that their new products are better, but simply because there are plenty more fish in the sea to it not crimp my options any to boycott them for their past stupidity.
So I'm with you Crashman. VIA can go suck a lemon for all I care.
Tech support said take a screen shot.
Putting it down with my .22 was the humane thing to do.