Originally posted by: oldfart
I have never had a system that was problem free for very long
Really? I've had lots of them. My current (and overclocked) system has been 100% problem free since I put it together 8 months ago. The only time I've opened the case is to replace a GF3 with a GF4.
If it wasn't clear in the original, these sentences go together:
"
I have never had a system that was problem free for very long. Just keep adding and changing things, and at least every couple of changes will bring an unforseen difficulty (which I generally solve).
"
My normal mode of thought is "What else can I do with my computer? What have I never tried? Can I make two unusual things work together at the same time." My idea of changing something is not just going from MediaPlayer 6 to MediaPlayer7.1, although even that can bring screwy surprises.
If I leave it alone, everything works fine. Certainly everything is stabile. When you change things...
But you are right. If you want a sure thing, VIA or Intel, make the system identical -and I mean identical- to a known good one. Don't "tweak" it, don't "upgrade" a part. Then don't change anything. This may be where people get the idea that VIA chipsets are a PITA. People who never change their system read about somebody else changing something and having a problem. They imagine that if they themselves changed something, it would go fine. Wrong. I mean, sometimes it does, and sometimes it doesn't. Why does VIA get the bad rap? VIA people like to mess with their computers. Intel people sit aroound all day long, sip wine, savor croissants, and recite Zen poems. They don't want to foul themselves on computer stuff. Orr is it he MAC people? Whatever,
Sometimes changes go OK. I went from a Geforce2 MX to a Geforce2 Pro with not a wimper. I didn't even change drivers. It worked in both 98 and XP.
Other times ...
When I installed Netmeeting 3, so I could use a remote desktop, I couldn't get games to operate full screen. (This is when I am NOT using the remote desktop.) I didn't know Netmeeting was the cause. It seemed to be a video problem. I thought it had something to do with the video driver or the games or DirectX or... g*d knows. I didn't associate the two things because I don't play games very often or use the network very often. It took me a long time to figure that one out. I suppose I could have cursed VIA for their problematic chipset. Only thing was, a computer on the network, the one I wanted to run remotely, had exactly the same no-full-sceen problem, and it had an Intel 810e chipset. I had to mention this because otherwise the Intel people would put this on their list of VIA bugs. They are probably adding it anyway.
I wasn't exagerating when I said I could go on for hour after boring hour listing problems of this type that I have worked through. If you don't try different combos of things, you will never know about them. This one was simple to explain.
This is just normal for anybody who is around a variety of computers. I'm nowhere close to being an extreme techy.
Anybody ever have a keyboard -a normal keyboard- that will not work with one computer, allthough the keyboard has worked with many over the years, and still works with 3 other computers? I have. Any other keyboard works.
Anybody ever have a nice video board conk out that has worked for years; won't boot in 3 computers, but works flawlessly, in full 3D railgun-pellet-flying glory on a fourth? I have.
Do you have two versions of Linux, three versions of XP and two versions of W98 on your computer? Do you have three other computers in the basement with likewise oddball setups?
The more changes you make, the more problems you run into, the more problems you know of. This idea of a problem-free computer is delusion brought about by an extreme low familiarity with a variety of hardware.
Don't get me wrong. If Intel put out a chipset for Athlons -which we all know is exactly contrary to Intel's goal of killing AMD- I'd consider it. Not because I have had less problems with Intel in practice. It just is easier to go with the flow, which is Intel. Intel has something like 4 times the users out there. That means 4 times as many people with the same problems as you that you can go to for help. Four times as many people working on the same problem. Maybe fifty times as much time that manufacturers put into making a given product compatible.
Let us refresh our memories. AMD processors used to plug into Intel motherboards. In that era, Intel arranged their legalistics to alllow general use. It worked well for them and they prospered, growing into the phenominal giant we know from an obscure controller chip maker. In that era Intel created the PCI bus, which is really the Pentium bus. Partly because of Intel's policy, PCI rapidly superceded the previous standard bus, VESA local buss. Then Intel decided to kill off AMD, its cross-liicense partner since the 8080 days. In order to do that, the marketing department created a new processor interface (slot 1) and arranged the legalistics to be totally exclusive to Intel. Analysts have claimed it to be technically inferior to what had gone before in every way. AMD's stategy was to shadow Intel by using the same connectors and other parts as Intel, although employing a different processor bus licensed from DEC. Shadowing Intel this way meant that mobos could be nearly the same for AMD processors as for the Intel versions and had nearly the same cost of production. Licensing a pre-existing buss from DEC meant Intel could have no legal grounds to stop AMD. Getting the glue chips, the chipset, to interface the mobo to the processor was a problem. Intel sure wasn't going to do it! The whole point of this maneuver was to bump off AMD. So that is why we are left with non-Intel chipsets for AMD processors.
PCI, from the point of view of Intel's maketing department, is a failure. It allows AMD processors to work with cards designed for Intel equipment. A minor bright spot is there are some proprietary things about Intel's own PCI version that it can still withhold. Its not much, because manufacturers have gotten around it.