Bochs/bochs
2007-11-24 14:36:08 +00:00
..
bios - updated after latest changes 2007-11-18 10:21:51 +00:00
build - installer now uses system variable WINDIR instead of hardcoded C:\WINDOWS 2007-09-28 17:58:48 +00:00
bx_debug Eliminate saving of RSP from heart of cpu_loop 2007-11-24 14:22:34 +00:00
cpu Eliminate saving of RSP from heart of cpu_loop 2007-11-24 14:22:34 +00:00
disasm Fixed memory bug in disasm code 2007-11-18 21:29:17 +00:00
doc Update docs and help 2007-10-23 21:59:04 +00:00
docs-html - updated after removing iodebug.html 2006-11-01 17:12:13 +00:00
dynamic
font
fpu Eliminate saving of RSP from heart of cpu_loop 2007-11-24 14:22:34 +00:00
gui - fixed compilation errors 2007-11-02 16:58:46 +00:00
host/linux/pcidev
instrument Some code cleanups and warning fixes 2007-03-14 21:15:15 +00:00
iodev Some indent fixes + speed up hardware read by using inline functions 2007-11-12 21:04:17 +00:00
memory - fixed compilation error 2007-11-02 23:30:07 +00:00
misc Applied patch from #SF tracker 2007-10-31 13:10:04 +00:00
patches Update trace cache patch for new CVS 2007-11-24 14:36:08 +00:00
plex86
.bochsrc Fixed typo 2007-11-20 21:21:08 +00:00
.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 Removed save/restore option 2007-09-28 20:03:31 +00:00
.conf.linux add --show-ips to all configs for future releases (it is not ON by default ?) 2007-10-09 19:49:23 +00:00
.conf.macos Some changes and updates for new release - I would like to compile it with x86-64 + acpi 2007-09-10 15:21:05 +00:00
.conf.macosx Some changes and updates for new release - I would like to compile it with x86-64 + acpi 2007-09-10 15:21:05 +00:00
.conf.sparc Some changes and updates for new release - I would like to compile it with x86-64 + acpi 2007-09-10 15:21:05 +00:00
.conf.win32
.conf.win32-cygwin add --show-ips to all configs for future releases (it is not ON by default ?) 2007-10-09 19:49:23 +00:00
.conf.win32-vcpp add --show-ips to all configs for future releases (it is not ON by default ?) 2007-10-09 19:49:23 +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 Fix compilation errrr 2007-11-22 17:30:40 +00:00
bxversion.h.in
CHANGES Enable alignment check by default for cpu-level >= 4 2007-11-23 12:47:13 +00:00
config.cc Print timestamps feature for performance measurements 2007-11-20 18:36:26 +00:00
config.guess
config.h.in Configure fro speed 2007-11-22 06:28:05 +00:00
config.sub
configure Enable alignment check by default for cpu-level >= 4 2007-11-23 12:47:13 +00:00
configure.in Enable alignment check by default for cpu-level >= 4 2007-11-23 12:47:13 +00:00
COPYING
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 Optimize access to IP (16 bit) - made IP register similar to GPR 2007-10-18 22:44:39 +00:00
install-sh
load32bitOShack.cc Eliminate saving of RSP from heart of cpu_loop 2007-11-24 14:22:34 +00:00
logio.cc warning fixes 2007-10-24 23:29:40 +00:00
ltdl.c
ltdl.h
ltdlconf.h.in
ltmain.sh
main.cc Print timestamps feature for performance measurements 2007-11-20 18:36:26 +00:00
Makefile.in During Bochs benchmarking I figured out that hostasm actually slow down the emulation ... so remove this ugly code which also doesn't help :) 2007-10-21 22:07:33 +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
PARAM_TREE.txt A lot of changes but everything is really trivial. 2007-09-28 19:52:08 +00:00
pc_system.cc Complete MONITOR/MWAIT implemntation (including monitoring of memory range) 2007-11-01 18:03:48 +00:00
pc_system.h Complete MONITOR/MWAIT implemntation (including monitoring of memory range) 2007-11-01 18:03:48 +00:00
plex86-interface.cc Eliminate saving of RSP from heart of cpu_loop 2007-11-24 14:22:34 +00:00
plex86-interface.h
plugin.cc warning fixes 2007-10-24 23:29:40 +00:00
plugin.h warning fixes 2007-10-24 23:29:40 +00:00
README - updates for release 2.3.5 2007-09-16 07:53:00 +00:00
README-plugins
README-wxWindows
README.rfb
TESTFORM.txt
TODO Update save/restore TODO 2007-11-09 12:08:30 +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

Bochs x86 Pentium+ Emulator
Updated: Sun Sep 16 09:53:00 CEST 2007
Version: 2.3.5

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.