Reply 340 of 394, by feipoa
1) The x222 Memory Read Burst Timing hack for EDO only seems to work with my single-sided 64 MB parity SIMMs. It did not work with my EDO double-sided 64 MB parity SIMMs. Unfortunately, I only have four sticks of single-sided 64 MB EDO parity simms and eight sticks of double-sided 64 MB EDO parity simms. The boot-up memory counter counts all 512 MB, but I haven't tested them in operating systems because each OS is set for x222 read timings. There is no way to skip the boot-up memory count, 256 MB is about as much patience as I have anyway so I won't be procuring more single-sided EDO SIMMs.
2) I tried to run a pair of Intel MMX Overdrive CPUs in this board (PODPMT66X200), and while the CPUs work individually, the system doesn't show the pair on boot - it just shows one. I guess Intel disabled SMP on their MMX overdrives. So looks like if you want to run dual MMX CPUs, you need to use upgrade VRM's, like those from Powerleap, Evergreen, Kingston, etc. Alternately, you can still use an MMX overdrive in the CPU1 socket and the Kingston in CPU2 socket and still use SMP.
3) I re-arranged my systems so that I can have matching Voodoo2 SLI's in the NEC system. It took some time to find reasonably priced Voodoo2's ($50-$60 each) as the market for this vintage garbage has gone COVID crazy.
4) re: r_smp at 0 and 1 in W2K. I kept running into trouble running Quake 3 v1.32 on this system in W2K. However, I did run it in NT4. r_smp 1 will not work with the Voodoo2 SLI for whatever reason, but I did try r_smp 0 vs. r_smp 1 using the GF2MX. r_smp 0 = 14.7 fps w/snd and r_smp 1 = 15.1 fps w/snd, so about a 3% increase. I did boot NT4 with the /onecpu flag and the r_smp 0 result was the same, that is, 14.7 fps. This implies to me that having the second CPU taking care of background operating system tasks didn't help any.