The Open Source IA-32 Emulation Project. The "iphone" branch has the isoftcom.com 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.
Switch branches/tags
x86-64-works x86-64-update-marker2 x86-64-update-marker1 x86-64-merge2 x86-64-merge1 working-on-smp-03-21pm win32-snaps-2001-10-05 tmp-before1 tmp-after1 stay-in-cpu-loop-for-1proc softfloat-fpu-implementation_ver4_branch_root softfloat-fpu-implementation_ver3_branch_root softfloat-fpu-implementation-branch_root smp-bochs-updated-to-here smp-bochs-updated-to-05-08-2001 smp-bochs-updated-5-22-am smp-bochs-before-update-05-21 smp-before-using-SMF=0 rpm-for-tim-05-22-2001 no-cpu-array-for-1proc may7 main-branch-when-1_2-released io-cleanup-bbd-works-smf1 io-cleanup-bbd-works-smf0-except-cpu io-cleanup-bbd-afternoon io-cleanup-bbd-05-10-late cvs-snapshot-2003-08-07 cvs-snapshot-2001-10-08 cvs-snapshot-2001-10-02 cvs-snapshot-2001-08-14 bochs-style-FPU-branch_root bochs-cosimulation-patch-root before-x86-64-merge before-term-patch before-stripping-io-newlines before-split-hard-disk before-smp-branch-merge before-plugin-merge before-merging-plugins before-make-install-hacking before-kbd-patch before-io-branch-merge before-cpu-speed-optimizations before-ch-rombios-patch august1 applied-patch-portable2 applied-patch-portable1 applied-patch-const64bit after-x86-64-merge after-term-patch after-stripping-io-newlines after-smp-branch-merge after-merging-plugins after-io-branch-merge after-ch-rombios-patch WORKING_SMP_ZWANE TMP-august1 REL_2_4_1_FINAL REL_2_4_pre1_FINAL REL_2_4_FINAL REL_2_3_7_FINAL REL_2_3_6_FINAL REL_2_3_5_FINAL REL_2_3_pre3_FINAL REL_2_3_pre2_FINAL REL_2_3_pre1_FINAL REL_2_3_FINAL REL_2_3_BASE REL_2_2_6_FINAL REL_2_2_5_FINAL REL_2_2_1_FINAL REL_2_2_pre4_FINAL REL_2_2_pre3_FINAL REL_2_2_pre2_FINAL REL_2_2_pre1_FINAL REL_2_2_FINAL REL_2_2_BASE REL_2_1_1_FINAL REL_2_1_pre3_FINAL REL_2_1_pre2_FINAL REL_2_1_pre1_FINAL REL_2_1_FINAL REL_2_1_BASE REL_2_0_2_FINAL REL_2_0_1_FINAL REL_2_0_pre4_FINAL REL_2_0_pre3_FINAL REL_2_0_pre2_FINAL REL_2_0_pre1_FINAL REL_2_0_FINAL REL_2_0_BASE REL_1_4_1_pre1_FINAL REL_1_4_1_FINAL REL_1_4 REL_1_4_pre2_FINAL REL_1_4_pre1_FINAL REL_1_4_FINAL REL_1_3_pre1_FINAL REL_1_3_FINAL REL_1_3_BASE
Nothing to show
Pull request Compare This branch is even with dariaphoebe:master.
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
bios
build
bx_debug
cpu
disasm
doc
docs-html
dynamic
font
fpu
gui
host/linux/pcidev
instrument
iodev
memory
misc
patches
plex86
.bochsrc
.conf.amigaos
.conf.beos
.conf.everything
.conf.linux
.conf.macos
.conf.macosx
.conf.nothing
.conf.sparc
.conf.win32-cygwin
.conf.win32-vcpp
.cvsignore
CHANGES
COPYING
Makefile.in
PARAM_TREE.txt
README
README-plugins
README-wxWindows
README.rfb
TESTFORM.txt
TODO
aclocal.m4
bochs.h
bxversion.h.in
bxversion.rc.in
config.cc
config.guess
config.h.in
config.sub
configure
configure.in
crc.cc
extplugin.h
gdbstub.cc
install-sh
load32bitOShack.cc
logio.cc
ltdl.c
ltdl.h
ltdlconf.h.in
ltmain.sh
main.cc
msrs.def
osdep.cc
osdep.h
pc_system.cc
pc_system.h
plex86-interface.cc
plex86-interface.h
plugin.cc
plugin.h
win32_enh_dbg.rc
win32res.rc
wxbochs.rc

README

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

WHAT IS BOCHS?

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 "http://bochs.sourceforge.net".

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.

GETTING CURRENT SOURCE CODE

Source code for Bochs is available from the Bochs home page at
http://bochs.sourceforge.net.  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.

WHERE ARE THE DOCS?

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
  http://bochs.sf.net/doc/docbook/index.html

Some information has not yet been transferred from the older
HTML docs.  These can be found at http://bochs.sf.net/docs-html

WHERE CAN I GET MORE INFORMATION?  HOW DO I REPORT PROBLEMS?

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.

HOW CAN I HELP?

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.