Reply 40 of 83, by feipoa
- Rank
- l33t++
OK. sis.exe only works on my system if L2 is set to AUTO. If I set L2 to WRITE-BACK, sis.exe causes the system to hang up. Speedsys now shows improvement with the 7+1 dirty tag ram strategy. I will past it again here:
L2: WT --------------------> WB (broken) --------------------> WB (working - sis.exe)
L1: 140.66-----------------> 141.67 MB/s ---------------------> 141.67 MB/s
L2: 57.61-------------------> 61.60 MB/s ---------------------->61.62 MB/s
RAM: 47.41-----------------> 37.73 MB/s ---------------------> 46.73 MB/s
So, there is an inconsequential increase in L1 speed, an modest increase in L2 speed, and an inconsequential decrease in RAM speed. All when compared to L2:WT mode. In DOOM, the working L2:WB resulted in 1293 realtics, while for L2:WT, it is 1295 realtics. 2 realtics difference translates to 0.1 fps extra for the working L2:WB mode. 57.76 fps vs. 57.68 fps. This is why, when you have working L1:WB cache that there is little incentive to use L2 cache in write-back mode as well.
Perhaps bakemono could make an NT4 driver for this function? If one is to modify the registers on the motherboard's BIOS, then how will we get the L2 cache back into WT mode without having to reflash the BIOS? Because it looks like we are trying to override the AUTO mode rather than the write-back mode. Is this analysis correct? Or is there a way to modify the write-back mode option for these register edits?
Plan your life wisely, you'll be dead before you know it.