Reply 100 of 140, by andre_6
Eep386 wrote on 2021-06-12, 16:09:The easy way to get the total cache is to watch the boot-up sequence. At some point it should say something like '256K CACHE ENA […]
The easy way to get the total cache is to watch the boot-up sequence. At some point it should say something like '256K CACHE ENABLED'. If it's an Award BIOS, then the cache will be listed on the final sign-on screen which shows the 'specifications' of the system.
For example, for 256K cache, both JS1 and JS2 should be set to 2-3.
If this is the case, just try putting the SRAM chip into that empty socket, aligned exactly the same way the other chips are (eg. if the text reads from left to right on the other chips, the chip you're adding should be aligned in the same manner).If you've already installed the SRAM properly, then just power it up. Normally the BIOS won't say anything different about it, the difference will instead be measured in benchmarks and, in some cases, can be 'felt' as the system is generally running faster. On occasion you may have to enable L2 Write Back Cache in BIOS setup, but that's only on certain weird motherboards. (Sometimes that option is under a different name, such as "Tag includes Dirty" or "7+1".)
If you still have doubts about your cache size, or you are curious about the kind of performance you're getting, you can use a utility like CACHECHK to help you ascertain how much cache you have, and how fast your memory and cache access speeds are. (Run it without EMM386.EXE active, otherwise you'll get strange behavior.)
CACHECHK.zip
Ascertaining the cache size from CACHECHK is a little tricky at first as it won't outright tell you, but you can ascertain it by observing the access latency times.
Cached ranges will have a smaller "score" number than areas outside of cache, like so:1 2 4 8 16 32 64 128 256 512 1024 etc..
<meg range> 28 28 28 28 40 40 40 40 41 47 47....
From a listing like this, you can tell that accesses up to 8K are 28ns, so that would be the "first" level of cache in the system. On your garden variety 486 chip, it's usually up to 8K.
Accesses from 16K up to 256K are 40ns, so that would probably be your "second" level of cache. Sometimes the number at the very end of the "cached" range is a little higher or lower than the others, this is normal (some chipsets are like that).
Everything above 256K scores a higher number, so that would probably be the off-cache access speed.I should mention that your results will undoubtably vary. Chipsets and memory configurations tend to vary very widely (pun not intended) from system to system.
In case you're curious as to what 'average' 486DX2-66 cache and off-cache scores should be, generally your L2 cache speed "scores" should be below 50 (around 47-ish) and your off-cache scores below 66.
For a DX-33, these numbers may be a little higher.If CACHECHK gives you a warning about certain areas of memory being "really slow", don't worry too much about it, its algorithm for determining that kind of thing is a little buggy, and will often say that even if said ranges are blazing fast. Also, if certain cached ranges are really close to each other in speed, sometimes CACHECHK gets confused and says you only have one cache - you can disregard this message if, say, the L1 access is 28 and L2 access is something really close (but still discernably different) like 30 or 32, or other really close numbers. Certain *extremely* fast motherboards sometimes return scores like that.
I have inserted the chip on the board and placed the jumpers at 2-3 like the manual indicates. Then I powered on and went to the Award BIOS. Here it said:
Cache Internal & External: Enabled
Sizing Cache & Memory: 64k...ok
(Page Down to other BIOS page)
256/384k Cache Relocation Enabled
Cache Timing Fast
Video Cacheable Disabled
System Cacheable Enabled
It automatically changed my HDD's cylinders (not the rest), and even after I reset the correct values it doesn't boot at all. I'm going to try and boot from EZ Drive boot disk to see what happens. But if it says "sizing cache & memory" at 64k then something's awry here right?
Edit: Turns out that the jumpers were at 2-3 all along. The 256k is recognized and everything works as it should, if I get the chance soon I will give it a look with the cachechk, thank you. It was an inexpensive upgrade so it would always be worth it. As soon as I can I will install the remaining upgrades