Please find attached a patched version of rlfmc.dll that unifies the TSC and non-TSC code paths as much as possible, and switches non-TSC timing from timeGetTime to QueryPerformanceCounter. I validated it as well as possible to work correctly on non-TSC machines and still work as before on TSC- …

Well, I don't know what to tell you as you have a fundamental misconception about how computer hardware works. HWiNFO is not misreporting it as PCIe 1.x is physically not capable of running at any other speed than 2.5 GT/s unless you OC the 100 MHz reference frequency, which will very likely cause …

Hardware specs means nothing without proper software support or drivers.. If im not work PCI-E is backwards compatible with PCI and if pci.vxd is in play for such operations, i doubt that is running with PCI-E speed, there is nothing like pci-e.vxd You could say the same with Sata in Dos, its Sata1 …

PCIe doesn't have a PCI 133 MB/s mode, the speed is negotiated between the motherboard and PCIe card during POST to see what the highest common speed is and then uses that. From a compatibility perspective, Win98 doesn't care what speed it's running at as it only deals with the card at the software …

Probably because PCI-E is running in PCI mode -133 MB/s share for all device include discs, although some very modern MB has multiple parallel PCI buses to improve that.. AGP is up to 2048 MB/s (AGP 8x) and there even some better AGP specific code which give you than more much more brute force. Old …