DOSBox-X Git (2026/05/06) is an enhanced version of DOSBox, designed to emulate an Intel x86 PC, enabling the play of old MS-DOS games on modern systems. The latest update includes several memory setup improvements: cleaning up memory management, adjusting the minimum memory control block (MCB), and optimizing the setup for device drivers. Notable changes entail ensuring device drivers respect memory limits, and correcting how bytes processed by drivers are reported. These updates enhance overall stability and functionality for users seeking to run legacy software. Download is available via the provided source link.
(HEY YOU!! We hope you enjoy! We try not to run ads. So basically, this is a very expensive hobby running this site. Please consider joining us for updates, forums, and more. Network w/ us to make some cash or friends while retro gaming, and you can win some free retro games for posting. Okay, carry on đ)
DOSBox-X Git (2026/05/06) has been compiled. DOSBox-x is a version of DOSBox. DOSBox emulates an Intel x86 PC with sound, graphics, mouse, joystick, modem, and more, enabling the execution of many classic MS-DOS games that cannot be run on contemporary PCs and operating systems, including Microsoft Windows XP, Windows Vista, Linux, and FreeBSD.
DOSBox-X Changelog:
* Enhanced memory setup clean-up.
* Revised the implementation to trim the MCB chain after the fact from the minimum MCB, rather than setting DOS_MEM_START immediately.
* Eliminated the unnecessary mcb_sizes variable from SetupMemory.
* Disabled the dummy device MCB in SetupMemory.
* Decoupled IHSEG setup from DOS_SetupMemory.
* Avoid reserving the top 16 bytes of conventional memory for the UMB chain if umb=false.
* In DOS_Execute(), when invoked with DOSEXEC_DEVICEDRIVER, accept the upper 16-bit word as a segment limit. After determining the executable resident size, ensure adequate memory is available within the limit, so device driver loading does not attempt to load something that won’t fit. Note that MS-DOS 4.0’s source code for the EXEC OVERLAY call does not range check and will load without considering memory availability, which may result in memory overwrites.
* When directly calling the external device driver for reading/writing in response to INT 21h AH=3F/40 (READ/WRITE), return the actual byte count processed instead of misleading the DOS program into thinking that all bytes were handled.
Retro Replay Retro Replay gaming reviews, news, emulation, geek stuff and more!