Bochs/bochs
2011-08-26 19:08:37 +00:00
..
bios Support ctrl-alt-del for reboot by Sebastian 2011-08-16 17:54:44 +00:00
build - fixed a warning caused by wrong runtime library for the BOCHS.EXE components 2011-08-22 12:35:49 +00:00
bx_debug Fixed internal debugger part of the bug: 2011-08-17 19:51:32 +00:00
cpu MOVBE instruction exists only in memory form 2011-08-25 21:20:50 +00:00
disasm MOVBE instruction exists only in memory form 2011-08-25 21:20:50 +00:00
doc remove '-cpu' command line option, it can be used using cpu:model command line so no extra option is needed 2011-08-20 18:59:25 +00:00
docs-html clarify error message for pcidev 2011-08-17 18:27:49 +00:00
fpu regen Makefile.in dep 2011-08-18 05:44:54 +00:00
gui - removed Windows font support for the text mode (was disabled by default) 2011-08-22 10:25:29 +00:00
host/linux/pcidev
instrument clean up/fixed instrumentation examples + removed old 2-years old configure options check (deprecated) 2011-07-23 19:58:38 +00:00
iodev - enable extended "read TOC" feature for Windows versions newer than XP (>= 5.1) 2011-08-24 10:48:05 +00:00
memory regen Makefile.in dep 2011-08-18 05:44:54 +00:00
misc - fixed some MSVC warnings 2011-06-19 05:37:30 +00:00
patches - part #1 of BeOS support removal: patches and shortcut script 2011-07-11 16:51:38 +00:00
.bochsrc added yonah CPUID to cpudb. remove bxversion.h from dep files 2011-08-16 19:58:56 +00:00
.conf.amigaos
.conf.everything Patch for emulating target with larger memory than host has available by Gary Cameron. 2011-07-22 17:46:06 +00:00
.conf.linux - removed deprecated --enable-acpi option 2011-05-02 19:29:15 +00:00
.conf.macos - removed deprecated --enable-acpi option 2011-05-02 19:29:15 +00:00
.conf.macosx - removed deprecated --enable-acpi option 2011-05-02 19:29:15 +00:00
.conf.nothing
.conf.sparc - removed deprecated --enable-acpi option 2011-05-02 19:29:15 +00:00
.conf.win32-cygwin - removed deprecated --enable-acpi option 2011-05-02 19:29:15 +00:00
.conf.win32-vcpp - removed deprecated --enable-acpi option 2011-05-02 19:29:15 +00:00
aclocal.m4
bochs.h - don't include plugin.h in bochs.h to reduce dependencies 2011-08-17 22:41:03 +00:00
bxversion.h.in
bxversion.rc.in - deleted executable property 2011-04-03 09:55:17 +00:00
CHANGES - 10% emulation speedup with handlers chaining optimization implemented. The 2011-08-21 14:31:08 +00:00
config.cc added yonah CPUID to cpudb. remove bxversion.h from dep files 2011-08-16 19:58:56 +00:00
config.guess
config.h.in forgot to merge file 2011-08-21 14:38:33 +00:00
config.sub
configure fixed configure script bug 2011-08-26 19:08:37 +00:00
configure.in fixed configure script bug 2011-08-26 19:08:37 +00:00
COPYING
cpudb.h added yonah CPUID to cpudb. remove bxversion.h from dep files 2011-08-16 19:58:56 +00:00
crc.cc - deleted executable property 2011-04-03 09:55:17 +00:00
extplugin.h - first step for DLL plugin support with MSVC. Now the BOCHS.EXE with plugin 2011-06-15 17:24:32 +00:00
gdbstub.cc Adding Id and Rev property to all files 2011-02-24 22:05:47 +00:00
install-sh
load32bitOShack.cc - fixed some MSVC warnings 2011-06-19 05:37:30 +00:00
logio.cc - removed 'text_snapshot_check' feature and related BX_PASS loglevel 2011-07-31 14:38:03 +00:00
ltdl.c Adding Id and Rev property to all files 2011-02-24 22:05:47 +00:00
ltdl.h Adding Id and Rev property to all files 2011-02-24 22:05:47 +00:00
ltdlconf.h.in
ltmain.sh
main.cc - added command line option '--help cpu' that shows the list of supported cpu 2011-08-22 04:07:10 +00:00
Makefile.in - removed duplicate 'clean' for cpu/cpudb 2011-08-19 06:31:51 +00:00
msrs.def - deleted executable property 2011-04-03 09:55:17 +00:00
osdep.cc Adding Id and Rev property to all files 2011-02-24 22:05:47 +00:00
osdep.h - add some symbols required by MSVC for device plugins 2011-06-15 21:55:48 +00:00
param_names.h - removed 'text_snapshot_check' feature and related BX_PASS loglevel 2011-07-31 14:38:03 +00:00
PARAM_TREE.txt - removed 'text_snapshot_check' feature and related BX_PASS loglevel 2011-07-31 14:38:03 +00:00
pc_system.cc Adding Id and Rev property to all files 2011-02-24 22:05:47 +00:00
pc_system.h Adding Id and Rev property to all files 2011-02-24 22:05:47 +00:00
plugin.cc - preparing Bochs for experimental USB xHCI support (written by Ben Lunt) TODO list: 2011-07-04 19:42:47 +00:00
plugin.h - rewrite of the method init_module() similar to the netmod one 2011-08-18 07:05:09 +00:00
README - preparing release 2.4.6 2011-02-22 17:10:47 +00:00
README-plugins
README-wxWindows
README.rfb
TESTFORM.txt
TODO
win32_enh_dbg.rc - deleted executable property 2011-04-03 09:55:17 +00:00
win32res.rc Unify manifest file for Win32 and Win64 - also fixes MSDEV command line compilation issue 2011-03-07 17:07:29 +00:00
wxbochs.rc

Bochs - The cross platform IA-32 (x86) emulator
Updated: Tue Feb 22 18:07:00 CET 2011
Version: 2.4.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.  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.