The Open Source IA-32 Emulation Project. The "iphone" branch has the port, cleaned up and with SDK 3.0. Ethernet may also work. The "iphone-master" branch has a port to the current head of master.
C++ C R Shell Perl
Latest commit 98c6279 Nov 4, 2009 sshwarts more MTRR res bits
Failed to load latest commit information.
build - VS2008 project files must be present in folder 'vs2008' Apr 29, 2009
bx_debug style changes Nov 2, 2009
doc update for user manual Nov 3, 2009
dynamic - remove obsolete makefile Oct 26, 2002
fpu bugfixes Nov 1, 2009
gui fixed gcc4 warning Nov 3, 2009
host/linux/pcidev another whitespace cleanup by Sebastien Feb 5, 2008
instrument Fix Nov 4, 2009
iodev optimize sr params Oct 16, 2009
misc cleanups, tab2space and fixes for compilation by MSVCPP Apr 14, 2009
patches move a20 handling into getHostAddr method of BX_MEM Mar 8, 2009
plex86 - some more FSF address updates Feb 9, 2009
.bochsrc new .bochsrc memory option Oct 17, 2009
.conf.everything --enable-vme is deprecated Aug 14, 2009
.conf.macosx Some changes and updates for new release - I would like to compile it… Sep 10, 2007
.conf.nothing added smalles possible confiure script Oct 15, 2009
.conf.win32-vcpp - added USB OHCI support to the configure shortcut scripts used for b… Apr 29, 2009
CHANGES fix feature req was done for 2.1 Nov 2, 2009
COPYING - removed wrong character from FSF address (converted invisible and u… Feb 8, 2009 - VS2008 project files must be present in folder 'vs2008' Apr 29, 2009
README-plugins another whitespace cleanup by Sebastien Feb 5, 2008
README-wxWindows another whitespace cleanup by Sebastien Feb 5, 2008
TESTFORM.txt TESTFORM update Jan 31, 2009
TODO update todo Nov 3, 2009
aclocal.m4 - removed wrong character from FSF address (converted invisible and u… Feb 8, 2009
bochs.h remove another unused function Oct 15, 2009 Added Bochs version info for Win32 - patch from @SF tracker Feb 9, 2008 fix defaults for new memory option Oct 17, 2009
config.guess cleanup Oct 31, 2009
config.sub - removed wrong character from FSF address (converted invisible and u… Feb 8, 2009
configure cleanup + small optimization Oct 27, 2009 Indent changes Apr 7, 2008
extplugin.h - update for macos compile Dec 12, 2002 fixes for future Oct 15, 2009
install-sh - commit patch.check-platform. For full details, pull up the patch it… Mar 7, 2002
ltdl.h Add plugin support to Bochs by merging all the changes from the Oct 24, 2002 read 64-bit params for 'memory' Oct 17, 2009
msrs.def added msrs def example Dec 28, 2008 fixed non-printable character Aug 22, 2009
osdep.h right fix for msvcpp problem Oct 2, 2009
plex86-interface.h fixed non-printable character Aug 22, 2009
plugin.h fixed non-printable character Aug 22, 2009
win32_enh_dbg.rc - Added graphical Bochs debugger under Win32 host ! Oct 21, 2008


Bochs - The cross platform IA-32 (x86) emulator
Updated: Sun June 7 10:07:00 CEST 2009
Version: 2.4.1


Bochs is a highly portable open source IA-32 (x86) PC emulator
written in C++, that runs on most popular platforms.  It includes
emulation of the Intel x86 CPU, common I/O devices, and a custom
BIOS.  Currently, Bochs can be compiled to emulate a 386, 486,
Pentium/PentiumII/PentiumIII/Pentium4 or x86-64 CPU, including optional
MMX, SSEx and 3DNow! instructions.  Bochs is capable of running
most Operating Systems inside the emulation, for example Linux, DOS,
Windows 95/98/NT/2000/XP or Windows Vista.
Bochs was written by Kevin Lawton and is currently maintained by
the Bochs project at "".

Bochs can be compiled and used in a variety of modes, some which are
still in development.  The 'typical' use of bochs is to provide
complete x86 PC emulation, including the x86 processor, hardware
devices, and memory.  This allows you to run OS's and software within
the emulator on your workstation, much like you have a machine
inside of a machine.  Bochs will allow you to run Windows
applications on a Solaris machine with X11, for example.

Bochs is distributed under the GNU LGPL.  See COPYING for details.


Source code for Bochs is available from the Bochs home page at  You can download the most recent
release, use CVS to get the latest sources, or grab a CVS
snapshot which is updated nightly.  The releases contain the most
stable code, but if you want the very newest features try the
CVS version instead.


The Bochs documentation is written in Docbook.  Docbook is a text
format that can be rendered to many popular browser formats such
as HTML, PDF, and Postscript.  Each binary release contains the
HTML rendering of the documentation.  Also, you can view the
latest documentation on the web at

Some information has not yet been transferred from the older
HTML docs.  These can be found at


Both the documentation and the Bochs website have instructions on how
to join the bochs-developers mailing list, which is the primary
forum for discussion of Bochs.  The main page of the website also
has links to bug reports and feature requests.  You can browse and
add to the content in these areas even if you do not have a (free)
SourceForge account.  We need your feedback so that we know what
parts of Bochs to improve.

There is a patches section on the web site too, if you have made
some changes to Bochs that you want to share.


If you would like contribute to the Bochs project, a good first step
is to join the bochs-developers mailing list, and read the archive
of recent messages to see what's going on.

If you are a technical person (can follow hardware specs, can write
C/C++) take a look at the list of open bug reports and feature
requests to see if you are interested in working on any of the
problems that are mentioned in them.  If you check out the CVS
sources, make some changes, and create a patch, one of the
developers will be very happy to apply it for you.  Developers who
frequently submit patches, or who embark on major changes in the
source can get write access to CVS.  Be sure to communicate with the
bochs-developers list to avoid several people working on the same
thing without realizing it.

If you are a Bochs user, not a hardware/C++ guru, there are still
many ways you could help out.  For example:
  - write instructions on how to install a particular operating system
  - writing/cleaning up documentation
  - testing out Bochs on every imaginable operating system and
    reporting how it goes.