Bochs/bochs
2008-12-05 12:48:36 +00:00
..
bios Don't power down vga card on entering S3 state. 2008-12-04 18:48:33 +00:00
build update msdev workspaces 2008-10-18 20:36:52 +00:00
bx_debug Fixed double tick count in stepN command of bx_debugger with SMP enabled but only 1 CPU 2008-11-18 21:03:04 +00:00
cpu preparing to different way of handling MSR registers 2008-12-05 12:48:36 +00:00
disasm Fixes in disasm 2008-10-01 09:10:54 +00:00
doc Remove external debugger interface: 2008-10-01 09:44:40 +00:00
docs-html - Added graphical Bochs debugger under Win32 host ! 2008-10-21 13:45:03 +00:00
dynamic
font
fpu Fixed problem in one of my prev commits 2008-09-18 19:10:23 +00:00
gui - make the wx status bar work again (colors are not supported) 2008-11-16 21:01:09 +00:00
host/linux/pcidev another whitespace cleanup by Sebastien 2008-02-05 22:57:43 +00:00
instrument Fixed CPU state after software reset (INIT). 2008-11-18 20:55:59 +00:00
iodev Handle S3 in PIIX4 ACPI 2008-12-04 18:50:31 +00:00
memory - Fixed theoretically possible pageWriteStamp overflow 2008-10-21 19:50:05 +00:00
misc another whitespace cleanup by Sebastien 2008-02-05 22:57:43 +00:00
patches Added patch for compilation of Bochs BIOS with win32 version of bcc 2008-05-08 18:53:07 +00:00
plex86 another whitespace cleanup by Sebastien 2008-02-05 22:57:43 +00:00
.bochsrc - Added graphical Bochs debugger under Win32 host ! 2008-10-21 13:45:03 +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 Add -enable-movbe option to .conf.everything 2008-08-13 21:51:07 +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 re-locate BX_SMP_PROCESSORS macro 2008-10-20 19:13:08 +00:00
bxversion.h.in
bxversion.rc.in Added Bochs version info for Win32 - patch from @SF tracker 2008-02-09 07:51:15 +00:00
CHANGES Updates in CHANGES 2008-12-04 18:54:43 +00:00
config.cc Fixed in CVS 2008-10-14 06:55:18 +00:00
config.guess
config.h.in moving definition to config.h 2008-12-01 19:35:25 +00:00
config.sub
configure - Added graphical Bochs debugger under Win32 host ! 2008-10-21 13:45:03 +00:00
configure.in - Added graphical Bochs debugger under Win32 host ! 2008-10-21 13:45:03 +00:00
COPYING
crc.cc Indent changes 2008-04-07 18:48:11 +00:00
extplugin.h
gdbstub.cc Fixed registers 'mess' in gdbstub. Or at least part of it 2008-11-09 22:56:54 +00:00
install-sh
load32bitOShack.cc Hide some BX_MEM_C variables 2008-05-01 20:08:37 +00:00
logio.cc Remove external debugger interface: 2008-10-01 09:44:40 +00:00
ltdl.c
ltdl.h
ltdlconf.h.in
ltmain.sh
main.cc updates for instrumentation 2008-11-18 20:58:09 +00:00
Makefile.in Fixed compilation by Microsoft nmake 2008-06-01 16:48:13 +00:00
osdep.cc another whitespace cleanup by Sebastien 2008-02-05 22:57:43 +00:00
osdep.h another whitespace cleanup by Sebastien 2008-02-05 22:57:43 +00:00
PARAM_TREE.txt Implement modern BIOS mode for limiting max reported CPUID function to 3. 2008-09-22 21:38:15 +00:00
pc_system.cc Optimize TLB flush methods 2008-08-13 21:51:54 +00:00
pc_system.h optimize bx_pc_system.tickn 2008-03-19 18:36:17 +00:00
plex86-interface.cc Some changes to make x86-debugger feature working back 2008-05-23 17:49:46 +00:00
plex86-interface.h
plugin.cc whispace, tab2space, indent, dos2unix and other cleanups 2008-02-15 22:05:43 +00:00
plugin.h Fixed CPU state after software reset (INIT). 2008-11-18 20:55:59 +00:00
README - updates for release 2.3.7 2008-06-03 16:11:20 +00:00
README-plugins another whitespace cleanup by Sebastien 2008-02-05 22:57:43 +00:00
README-wxWindows another whitespace cleanup by Sebastien 2008-02-05 22:57:43 +00:00
README.rfb
TESTFORM.txt TESTFORM update 2008-06-15 16:26:07 +00:00
TODO Update CHANGES 2008-11-06 19:37:19 +00:00
win32_enh_dbg.rc - Added graphical Bochs debugger under Win32 host ! 2008-10-21 13:45:03 +00:00
win32res.rc - Added graphical Bochs debugger under Win32 host ! 2008-10-21 13:45:03 +00:00
wxbochs.rc - added version info for wxMSW port 2008-02-10 22:03:47 +00:00

Bochs - The cross platform IA-32 (x86) emulator
Updated: Tue Jun 3 18:11:00 CEST 2008
Version: 2.3.7

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.