Bochs/bochs
Stanislav Shwartsman caa30e3462 bugfix
2010-04-02 18:24:27 +00:00
..
bios
build RPM preuninstall scriptlet removes /core - ID: 2955911 2010-02-21 06:38:21 +00:00
bx_debug announce (not implement yet) PCID 2010-03-31 14:00:46 +00:00
cpu bugfix 2010-04-02 18:24:27 +00:00
disasm fixes 2010-03-30 18:12:19 +00:00
doc Move MMX to be runtime option 2010-03-01 18:53:53 +00:00
docs-html
dynamic
font
fpu FPREM/FPREM1 fix 2010-03-22 22:11:00 +00:00
gui fix undefined CPUID options when CPU_LEVEL is too small 2010-03-05 20:42:10 +00:00
host/linux/pcidev
instrument
iodev apic_dest_t as datatype 2010-03-27 09:56:30 +00:00
memory apic virtualization + vmx fixes 2010-03-16 14:51:20 +00:00
misc
patches
plex86
.bochsrc Bochs boots with seabios now, think of adding seabios.bin into distribution ... 2010-04-02 18:12:47 +00:00
.conf.amigaos
.conf.beos
.conf.everything Move MMX to be runtime option 2010-03-01 18:53:53 +00:00
.conf.linux allow to configure CPU features at runtime - implemened on example of SSE/AES/MOVBE/POPCNT 2010-02-25 22:04:31 +00:00
.conf.macos allow to configure CPU features at runtime - implemened on example of SSE/AES/MOVBE/POPCNT 2010-02-25 22:04:31 +00:00
.conf.macosx allow to configure CPU features at runtime - implemened on example of SSE/AES/MOVBE/POPCNT 2010-02-25 22:04:31 +00:00
.conf.nothing
.conf.sparc allow to configure CPU features at runtime - implemened on example of SSE/AES/MOVBE/POPCNT 2010-02-25 22:04:31 +00:00
.conf.win32-cygwin allow to configure CPU features at runtime - implemened on example of SSE/AES/MOVBE/POPCNT 2010-02-25 22:04:31 +00:00
.conf.win32-vcpp allow to configure CPU features at runtime - implemened on example of SSE/AES/MOVBE/POPCNT 2010-02-25 22:04:31 +00:00
aclocal.m4
bochs.h
bxversion.h.in
bxversion.rc.in
CHANGES update CHANGES 2010-04-02 17:22:11 +00:00
config.cc fixes 2010-03-12 11:42:34 +00:00
config.guess
config.h.in Move MMX to be runtime option 2010-03-01 18:53:53 +00:00
config.sub
configure compilation fix 2010-04-02 08:00:57 +00:00
configure.in compilation fix 2010-04-02 08:00:57 +00:00
COPYING
crc.cc
extplugin.h
gdbstub.cc Move param_names.h into bochs root folder 2010-02-26 14:18:19 +00:00
install-sh
load32bitOShack.cc Move param_names.h into bochs root folder 2010-02-26 14:18:19 +00:00
logio.cc
ltdl.c
ltdl.h
ltdlconf.h.in
ltmain.sh
main.cc fix undefined CPUID options when CPU_LEVEL is too small 2010-03-05 20:42:10 +00:00
Makefile.in Move param_names.h into bochs root folder 2010-02-26 14:18:19 +00:00
msrs.def
osdep.cc
osdep.h
param_names.h MWAIT_IS_NOP option 2010-03-12 11:28:59 +00:00
PARAM_TREE.txt MWAIT_IS_NOP option 2010-03-12 11:28:59 +00:00
pc_system.cc
pc_system.h
plex86-interface.cc
plex86-interface.h
plugin.cc
plugin.h
README
README-plugins
README-wxWindows
README.rfb
TESTFORM.txt Make XAPIC runtime option as well 2010-02-28 14:52:17 +00:00
TODO
win32_enh_dbg.rc
win32res.rc
wxbochs.rc

Bochs - The cross platform IA-32 (x86) emulator
Updated: Thu November 12 13:53:00 CET 2009
Version: 2.4.2

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.