Bochs/bochs
2013-01-19 15:18:07 +00:00
..
bios Move BIOS_COPYRIGHT_STRING to gain space at 0xfef3. Sebastian 2013-01-08 18:12:14 +00:00
build add rdrand.cc to MSDEV workspace files 2012-10-09 16:50:45 +00:00
bx_debug add 'tlb' command to debugger to do TLB lookup 2013-01-14 17:02:07 +00:00
cpu unfortunately this change is rquired to make SMAP and SMEP features to work. 2013-01-16 17:28:20 +00:00
disasm Add RDRAND/RDSEED instructions support (+ disasm) 2012-10-09 15:16:48 +00:00
doc move misaligned_sse from compile time to .bochsrc option 2012-12-20 19:43:11 +00:00
docs-html implemented SMAP (Supervisor Mode Access Protection) from [Intel Architecture Instruction Set Extensions Programming Reference] rev14 2012-09-10 15:22:26 +00:00
gui save the network configuration lines using the parameter tree 2013-01-19 12:25:53 +00:00
host/linux/pcidev
instrument fixed typo caused compilation err 2013-01-18 08:12:36 +00:00
iodev save the sound configuration using the parameter tree 2013-01-19 15:18:07 +00:00
memory implemented volatile BIOS memory write support (controlled by PIIX/PIIX3 XBCS register) 2012-12-02 19:59:23 +00:00
misc - moved the lowlevel cdrom and disk image stuff to the new subdirectory iodev/hdimage 2012-08-05 18:13:38 +00:00
patches - removed outdated patch 2012-07-15 09:31:02 +00:00
.bochsrc move misaligned_sse from compile time to .bochsrc option 2012-12-20 19:43:11 +00:00
.conf.amigaos
.conf.everything
.conf.linux - added devices ES1370 and E1000 to shortcut scripts (known to work with Linux 2012-05-01 18:03:43 +00:00
.conf.macos - added devices ES1370 and E1000 to shortcut scripts (known to work with Linux 2012-05-01 18:03:43 +00:00
.conf.macosx - added devices ES1370 and E1000 to shortcut scripts (known to work with Linux 2012-05-01 18:03:43 +00:00
.conf.nothing Enable PCI support by default / better text formatting for 'configure --help' 2012-10-25 16:02:03 +00:00
.conf.sparc
.conf.win32-cygwin - added devices ES1370 and E1000 to shortcut scripts (known to work with Linux 2012-05-01 18:03:43 +00:00
.conf.win32-vcpp - added devices ES1370 and E1000 to shortcut scripts (known to work with Linux 2012-05-01 18:03:43 +00:00
aclocal.m4 - fixed autoconf 2.68 warnings 2012-02-19 19:50:56 +00:00
bochs.h save the network configuration lines using the parameter tree 2013-01-19 12:25:53 +00:00
bxversion.h.in
bxversion.rc.in
CHANGES - forgot to add release date 2012-09-02 11:24:32 +00:00
config.cc save the network configuration lines using the parameter tree 2013-01-19 12:25:53 +00:00
config.guess
config.h.in move misaligned_sse from compile time to .bochsrc option 2012-12-20 19:43:11 +00:00
config.sub
configure move misaligned_sse from compile time to .bochsrc option 2012-12-20 19:43:11 +00:00
configure.in move misaligned_sse from compile time to .bochsrc option 2012-12-20 19:43:11 +00:00
COPYING
cpudb.h added AMD Bulldozer architecture CPU (Zambezi) to CPUDB 2013-01-07 19:33:04 +00:00
crc.cc
extplugin.h
gdbstub.cc vga refresh framework changes 2012-10-28 08:23:39 +00:00
install-sh
LICENSE - added original authors on top of LGPL'd sources ported from Qemu 2012-08-30 20:41:25 +00:00
load32bitOShack.cc implemented SVM decode assists. some is still missing - coming soon 2012-11-02 07:46:50 +00:00
logio.cc vga refresh framework changes 2012-10-28 08:23:39 +00:00
ltdl.c
ltdl.h
ltdlconf.h.in
ltmain.sh
main.cc started implementing the i430FX chipset 2012-11-11 08:11:17 +00:00
Makefile.in - fpu directory is now a subdirectory in 'cpu' 2012-09-12 21:08:40 +00:00
msrs.def
osdep.cc
osdep.h - fixed compilation with large ramfile support present on MSVC 2012-08-26 14:43:14 +00:00
param_names.h save the sound configuration using the parameter tree 2013-01-19 15:18:07 +00:00
PARAM_TREE.txt move misaligned_sse from compile time to .bochsrc option 2012-12-20 19:43:11 +00:00
pc_system.cc some cleanups and optimizations with new event interface 2012-10-03 15:49:45 +00:00
pc_system.h some cleanups and optimizations with new event interface 2012-10-03 15:49:45 +00:00
plugin.cc Applied initial version of the 3dfx Voodoo Graphics emulation. The Voodoo core 2012-09-14 21:50:50 +00:00
plugin.h implemented volatile BIOS memory write support (controlled by PIIX/PIIX3 XBCS register) 2012-12-02 19:59:23 +00:00
README - preparing release 2.6 2012-09-02 11:11:00 +00:00
README-plugins
README-wxWidgets - attempt to fix random freezes when using the wxGTK port (using the gui option 2012-08-22 13:11:08 +00:00
README.rfb
TESTFORM.txt
TODO removed old deprecated options from the code 2012-09-14 13:32:54 +00:00
win32_enh_dbg.rc
win32res.rc - second try to fix duplicate resource id 2012-08-06 21:00:42 +00:00
wxbochs.rc

Bochs - The cross platform IA-32 (x86) emulator
Updated: Sun Sep  2 13:10:00 CEST 2012
Version: 2.6

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. Bochs can be compiled to emulate many different x86 CPUs,
from early 386 to the most recent x86-64 Intel and AMD processors
which may even not reached the market yet. Bochs is capable of running
most Operating Systems inside the emulation, for example DOS,
Linux or Windows. 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 LICENSE and 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 SVN to get the latest sources, or grab a SVN
snapshot which is updated frequently. The releases contain the most
stable code, but if you want the very newest features try the
SVN 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 SVN
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 SVN.  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.