🚀 go-pugleaf

In article <4kq5f0$ehl@usenet6.interramp.com>,
ir003870@interramp.com (Billy Ko) says:

>The recommended thing to do is put the SLOWEST memory in the first bank!  The 
>reason is this: the fast chip can always slow down to the speed of the slow 
>chip, but the slow chip can't keep up with the fast one.

*sigh*

Where do people *get* this bullsh*t?

>BTW - when marching, the military always puts the smallest guys in front, so 
>that the big guys won't run away from the small ones.  Same reasoning.  Slow 
>in front, fast in back, and for much the same reason.

So?

>I got this info from page 804, Inside OS/2 Warp

I don't believe it.

I've worked with MBs where the *largest* bank of memory had to be bank 0, (due
to refresh issues) but that has nothing to do with speed. I've mixed speeds
between banks all the time.

A MOTHERBOARD CANNOT GUESS THE SPEED OF A BANK OF MEMORY! It will *not*
know until you program it to CMOS. Set the speed in non-EDO systems to that
of the slowest memory *in any bank*, and it will all behave fine!

	-Kenny

-- 
Kenneth R. Crudup, Unix & OS/2 Software Consultant, Scott County Consulting
kenny@panix.com		CI$: 75032,3044	  +1 617 524 5929/4949 Home/Office
16 Plainfield St, Boston, MA 02130-3633	  +1 617 983 9410      Fax
OS/2 box: pkenny.tiac.net (when I'm online) Get Warp-ed! OS/2 3.0 is here NOW!