🚀 go-pugleaf

On 20 Apr 1996 John@.MISSING-HOST-NAME. wrote:

[snip snip snip]

> Now hear this. OS/2, W95, and even the mighty UNIX, have absolutely no
> idea what the speed of the memory is. They don't care, it matters not at all,
> and anyone who says that the OS knows, or cares, is wrong. Plain and 
> simple!
> 
[snip]

Hmmmm..., I may be getting into this thread a bit late, but
if this issue is so "plain and simple" then why do some 
authorities disagree with you in print?  For example, the authors of 
_OS/2 Warp Unleashed_ state, "A Trap 0002 almost always indicates a 
problem exists with the physical memory.  The most common causes are 
single inline memory modules (SIMMs) that are not the same speed..." (P. 
943)  Unless I'm missing something here, your statement is entirely at 
odds with this statement as well as others.  Another example can be found 
in the _User's Guide to OS/2 Warp_, which comes with Warp itself and is 
published by IBM.  Here, on p. 175 the author's explain that a Trap 0002 
error can be due to mismatched SIMMs that operated at different speeds.

You go on to say:

> have we got it now? Mix the speeds. faster won't hurt! No OS on the planet
> can determine ram access speed! No OS cares!
> 

Well, it seems that at least from two sources, you are overstating the 
case.  The OS may not "care" (whatever that means), but according to 
these sources it may get tripped up in accessing memory from SIMMs of 
different speeds.

===========================================================================
     Scott R. Eliason                    Email:  scott-eliason@uiowa.edu
     Department of Sociology           
     University of Iowa