As I read, a cpu is not just a cpu, a motherboard is not just a motherboard, a gpu is not just a gpu.... ect ect ect
I don't know what means. Actually a CPU is pretty much just a CPU as is the GPU. They are totally stupid, unable to do anything unless instructed to do something. The motherboard, on the other hand, is much more than just a motherboard. It is an integrated circuit board that also contains the network interface, sound, and often the graphics solution too. It contains it's own mini operating system (the BIOS), I/O and storage (CMOS).
From past experience with The Sims 3 it played beautifully on an Intel P4 2.4GHz single-core, 3.5GB of RAM and a 4850 Radeon over AGP @ 4x
You are trying to compare new apples to pre-historic oranges. P4 single cores and AGP are ancient history - especially AGPx4 and neither should be used to judge how anything will run on modern hardware from either CPU or GPU makers.
P.S. I have about 9yrs of self-taught IT experience, all from solving problems on my own or trial and error.
And that's great, but scares me to death too. Not necessarily you in particular, but all too often I have seen self-taught users, who have no clue and did not take the time to learn about the basics of electronics or the safe handling of electronics doing hardware maintenance. They put themselves or others into situations that is downright dangerous. Too often folks think because they can swap-out RAM, or assemble a few parts in a case to build a computer that suddenly are now "technicians" and computer experts - when they never heard of Ohm's Law, ESD, or understand the fact that anything that plugs into the wall can kill.
"Normal" people would never dream of opening the back of their TVs, monitors, or home theater audio receivers and poke around inside with highly conductive meter probes, but you see the ill-informed doing this, or advising this practice with computers, or worse, power supplies. So for the record, I think it great you are doing your homework by coming to places like Sysnative to research and verify. But I caution to never assume you really know what you are doing without verifying first - if the safety of the equipment, or you, or your data are factors.
For the record, I got into computers professionally when I stood inside one in the mid 70s. It took up the whole floor of an ADC NORAD "blockhouse" and my job was to figure out how to interface my SLFCS (survivable low frequency communications system) radios to it. I say "my" - it was the Air Force's, but they sent me to school on it, put me in charge of it, and I had to train and certify the other radio techs before they could think about touching it. And also for the record, it took me over two years formal classroom, on-the-job, and certification training before I could call myself a technician.
And what has remained constant over the last 40+ years working secure IS/IT hardware support is things change and the more you learn, the more you realize there is MUCH more to learn. And there's always someone nearby who knows a heck of lot more than you do. :grin1: