when i laughed and said 'i rest my case' it was because you were naming things wrong. You didn't even know what it was called. it is obvious, to anyone who knows the proper names for these things, that i understood very well what you were referring to (when saying 'bit rate'). Since you did not understand why i was laughing, you thought i was implying that " 'bitrate' is not important". Completely wrong.
well... yeah. if you want to appear knowledgeable and be understood, you need to use the proper words for things. otherwise, all goes to hell. what you are writing is not read only by me. i know the difference between these two and i don't care if you call it whatever you want to call it. but, as i said, what you write is not read only by me, it is read also by the OP who is not as knowledgeable and wants some advice. Do you now understand the importance of calling things by their proper name?
dadge, it is "bus width" not "bit rate". Those two are not really related.
bit rate is measured in amount of data per unit of time. Kbps, Mbps, etc.
the memory bus width for data is not "bit rate".
besides, knowing the bus width is only half the story. how many data transfers are done per clock? 1? 2? 4? a quadpumped 128bit-wide beats a singlepumped 256bit one if you consider same clocking.
as for cock slamming, is that when you take your favourite rooster and bang it against a door or something?
you learn more online but you don't learn the same things.
You won't be given the chance to learn good car control when racing online and i am pretty certain most would not consider it really nice to have someone toy around with the controls while the rest want to race.
think of it as something that teaches you the very very basic ablities one needs to start going round a circuit. for you who can race easily it might not seem important but for someone who just now starts with lfs (not talking about the OP, necessarily) they are great help.
well, then, why do you characterize the 6200 as running lfs 'crap' ? i am more than certain it can run at 1024x768 without effects and medium detail. is that 'crap' ?
for the most part i agree with SRC, i have a question though.
you said that specs are there to advertise stuff (generaly).
what do you think about those few who know what specs to look for and what would make a difference? For example, consider that we have two cards with same core and similar frequencies. One is 512MB gddr2 the other is 256MB gddr3. Can you not say which one is faster?
i think one of you is content with his graphics card being enough to run the game at 1024x768 and medium detail while others don't consider the graphics card to be any good unless it can get triple digit fps at 1920x1200 with 8xAA and 16xAF.
if you actually have the specs (clocks, stream processors, bus width, memory type and clocks, some examples off the top of my head) and not just a bunch of not really significant numbers (memory size) the you can generally (not always) compare cards
in the end, a benchmark is what you need tho, yeah.
what all these techniques try to achieve is make photographs of subjects, like one would see with his own eyes. Eyes are much much more capable at extreme brightness deviation. Cameras, not so much.
and what will you get? I mean, for the money that you will give him?
how about... instead of giving money to overclock an already fast enough cpu... you use the extra money to get a faster graphics card, which is just what your machine needs...
he suggested overclocking an already very fast processor, way faster than what is needed for LFS, even at high graphical settings (Where the problem is the gpu, not the cpu anyway).
It is completely pointless.
plus, the 3.2 p4 is not faster than a 2.4 core2. even the 3.6GHz Extreme Editio ... the 1.8GHz, 'slow' core2, in every game. let's not talk about a simple 3.2 p4 being faster than a 2.4Ghz Q6600... that is ridiculous... the q6600 is about twice as fast as the 3.6GHz EE p4...