rasz_pl wrote on 2022-09-04, 21:10:
I rather whip out debugger and add few noops here and there to fix the game
Much easier to get a flexible system, than to try and fix all DOS games that have such quirks (and there are many!). 😁
mockingbird wrote on 2022-09-04, 20:16:
With a multiplier of 3 and throttle set pretty low, I can get to a 486 DX2/50 (according to Speedsys), but the game runs too slow.
In my experience, Speedsys is not accurate for fast machines with throttled speed/disabled caches (many times it will show a much higher speed than it should - it's unclear what underlying tests it does to evaluate the performance).
Something like 3DBench 1.0C is much more accurate, because it will show you what the actual VGA performance is. For Titus the Fox, you generally want a score between ~ 19 and 28 FPS in 3DBench 1.0c (equivalent to the 486SX-20 <--> 486DX-33 speed interval). Norton System Info is also decently accurate.
So, depending on the platform, the CPU you're using (and its native frequency), you might achieve this speed by simply disabling the L1 cache, without needing Throttle at all (if you use Throttle, speed might drop too much and you will again introduce slowdown/stutters).
For Jazz (on VIA KTxxx chipsets!), you want to drop your CPU & FSB frequency to the lowest that your CPU/motherboard supports, and then use Throttle up to levels 5 or 6 (maybe a bit more), to get to a Pentium MMX equivalent speed. This will get rid of the Turbo Pascal divide by 0 error (or you can patch the game with the TPpatch and then you can play it at full CPU speed - however, with certain sound cards, sound might be affected/run at a lower sample rate 🤣 ). Do NOT disable the L1 cache, Jazz runs much better on very late 486 or Pentium systems (~ 60 - 150 FPS in 3DBench 1.0C). You can disable the L2 cache, though (but the impact will be limited). Again, this is not an exact science (if it were, things would be much easier). It's up to you to evaluate what performance a game needs and play with the settings to achieve said speed.
Now, it's been a long time since I've tested a KT133 board (the last one I've tested was the ASUS A7V a few years ago), but according to my notes, ACPI Throttle worked fine, just like on newer KT400/KT600/KT880 boards.
The idea is to only use ACPI Throttling if you actually need it. 😀
mockingbird wrote on 2022-09-04, 20:16:
You say you managed to get Titus running perfectly with your Ezra-T?
I doubt that there's a single DOS game that won't run perfectly on the Ezra-T (with the right combination/settings). With the Ezra-T, you don't need ACP Throttle... at all! Man, I should really make a video about this CPU's DOS versatility, but I'm just way too lazy... 😁 (and busy 🙁 )
Of course, the Ezra-T is only part of the equation. The video card that you're using with it will also be important (and, let's face it, this CPU needs a good videocard - either a GeForce 2 GTS/PRO/Ti or at least a Voodoo 3 3000). These video cards are generally very compatible, but there will undoubtably still be some games that have issues with them (still, overall, we're talking about very few games).
As with VIA KTxxx chipsets and Throttle, it's basically a matter of knowing what speed a certain game needs (and knowing what tools actually show the correct speed - again, 3DBench 1.0c has always worked perfectly for me, so it's only a matter of learning what FPS is equivalent to what speed).
2 x PLCC-68 / 4 x PGA132 / 5 x Skt 3 / 1 x Skt 4 / 9 x Skt 7 / 12 x SS7 / 1 x Skt 8 / 14 x Slot 1 / 6 x Slot A
5 x Skt 370 / 8 x Skt A / 2 x Skt 478 / 2 x Skt 754 / 3 x Skt 939 / 7 x LGA775 / 1 x LGA1155
Current PC: Ryzen 7 9800X3D
Backup: Ryzen 7 5800X3D