🚀 go-pugleaf

>If the memory speeds are different (70ns and 80ns, for example), then 
>you're asking for trouble.  Get the manual for the motherboard and 
>install the speed memory that it specifies.  Mixing speeds leads to 
>memory parity errors, which leads to all sorts of wierd things 
>(spontaneous reboots and hangs, for example). 

Excuse me, but this is nonsense.

Memory "speed" is not that at all. It is instead 
	The _maximum_ time required until data output is
	stable and valid, after an address change.

In other words:
	CPU places an address 0FE80786 on the address bus.
	x amount of time passes (say 80 ns)
	The output of that chip for that address is known to be valid.

(Yes, I left out lots of other factors such as decode time, etc, etc.
-- In this discussion they will just obscure the issue...)

Now, there is nothing that says the data can not be there BEFORE then,
say 79 ns. Nor is there any reason that you cannot go back & read the
data later, say 85, or 100 ns. The spec is the maximum; many will do
better.

In fact, the manufacturer selects out the faster chips & sells them as
such, so there will not be a large number of 70 ns one in 100 ns
packages. But that is because they can get you to pay more for them...

So long as ALL chips are at LEAST fast enough, you will be ok.
-- 
A host is a host from coast to coast.................wb8foz@nrk.com
& no one will talk to a host that's close...........(v)301 56 LINUX
Unless the host (that isn't close)....kibo# 777............pob 1433
is busy, hung or dead..............vr....................20915-1433