EEC and CL question - Techist - Tech Forum

Go Back   Techist - Tech Forum > Computer Hardware > Monitors, Printers and Peripherals
Click Here to Login
Closed Thread
 
Thread Tools Display Modes
 
Old 01-22-2005, 02:32 PM   #1 (permalink)
Newb Techie
 
Join Date: Dec 2004
Posts: 30
Default EEC and CL question

I'm buying some new memory and can get EEC memory cheaply, is it OK to use this on any mobo, or does it have to be EEC compatible?

Plus, what's cas latency? Is it the amount of time the memory can hold it's data fotr between refereshs? And how does this affect my system?

Any help appreciated!

Thanks,
Jim
__________________

jim_77 is offline  
Old 01-22-2005, 04:26 PM   #2 (permalink)
True Techie
 
Join Date: Jan 2005
Posts: 184
Default

Basically your memory has cells with unique addresses based on what row and column they are on. The chip set reads the row of the memory matrix using RAS, then the column using CAS.

The latency between reading the row and column is called RAS-to-CAS Display and the time between reading the column and actually providing the information is called CAS Latency.

RAS - Row Address Strobe
CAS - Column Address Strobe
Latency - Time Taken/Delay
__________________

rememberme is offline  
Old 01-22-2005, 04:30 PM   #3 (permalink)
True Techie
 
Join Date: Jan 2005
Posts: 184
Default

...and I believe ECC is slower than non-ECC because it is an error correction feature that corrects bit-errors. You don't really need this if it is a personal computer and I think your mobo needs to state that it is supported.
rememberme is offline  
Closed Thread

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off




Copyright 2002- Social Knowledge, LLC All Rights Reserved.

All times are GMT -5. The time now is 11:27 PM.


Powered by vBulletin® Version 3.8.8 Beta 1
Copyright ©2000 - 2017, vBulletin Solutions, Inc.