DOSBox-X Git (2016/01/29) is compiled. DOSBox-x is a branch of DOSBox v0.74. DOSBox emulates an Intel x86 PC, complete with sound, graphics, mouse, joystick, modem, etc., necessary for running many old MS-DOS games that simply cannot be run on modern PCs and operating systems, such as Microsoft Windows XP, Windows Vista, Linux and FreeBSD.
DOSBox-X Git Changelog:
* S3 bugfix: INT 10h now uses I/O writes to clear & remove the hardware
cursor. It uses I/O, not direct changes to VGA state, so that it works
properly within Windows 95 I/O virtualization. This fixes the garbled
cursor that would otherwise appear if a DOS game goes fullscreen and
uses the VESA BIOS to switch into 640x480x256 or higher res SVGA modes.
At the same time, allowing Windows 95 to virtualize I/O means bringing
up a DOS box in a window will not kill the hardware cursor.
Bugfix for GitHub issue #148: “Documentation: Windows 95 dos box and
vesa mode with hardware mouse”.
* S3 Trio emulation bugfix: On S3 cards, the “compatible VGA” vs “Extended
SVGA” memory mapping is controlled by bit 3 in CRTC register 0x31. INT
10h emulation already writes the bit via I/O, but manually set the
“compatible chain 4” enable flag farther up. The problem with setting it
manually is that the generic “S3” driver in Windows 95 (using bank
switching and legacy VGA memory 0xA0000-0xAFFFF) expects to trap and
virtualize that bit through I/O, which it can’t when DOSBox just sets it
internally like that. Prior to the fix, opening a DOS box in Windows 95
would trigger “compatible chain 4” emulation which would then cause any
non-accelerated graphics drawn after that point to come out garbled,
until you forced a video mode reset by entering and leaving fullscreen
mode in the DOS Box. As a reminder, Windows 95 calls INT 10h AX=0x0003
(set 80×25 alphanumeric text mode) when opening a DOS box and it does
so in a virtualized sense so that INT 10h affects the DOS virtual
machine, not the actual Windows 95 desktop.