Bochs/bochs
Stanislav Shwartsman 14e3dcca08 patch for ACPI header - ability to have different rev number for different ACPI tables 2007-08-30 21:05:22 +00:00
..
bios patch for ACPI header - ability to have different rev number for different ACPI tables 2007-08-30 21:05:22 +00:00
build - install both default and legacy version of the Bochs BIOS 2007-05-17 15:47:35 +00:00
bx_debug Patch from mailing list 2007-07-09 14:57:33 +00:00
cpu rewrite page fault 2007-08-30 16:48:10 +00:00
disasm implement prefetch hint opcodes 2007-08-23 16:47:51 +00:00
doc - install both default and legacy version of the Bochs BIOS 2007-05-17 15:47:35 +00:00
docs-html - updated after removing iodebug.html 2006-11-01 17:12:13 +00:00
dynamic
font
fpu Converted CR0 bits to one register similar to CR4 - a bit slower but helps with other features implemntation 2007-07-09 15:16:14 +00:00
gui Fixed Windows compilation 2007-08-25 13:11:53 +00:00
host/linux/pcidev - fixed possible memory leaks and compilation warnings (patch by Frank Cornelis) 2004-11-16 20:44:48 +00:00
instrument Some code cleanups and warning fixes 2007-03-14 21:15:15 +00:00
iodev - evaluate_media() now returns 1 only if the media is valid (total number of 2007-08-21 14:18:16 +00:00
memory Fixed typo 2007-05-15 12:48:59 +00:00
misc - fixed remaining type conflicts in vmware lseek() method and the bxcommit utility 2006-11-19 09:55:23 +00:00
patches Added trace cache patch 2007-03-07 20:26:02 +00:00
plex86 - support for GNU/kFreeBSD and GNU/kNetBSD added in lowlevel iodev code (cdrom, 2004-09-11 15:39:53 +00:00
.bochsrc - fixed floppy boot signature check switch 2007-08-01 17:10:24 +00:00
.conf.AIX.4.3.1
.conf.amigaos - enable VBE support by default in configure script 2006-11-20 18:55:16 +00:00
.conf.beos - enable VBE support by default in configure script 2006-11-20 18:55:16 +00:00
.conf.everything Implemented #AC check under configure option 2007-07-31 20:25:52 +00:00
.conf.linux - enable VBE support by default in configure script 2006-11-20 18:55:16 +00:00
.conf.macos - enable VBE support by default in configure script 2006-11-20 18:55:16 +00:00
.conf.macosx - enable VBE support by default in configure script 2006-11-20 18:55:16 +00:00
.conf.sparc - enable VBE support by default in configure script 2006-11-20 18:55:16 +00:00
.conf.win32
.conf.win32-cygwin - enable VBE support by default in configure script 2006-11-20 18:55:16 +00:00
.conf.win32-vcpp - enable VBE support by default in configure script 2006-11-20 18:55:16 +00:00
CHANGES Implemented #AC check under configure option 2007-07-31 20:25:52 +00:00
COPYING
Makefile.in - install both default and legacy version of the Bochs BIOS 2007-05-17 15:47:35 +00:00
PARAM_TREE.txt - moved config interface option to the general options list, since it cannot be 2006-10-08 10:18:51 +00:00
README - updated after release 2.3 2006-08-27 15:36:39 +00:00
README-plugins
README-wxWindows
README.rfb - remove GPL'd rfbproto.h 2004-04-05 12:09:25 +00:00
TESTFORM.txt Do not allow to allocate more than 2048Mb of emulated memory. 2005-03-06 21:23:38 +00:00
TODO - TODO status update for Bochs 2.3 2006-08-25 11:58:55 +00:00
aclocal.m4 - implemented GTK2+ detection for wxGTK (patch by Guillem Jover <guillem@debian.org>) 2006-03-13 17:18:33 +00:00
bochs.h SSE4 support 2007-04-19 16:12:21 +00:00
bxversion.h.in
config.cc - fixed some gcc 4.x warnings 2007-04-08 15:02:50 +00:00
config.guess
config.h.in Implemented #AC check under configure option 2007-07-31 20:25:52 +00:00
config.sub
configure Implemented #AC check under configure option 2007-07-31 20:25:52 +00:00
configure.in Implemented #AC check under configure option 2007-07-31 20:25:52 +00:00
crc.cc This is cumulative patch for bochs debugger, it is only very first step towards working debugger supporting all new simulator functionalitieS. 2006-01-24 19:03:55 +00:00
extplugin.h
gdbstub.cc Merge patch from @SF bug tracker 2007-02-07 17:53:06 +00:00
install-sh
load32bitOShack.cc Converted CR0 bits to one register similar to CR4 - a bit slower but helps with other features implemntation 2007-07-09 15:16:14 +00:00
logio.cc Patch received by e-mail from darkelf 2006-11-19 16:18:41 +00:00
ltdl.c
ltdl.h
ltdlconf.h.in
ltmain.sh
main.cc Improve single threaded simulation speed in SMP binary of Bochs 2007-03-06 21:12:20 +00:00
osdep.cc - fixed compile error related to gettimeofday() in MinGW/MSYS and Cygwin with 2006-08-07 17:59:15 +00:00
osdep.h Remove redundant 0x from FMT_ADDRX macro for cygwin 2006-02-11 20:47:22 +00:00
pc_system.cc - cleanup() method added to reset the number of status items (cannot be done in 2006-09-17 20:37:28 +00:00
pc_system.h Merge SAVE_RESTORE branch to CVS 2006-05-27 15:54:49 +00:00
plex86-interface.cc Fixed ton of code duplication. 2006-08-31 18:18:17 +00:00
plex86-interface.h
plugin.cc - removed exit() method from the devmodel object, since all that stuff can be 2006-09-16 14:47:40 +00:00
plugin.h - ported ACPI enable/disable support from latest Qemu sources 2007-08-04 08:57:42 +00:00
win32res.rc - removed USB port option parameter and store device and option in one single 2007-03-18 17:52:15 +00:00
wxbochs.rc

README

Bochs x86 Pentium+ Emulator
Updated: Sun Aug 27 09:18:00 CEST 2006
Version: 2.3

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, Pentium Pro or x86-64 CPU, including optional MMX, 
SSE/SSE2/SSE3 and 3DNow! instructions.  Bochs is capable of running
most Operating Systems inside the emulation including Linux, DOS,
Windows 95/98 and Windows NT/2000/XP.
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.