First post, by retro games 100
- Rank
- l33t
Problem overview: if the mobo BIOS external cache setting is enabled, mobo hangs on it's POST activity.
Mobo: Acer AP43 (486 PCI), SIS496 chipset.
http://stason.org/TULARC/pc/motherboards/A/AC … C-486-AP43.html
Cache: it's been jumpered for 256k, but I don't know how to check (verify) how much cache I have on the mobo.
Testing: if I set the BIOS to "optimal setting", and also manually edit the external cache setting to disabled, then the mobo boots up successfully. It's only when I edit the external cache setting to enabled, that the mobo does not boot up successfully.
When I set the external cache to enabled, I also set the cache mode to write thru (not write back), and leave the tag width at 8 bits (not 7 bits).
Looking at the board, I see 2 cache banks. Each bank can hold 4 chips. 1 bank is full, the other bank is empty. So, there's 4 cache chips (and also 1 tag chip.) Each of the 4 cache chips occupy their entire socket space, but the tag chip is "2 notches" short of occupying it's entire socket space.
The 4 cache chips has this writing on them -
UM61512AK-15
9603G
MB2419
The tag chip has this writing on it -
W24257AK-15
95461
Looking at the mobo specification (please see link above), there are 5 cache configurations to choose from -
128KB
256KB (A)
256KB (B)
512KB (A)
512KB (B)
The board is currently jumpered for 256KB (B). I wonder if other BIOS settings are not cooperating with this cache configuration, or one of the cache chips is faulty. I would really like to mess around with any BIOS options first, before I start pulling out chips...
Any comments very gratefully received. 😀
Edit: I got the chipset a bit wrong. Sorry. There's 2 chips on the mobo, 1 says: SIS 85C497, the other chip (of a similar size) has a hand written sticker on it that just says: 21932. The mobo is AMIBIOS, but the interesting thing is that on POST, it displays some kind of revision update of feb '96, which seems quite modern! Lastly, inside the BIOS, there's an "engineer mode" which lets you mess about with memory and cache timing, but as I don't know what I'm doing, I just left the settings "as is".