Latest release: Bochs 2.1.1

Version 2.1.1 is a bugfix release :

• fix bug in int15h function 0xe820
• fix vmware3 disk support on big-endian platforms
• fix conditions for NM exception on FWAIT instruction
• fix symbol conflict in rfb and x display libraries
• allow 16 bit writes to ne2k page 0
• notify display libraries on change of bpp
• fix bug in int13h function 0x10
• fix floppy dialog error on win2k
• fix adress check in TSS IO permission bitmap
• fix buffer overflow vulnerability
• updates for MacOS compile

Details on what has changed since version 2.1


Previous release: Bochs 2.1

It's been nearly one year since the last stable release :

• We have improved the accuracy of the simulation in many ways, notably in the cpu, fpu, and vga areas.
• 3DNow! and PNI instructions are now supported, and Bochs includes a new disassembler that supports all IA-32 instruction sets.
• On the I/O devices side, Bochs now provides experimental PCI VGA and USB cards, 16550A uarts and gameport emulation.
• New types of disk image can be used as harddisks : stackable, commitable or growing. Bochs can also use VMWare 3 cow disk images.
• Sdl, x11, win32 and wxwindows display libraries now support 15, 16, 24 and 32 bpp color depth, and the x11 vga font is not needed any more.

Note that some configuration file options have been deprectated : please update these options to the new syntax, as they're likely to be removed in future releases.

Details on what has changed since version 2.0.2.


Bochs Binary and Source Releases

You can download any release since March 2001 on the Releases Page.


Download CVS Snapshot

CVS Snapshot: Bochs, like many other open source projects, uses CVS (Concurrent Version System) to keep track of source code. Unlike the current release, the CVS version of the sources contains everything the developers have written to this date, and it can change daily (or even hourly). As a result, the CVS version of Bochs will have more features and bug fixes than the release, but also it may be somewhat less stable. You can decide if you prefer to go exploring and try out our newest code, or stick with the better-tested release. Since the CVS sources are always in motion, we take a snapshot each night at some late hour after most developers should be in bed.

The CVS snapshots are provided as a convenience only. Of course, you could also get the same information using CVS itself. Some of the benefits of using CVS directly are: you can get any release or version, view the log messages that say what files were changed, and make patches very easily with "cvs diff -u". Last Modified on .