All of this could be avoided if people would just stop using
the wrong terms (which is why standard terminology exists).
There is no DDR2 800.
I know what he means, looks standard to me. But
what does YOU mean?!!
Do you mean the terminology is wrong? It looks clear to me.
DDR2 RAM, with an effective speed of 800. Actual speed of 200. (or
rather. Supporting those/that speed i.e. that is the max speed of
memory bus that it has been tested to run stably on. that's the stock
speed)
I've seen that in a motherboard manual I read a few hours ago (to look
at the BIOS of some different motherboards out there at the moment.).
Since I don't get to play with the latest stuff and see the BIOS for
myself.. It said DDR2-800
And you can buy 512MB DDR2-800 e.t.c.
so it's specific. even specific enough for a motherboard manual.
If you're saying that the terminology is ok but they don't sell it,
then that's not true.. 'cos the motherboard manual said it, and it's
on ebay.
I think what you're saying, you also said in a related post..
thread: what is PC2 DDR ?
ng: alt.comp.hardware
date: june
link:
http://groups.google.com/group/alt....+jameshanley39+&rnum=1&hl=en#6ea91d043ad6765c
I didn't understand you at the time.. but I think I do now..
I notice that the jedec document doesn't disagree with you.
It says DDR2 and it says PC2-xxxx But it doesn't say DDR2 800 e.t.c.
Are you saying it's not "legally" ok to say DDR 400 ? (we know what it
means. 200Mhz. DDR 400(200Mhz*2) )
put mhz after actual speed.. not after effective speed..
The PC notation lets one specify bandwidth..
But what if I want to specify the speed of memory bus supported by the
RAM?
I can't say DDR2 800 ?
All over the internet people say it and people know what they mean.
What should they say?
It's useful to have a notation for actual speed, effective speed,
bandwidth.
Not just for bandwidth! PC-xxxx or PC2-xxxx !
There is DDR2 PC(nnnn) memory, and there is a MHz clock rate
for the memory bus which is effectively (but not actually) a
2 x multiplier merely because double data rate transfers
twice per clock rate.
holy mackeral
using the term multiplier that way. Defining effective speed that way,
is just blurring concepts into smitherines. It's unbelievably
misleading.
A multiplier is an electronic thing for deriving one clock speed from
another.
The term effective speed with the memory bus, refers to a concept
called dual pumping or quad pumping. Putting more bits on the memory
bus in a clock cycle. When the term effective speed is used rather
than actual speed. It's not called 'effective' because effective
multiplier like you suggest. Fortunately nobody before you ever put
such misleading terminology in an explanation! The actual bus runs at
its speed, and the dual pumping or quad pumping of the bus gives an
effective speed. It's about putting more bits on the bus in a clock
cycle. Nothing to do with how a multiplier works.
Nobody means that when they speak of a memory multiplier.
si sandra misleadingly referred to a multiplier, at least it meant it,
as a multiplier does. i.e. it referred to the memory speed being a
multiple of the FSB. Nothing whatsoever to do with what you
suggest. . But if there was a multiplier, then it would be as si
sandra suggested. My RAM at 133 would've been FSB x 4/3. At least
their use of the term multiplier would've beent true if there was a
multiplier!
And when one of the first people to reply mentioned " multiplier "..
He wrote of not needing to multiply.. There was absolutely no way
that he shared your particular virtual meaning of memory
multiplier. .. Let's pretend that what he meant as consistent with
your meaning. Then look how ridiculous it gets. He wrote of not
needing to multiply. There is absolutely no way that he meant that the
DDR2 RAM with an effective speed of 800(200*4), would run at 200 -
that the effective speed would be dropped. He didn't mean un quad
pumping the memory bus.. Or un dual pumping it. It's not even possible
to do that anyway. And nobody would want to.
Whenever someone uses a wrong term like DDR2 800 we are left
to guess what it really means.
no guess work at all. DDR2 800 is a specific thing. The expression is
self-contained. There's no hole in it.
You want to know what chipset he has, that's an issue with the
motherboard. Not an issue with how he described his RAM.
I don't like the style of saying "you give me all the information, and
i'll figure it out".
I see it in networking newsgroups all the time.. People ask the OP
"how much do you want to spend".
It's better to say
"this is available in this price range, this is available in that
price range, e.t.c."
There's no point hiding the knowledge behind your analysis.
So, if things are different for different chipsets.. If I knew the
differences, I would write them out!
It's not wasted. It's archived, one can refer others to them.
It's better for the archives if information is organised. And threads
don't e.g. just turn into only being relevant for one particular model
of motherboard. or one chipset. Information should be complete.
Unfortunately the OP didn't provide full details in the
post, describing only a "MB" not anything specific.
he wasn't asking about particular MBs. He was asking a general
question about the RAM.
If I knew, and believed the answer depends,, then i'd tell him how it
depends. e.g. if his motherboard is of this chipset then x. If it has
tihs chipset then y.. There may be 6 different chipsets.
If he was really bad and didn't know what chipset he had, i'd tell him
how to find out given his motherboard (google!).
I'd do that rather than ask which motherboard he has.. Asking him like
that would be doing the analysis and hiding it, and just giving him
the answer.
It means the thread is only useful for that one motherboard. It means
if he wanted to buy another motherboard, he wouldn't know any
better.. It's just not techie friendly. That requirements analysis is
ok for a 90 year old end user, or maybe even any end user, if you're
feeling ungenerous . But I wouldn't ever do that in a techie
newsgroup. I think one should treat a techie how a techie would want
to be treated. He wants to expand his knowledge. Know how to solve
similar problems. Not just knowing the answer for one specific one.
And people searching the archives aren't going to get much out of a
thread that only addresses one particular motherboard.
I'm not saying i can do better. I lack the knowledge. I don't see that
many computers every day. Just my own old ones. I'm talking style of
answer here though.