Decent chance my pc133 memory can take the tightest timings I can set since it’s running at pc75. I’m a little rusty, can you more experienced guys/gals help me with the fastest timings?
In my experience almost all of those are as simple as the lower the better, though sometimes they can be counter intuitive. After installing Windows and installing benchmark programs, I'll generally begin to tighten the timings and see if it improves the score while remaining stable. For example, sometimes even underclocked memory can't tolerate CAS 2, so you have to prepared to change them as needed. And if you make a bunch of changes at once and your system becomes unstable, you can't be sure which change caused it, so best to be patient and change one thing at a time.
"I'd rather be rich than stupid" - Jack Handey
On my KT7A, I used to curse Windows 98 for being so unstable. When I got a hold of Windows XP, the install would freeze up, and I finally tried setting the memory timing to defaults - only then would XP install successfully. My cheapo Tiger Direct generic PC133 was not stable with the tighter timings (even with increased voltage) and it seems that Windows XP had a way to check that during the installation, where Windows 98 did not. So I was blaming the operating system for something that I had actually caused myself.
"I'd rather be rich than stupid" - Jack Handey
Repo Man11 wrote on 2021-01-23, 05:43:On my KT7A, I used to curse Windows 98 for being so unstable. When I got a hold of Windows XP, the install would freeze up, and I finally tried setting the memory timing to defaults - only then would XP install successfully. My cheapo Tiger Direct generic PC133 was not stable with the tighter timings (even with increased voltage) and it seems that Windows XP had a way to check that during the installation, where Windows 98 did not. So I was blaming the operating system for something that I had actually caused myself.
good plan. gonna have to circle around back to this can't even get windows on it yet 🤣
