feipoa wrote on 2024-12-18, 04:54:
Do you have some clock-for-clock comparisons at around 25-30 MHz, between HT12-16A and HT18/C?
I have the exact same board in that link. I was using 24Mhz mostly because of the ISA bus synchronising to the CPU clock if you don't solder a DIP-14 socket at the top-right corner of that board and set JP9 to 1-2, and with the PT-606E multi I/O card I was getting data corruption if I went to 12.5Mhz ISA bus speed - 12Mhz is perfectly stable. While it's nice to have a secondary IDE slot, I've never used it so I decided to switch back to the PT-606G, and now I seem to be getting bottlenecked at 13.5Mhz ISA bus speed.
My RAM for the HT12 (it is simply labelled HT12, not a variant) is not binned well enough to get above 25Mhz 0WS - running at 27Mhz corrupts the processing of CONFIG.SYS, but even at 25Mhz I get several stability issues. I can't even use a ET4000 without it immediately crashing in Wolf3D unless I drop down to 16Mhz 0WS, I only have 32/40/48/50/54/66Mhz oscillators available to use. It was doing fine with Windows benchmarks at 1024x768x256, but it crashed very early during the full Winbench 3.11 suite (as opposed to the useless Graphics WINMARK test). S3 911/924/801 cards will not load Windows at 256 colours, but are perfectly fine at 16 colours. The GD5429 is one of the most reliable cards I have, only showing a minor glitch with one specific test in the full Winbench 3.11 suite at 1024x768x256 and having an off-by-one issue with loading the Wolf3D title screen a single time directly after running Doom8088, which had glitched the rest of the image. No other issues that I've seen, even with running a full set of benchmarks at 800x600x65K in Windows.
With all that said, I freshly compiled some new benchmarks using the GD5429, the PT-606G for multi I/O and a 3com 3c509B that I use for XT-IDE. In addition to three runs of wolf_286, I also used three runs of WolfensteinCGA and a single run of the most recent release of Doom8088 using the doom2my and doom213h EXEs for benchmarking:
HT12 25Mhz 0WS, ISA bus at factory default of 8Mhz
doom2my - 18.119
doom213h - 15.976
wolf_286 - 17.2
wolf3dc - 27.4
HT18C 25Mhz, ISA bus set to 8Mhz via additional 32Mhz oscillator
doom2my - 14.857
doom213h - 12.839
wolf_286 14.6
wolf3dc 21.4
HT18C 25Mhz, ISA bus set to 12.5Mhz via CPU oscillator (factory default)
doom2my - 15.534
doom213h - 13.570
wolf_286 - 16.0
wolf3dc - 22.7
The CPU performance is fairly obvious with the Doom8088 benchmarks, as there's significantly less breathing room to be gained from increasing the ISA bus speed compared to wolf_286 or wolf3dc. The HT18C is good if you really need to multi-task a lot with Windows 3.1, but outside of one specific use case with a Doom map editor that works on Standard Mode that was claiming to use 6MB of RAM, I can't think of any genuine use case where I would prefer it over the HT12, especially when I get properly binned RAM which hopefully should be shortly after Christmas.