🚀 go-pugleaf

In <4kuqs2$g76@usenet2.interramp.com>, ir003870@interramp.com (Billy Ko) writes:
>In message <4krr9c$nbv@panix2.panix.com> - kenny@panix.com (Kenneth Crudup) wri
>tes:
>:>
>:>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!
>
>Excerpt from Inside OS/2 Warp, page 804:
>
>Trap Errors and Memory Problems
>Some basic things to check for when a customer is experiencing trap errors of 
>any kind include:
>
>1. All memory SIMMs must be the same size and speed...
>
>2. All SIMMs should be from the same manufacturer.
>
>3. If the customer has mixed memory SIMMs, it may be possible to get them to 
>work, although this would be a configuration unsupported by OS/2
>
>If mixed memory SIMMs are being used, the customer must place the SLOWER 
>speed memory in the first or lowest address sockets.  This approach 
>occasionally works because OS/2 tests memory in the lower address space to 
>determine its speed, then runs ALL memory at that speed
>
>
>And one more tip:
>
>Please don't engage in personal type attacks, it is very unbecoming of a 
>person.
>
>Bill
>Team OS/2
>
>
>
>

I got 60ns in the first bank, and 70ns in the second. works just fine. No
memory trap errors what so ever.. 

	Dennis