PC-Engineer wrote: The STB Lightspeed and Miro 20SD run both well in transparent mode....33MHz VLB Speed...
I meant the VLB graphics cards run at 40 MHz along with the VLB SCSI adapter present. Does Transparent still work?
PC-Engineer wrote: Which Windows version and which program would you recommend? I am going to install Win95 in the christmas holidays.
I noticed that 3D Winmark test from Ziff-Davis 3D Winbench97 suite and and the Graphics WinMark from the Ziff-Davis Winbench96 suite to cause errors with some less stable CPU configurations, paritcularly when the CPUs have already been running other benchmarks for 30 minutes prior, like letting WinQuake autoplay in loop first. 3DMark99max is another stressful benchmark program for a 486. Installing Win95 is another good first test. Running MemTest 4.00 overnight is also a good idea.
PC-Engineer wrote: I updated the BIOS before the buildt up to the latest official non BETA version (i guess) - to version 402.1.
From the BIOS zip archive: sv2g4021.bin VL/I-486SV2GX4 Beta BIOS 0402.001 (1999)
Looks like you are using the necessary Beta BIOS.
PC-Engineer wrote:As you can see in the picture above, i can confirm you, that the POD83 delivers a substantial boost in performance with L1 WB. ...Here you can see, that the WB for the POD has a lot more effect than for the P24D. Curiously, the P24D in L1WB/L2WB is slower than in L1WT/L2WB.
I originally looked at the POD in Quake. With benchmarks starting with L1/L2:WT/WT, then switching to L2:WB (no dirty), we get a 17% increase, then switching to L2:WB (dirty hack), we get an addtional 3.5% boost. So that's a 20.8% boost total.
Still using the POD in Quake. With benchmarks starting with L1/L2:WB/WT, then switching to L2:WB (no dirty), we get a -1.9% decrease, then switching to L2:WB (dirty hack), we get a 3.3% increase (on that -1.9%.), for an overall boost of only 1.4%
Thus for the POD running its L1 in Write-through mode, in Quake, the dirty tag write-back L2 cache hack offers a 3.5% benefit over the unhacked write-back L2 mode. When running the POD in L1: Write-back mode, then the dirty tag write-back L2 hack offers a 3.3% benefit over unhacked write-back L2 mode, or an overall net benefit of 1.4% compared to L2 being run in write-through mode.
Looking now at the P24D in DOOM. Benchmarks starting with L1/L2:WT/WT, then switching to L2:WB (no dirty), we get a 3% increase, then switching to L2:WB (dirty hack), we get an addtional 0.3% boost. So that's a 3.3% boost total.
Still using the P24D DOOM. With benchmarks starting with L1/L2:WB/WT, then switching to L2:WB (no dirty), we get a -0.3% decrease, then switching to L2:WB (dirty hack), we get an addtional 0.7% increase, for an overall boost of only 0.3%
Thus for the P24D running its L1 in Write-through mode, in DOOM, the dirty tag write-back L2 cache hack offers a 0.3% benefit over the unhacked write-back L2 mode. When running the POD in L1: Write-back mode, then the dirty tag write-back L2 hack offers a 0.7% benefit over the unhacked write-back L2 mode, or an overall net benefit of 0.3% compared to the L2 being run in write-through mode.
PC-Engineer wrote:I didn't try modbin because i had no empty 512kBit EPROMS anymore to try out. An other reason, that i did the HW hack for dirty tag
I checked Modbin, but there is NOT a hidden option to set the TAG mode from 8+0 to 7+1. So on this motherboard, the TAG hack may be necessary to properly use L2 in write-back mode.
PC-Engineer wrote: was the hope, that then the problem with the Adpatec SCSI controller will be solved
I am able to get the Adaptec VLB SCSI controller, a VLB graphics card (S3 Vision968 w/4MB) in synchronise mode, a 40 MHz FSB, and L1:write-back working with an Am5x86-160, using 1024K cache and 64 MBR RAM.
I'm trying to determine if I want to engage the effort of taking the whole case apart for a 0.3 to possibly 1.4% in total performance gain. I'm adding to to my ever growing list none-the-less. Thank you for point this out to everyone.
Plan your life wisely, you'll be dead before you know it.