@cde
Just to update you sir, I'm probably going to abandon the Tualatin route. No matter what, I cannot get the PIIX4 (BX) southbridge stable with my Ultra133 TX2 card, and that's a mandatory requirement (TRIM in DOS).
I'm down to the all PCI P4 2.6 northwood build and a Yamaha card alongside a Vortex2, or a KT133A build with an ESS ISA card and the Vortex2...
I prefer the ESS card to the Yamaha, but I also prefer the Intel platform to the VIA.
I wanted to ask you, which method of throttling were you not able to get to work? Was it Throttle for DOS? I ought to test that for you. As was stated before, Abit disabled a certain ACPI function in their last BIOS revision... There is an earlier revision which keeps this feature and might allow the board to work properly, and needless to say, work without requiring BIOS multiplier changes.
EDIT:
Well turns out my instability was caused by a newly installed GeForce 2 GTS. Either the GeForce 2 GTS is a speed sensitive card (crashed less at 1Ghz on my P3 system), or I have two defective cards one with Samsung ram, one with Infineon... I don't know what's wrong with the former one, it won't post at all.
SETMUL does not work. I had the same problem as this gentleman, so it's not board specific.
Next I'll try THROTTLE.EXE... I would have preferred SETMUL because I had the BIOS modified to expose the disable ACPI option (and use APM instead), and I think THROTTLE needs ACPI.
EDIT 2:
THROTTLE.EXE works... Both in ACPI and APM mode. Next I'll try SETMUL two other brands (and models) of KT133A boards... There are initial reports of it working with KT133 in the thread, so I don't know what's going on. I tried several different CWSDPMI.EXE versions. If THROTTLE.EXE is doing what it claims to do, and not just disabling caches like its debug output says it is, then to heck with SETMUL.