But, speed (and compatibility) suffers greatly through emulation, which is always kludgy. Many think emulation is the cureall and the panacea, while of course it is NOT. DOSBOX, for example is a far cry from running real DOS on bare metal. About 10x-50x slower and not perfect fullscreen, VESA write …

So, the last, and "fastest" true DOS machine possible will be a 10th Gen i9 system? I wonder what the last (CSM) VBIOS version is or was officially relased by Intel. Is it the Kaby Lake / Skylake VBIOS 16-bit code (intel HD graphics 620 / 650), which I believe stopped at build 1062 back in 2018 / 19 …

Much of the confusion could be mitigated by having a list right at the front of the readme.txt in the translation patch (which is distributed separately!) and the re-implementation engine, something like: The following combinations of translation patch, game data and engine are possible: Game Data …

I also registered at rpgcodex and asked the experts there is there's any way to run a native DOS .exe version of the game, even if it is the reimplemented SDL version of the game. All I would like to do is run the game natively in DOS. It appears the the SDL version is Windows only, but there's some …

ah lol =) that was VIA chipset, i have it, so i can't fix it?) p.s. offtopic --- i found Mario 64 for DOS its also use glide3x.dxe (3dfx) Mario 64 looks for DOS looks neat indeed, but I can't compile the DOS .exe. May you or someone else who has compiled the binary please post a link to download …

Late reply, as I just saw RaVeN-05's offtopic post about SM64 for DOS in the FitzQuake for DOS [fxMesa] of the Releases forum I've just discovered that this DOS port has been made, and it's such a shame that a compiled binary isn't available. (I mean a native CWSDPMI dos .exe). As I can't compile …

Same for video codecs. Instead of going higher and higher in resolution, settle for something good and ged rid of artifacts and blur. The improvements made in compression should not be used to save bandwith, but to enhance image quality at the same bandwitdh. Wiser words were never spoken! I've …

That explains the strange behavior. I suspected it was a BIOS problem. So, without disassembling the BIOS (both of my core i systems obviously have the CSM, so I can thankfully boot DOS natively), and manually setting the MBR for the HWP_ENABLE bit to 0, we're out of luck. Thanks for the information …

I've tested the program on my 1150 system (with G3260 cpu) and had confirmed your observation. Using the -t1, -o1, and -t1 o1 commands all yielded the same results, giving doom real ticks of ~4240. I'm not sure what is causing this, it looks really weird to me, as the -t command programs the south …

Many thanks for the significant new update, and elimination of the double fault errors on core i systems. Your program keeps getting better and better. This is fabulous indeed, I'll say the best utility of the year 2020 for DOS *by far*! I have a 5th Gen core i5 , the 5200 and I can now report that …

Next revision... perhaps to include AMD K10 multiplier support per Falcosoft's suggestion? I hesitate to include CPUs beyond K8/Core2, as their chipsets no longer support Windows 98, hence they are not ideal for retro gaming, although they could still be used for DOS gaming if slowed down enough. …

I tried your new 6.05 above, and it reports more CPU information (frequencies and cores) than previous 6.04, but still does not detect my CPU as the correct i7 Broadwell family, says unknown p6 generation. I've an i7-5500u chip in this laptop, which has a nominal core clock of 2400 Mhz and peak of …

The posted v. 6.04 from 8th April also works well on my i7-5500 notebook now. I peeked in the code and it seems the latest Core i3/i5/i7 detected is Ivy Lake. Later revisons being undected or deleted. I ought to test this on older and / or less common PCs, but the oldest I have now is a Core2 …

I'm sure appreciative of the response, and for your taking the time to explain how backporting code to DOS would not be an easy task. Interestingly, I am running on a Lenovo laptop, i7-5500, 8 GB RAM, MS-DOS 7.10, and version 6.03 runs fine, but 6.04 locks up upon startup. Once I press OK at title …

@Mumak Thanks for resurrecting HWiNFO for DOS! I registered just to say "thank you", but also to ask a vexing question: Please, please re-enable Sensor support. That was always the most useful feature of Hwinfo for me. As well as the "Benchmark" section. These were fantastic features. Removing …