🚀 go-pugleaf

In <Pine.A32.3.91.960422214058.64627A-100000@green.weeg.uiowa.edu>, "Scott R. Eliason" <seliason@blue.weeg.uiowa.edu> writes:
>> Give it up, dude. No one is listening to the facts. Some of us understand, the
>> rest are on their own if they won't pay attention. Its kind of like a 
>> religious arguement. They only believe the small portion they extract from the 
>> manual, totally ignoring the overall context.
>> 
>> John
>> 
>
>You know, your responses leave a lot to be desired.  Even though I 
>started reading this thread late in the game, I was listening and 
>trying to learn something from it.  And thanks primarily to others who 
>have contributed to the conversation, I have.  And though I've 
>learned a bit from reading your posts as well, you, on the other hand, 
>when confronted with information which isn't consistent with what you 
>already believe, can only muster statements like that above and 
>similarly unhelpful statements in other posts.   
>


You said it yourself, you started reading this thread late in the game. I already
went to through the details and the mumbo jumbo about all this RAM speed
crap. Its what I do for a living, and whether you like it or not, I am very 
good at it.

Once more for the late comers:

The OS cannot determine the access speed of any memory device.

No desktop PC on this earth can determine the access speed of a memory
device.

If your system is configured to run 70ns SIMMS, you can put 10ns SIMMS
in their place and the PC will not know the difference. The reverse is not
true.

There are no 'local PC stores' that can test your RAM to determine its speed.

If you run a Pentium with 2 SIMMS, it will do no good to put the slower
device in the first slot, since the first slot to a Pentium is the first two
slots. (check the bus access size on a P5)

Let's see, that's all I can think of for now. When you join a thread late,
read it for a while before you make accusatory statements. Yours was no
better than what you accuse me of. 

If you would like a friendly hint, go into your BIOS settings, and change the
wait states, one at a time. After each change, run your system for a while,
to see if it is stable. Chances are you may be able to run with one less
wait state since most RAM can run faster than its guaranteed rating. Don't
do this on mission-critical systems, or in any machine where a crash could
have serious implications. Sometimes you can run for days, and suddenly the
system will freeze. Do this at your own risk. 

Have a nice day.

Regards,

John